32 comments

Discussion is closed. Login to edit/delete existing comments.

• 

  David Maw September 24, 2023 · Edited 0

  Collapse this comment Copy link

  Progress indeed, but alas I'm still blocked by a number of issues, the worst of which is the inability to use a SwipeView within a CollectionView on Windows, ruling out its use in any cross-platform application. The initial attempt at a fix was a rewrite which seems to have been completed then rejected in favor of using the native control, after that, no apparent progress. That means it joins another dozen or so bugs I have outstanding from .NET 6, some are minor nits, but others, like this one (my version of it was #9243) are extremely difficult to code...

  Read more

  Progress indeed, but alas I’m still blocked by a number of issues, the worst of which is the inability to use a SwipeView within a CollectionView on Windows, ruling out its use in any cross-platform application. The initial attempt at a fix was a rewrite which seems to have been completed then rejected in favor of using the native control, after that, no apparent progress. That means it joins another dozen or so bugs I have outstanding from .NET 6, some are minor nits, but others, like this one (my version of it was #9243) are extremely difficult to code around, since their very presence in XAML causes run time crashes so you have to have distinct pages for Android and Windows.

  Having made a good faith effort to reproduce and report problems I’m disappointed by just how many are still outstanding after a year, still, I get priorities. From my perspective if there was just a way to make this one problem not cause a crash, I’d be way ahead, the rest I could code around if I had to.

  Read less
• 

  Timothy Liu September 21, 2023 0

  Collapse this comment Copy link

  Why Kotlin Multiplatforms can, while MAUI cannot?

  https://kotlinlang.org/docs/multiplatform.html#kotlin-multiplatform-use-cases

• 

  Robin Schroeder September 21, 2023 0

  Collapse this comment Copy link

  Running Visual Studio 2022 Preview 17.8.0 Preview 2.0

  We are getting an error while building our MAUI Android/iOS app:
  XA8000
  Could not find Android Resource ‘@layout/camerafragment’. Please update @(AndroidResource) to add the missing resource.
  C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\34.0.0-rc.1.432\tools\Xamarin.Android.Common.targets 1458

  Any guidance on this? We would love to update to .Net 8, but are blocked with this issue.

  • 

    Robin Schroeder September 25, 2023 · Edited 0

    Collapse this comment Copy link

    With help from the amazing Jonathan Peppers, we learned that this error is caused by having the following nugets in the soln. We didn’t need them anymore.

    Xamarin.CommunityToolkit.MauiCompat
    Xamarin.CommunityToolkit.Markup.MauiCompat

• 

  Hugo Fonseca September 19, 2023 1

  Collapse this comment Copy link

  David, I do not envy your position atm. Clearly the level of confidence in MAUI is extremely low at the moment and the MAUI team (as well as the VS team and Microsoft in general) is not doing it any favors with constant releases that introduce a new issue for every other issue they fix or feature they add.

  We, like many others, are trying to use MAUI to create a mobile app with a single code base that can target Android and iOS, as part of broader product. As a LOB product all we want is a stable platform, that...

  Read more

  David, I do not envy your position atm. Clearly the level of confidence in MAUI is extremely low at the moment and the MAUI team (as well as the VS team and Microsoft in general) is not doing it any favors with constant releases that introduce a new issue for every other issue they fix or feature they add.

  We, like many others, are trying to use MAUI to create a mobile app with a single code base that can target Android and iOS, as part of broader product. As a LOB product all we want is a stable platform, that performs reasonably, with a good development experience for these two main targets.

  As others have said, you need resources from Microsoft, a serious push not just for first level testing (internal within the team) and by the broader community, but by internal usage of the product by other Microsoft teams. Only the internal pain of usage the platform to develop applications will highlight its state and create the force (and provide the resources) to get it to a stable and usable state.

  I understand the deadlines and the need to release in line with the other .NET components, but someone needs to have the clear head to say it’s not ready and demand more resources to make it ready.

  We’re all here eagerly waiting for a stable version that we can rely upon and all jump on the bandwagon. Don’t get me wrong: the premises of the product is great, what you have achieved so far is good but you are risking it all disappear if you keep down this path.

  Best of luck and we look forward to future releases.

  Read less
  • 

    Leon September 20, 2023 0

    Collapse this comment Copy link

    To give developers enough confidence to use it, Microsoft need create a famous application with MAUI for different platforms.

• 

  ath tse September 19, 2023 · Edited 0

  Collapse this comment Copy link

  How about bug #15216 ?

• 

  Qui Bono September 18, 2023 1

  Collapse this comment Copy link

  Guys, MAUI is a disaster.
  I left for Flutter and got my life back.

• 

  Homer X September 16, 2023 2

  Collapse this comment Copy link

  As everyone is saying quality is so bad since the Xamarin times that nobody want to use this MAUI for new projects. In years using MS stack (VB, winforms, wpf, silverlight, asp.net, etc) i havent seen such a bad quality product coming from MS with so many bugs, i dont know what is problem and why havent been solved for years with xamarin but defenetely xamarin/maui doesnt look like a MS product and is not to the standards that a customer would expect from Microsoft.

  Blazor in the other side works great, maybe you should focus on MAUI+Blazor side and be...

  Read more

  As everyone is saying quality is so bad since the Xamarin times that nobody want to use this MAUI for new projects. In years using MS stack (VB, winforms, wpf, silverlight, asp.net, etc) i havent seen such a bad quality product coming from MS with so many bugs, i dont know what is problem and why havent been solved for years with xamarin but defenetely xamarin/maui doesnt look like a MS product and is not to the standards that a customer would expect from Microsoft.

  Blazor in the other side works great, maybe you should focus on MAUI+Blazor side and be part of the Blazor team.

  A great UI designer like WPF/Winforms designer would be nice to have too for many to start exploring the framework. we have been used to these designers since VB/winforms/wpf.

  Read less
• 

  Jan Seris September 15, 2023 · Edited 4

  Collapse this comment Copy link

  So did you finally hire more devs or are you still developing MAUI in 5 people? Tim Corey has perfectly summed up MAUI in his VS for Mac video: “They are more talking about MAUI than working on MAUI”. Rebranded Xamarin with introduced bugs from WinUI 3 breaking with every new update – 1 bug fix and 1 new bug in every new version.

• 

  Seyyed Soroosh Hosseinalipour September 14, 2023 0

  Collapse this comment Copy link

  ITNOA

  When publish a great and rich visual designer for MAUI?

  https://developercommunity.visualstudio.com/t/MAUI-XAML-Designer-and-editor-not-workin/1589956?q=MAUI+Designer

• 

  Strypper Vandel Jason September 13, 2023 2

  Collapse this comment Copy link

  “qUalITy” 🤡