Thibault Durand

Hi, I develop a Xamarin.Forms application that targets both iOS and Android and I was surprised to realize that NControl consider the given coordinates as points on iOS (scale-independent)(called density...

This makes TabbedPage behavior _very_ inconsistent between iOS and Android and is likely to confuse new Xamarin.Forms developers a lot. Fixing this should be high prio, considering for how long...

Wonder if this is a duplicate of #9209 ? Another repro here: https://github.com/durandt/maui-issue2-ios-stacklayout-scroll

> > > > agreed i have same issue with .net 8 maui and workaround is not working for me either > > > > > > > > >...

(Not a MAUI team member) I think using the ScrollView in a StackLayout is discouraged. Although what you are trying to achieve would have worked in Xamarin.Forms, the StackLayout seems...

Hi, I get the same error when changing language (culture) in my app. Changing culture raises an event. Every LocalizedString (custom class) will then raise OnPropertyChanged on the "Text" string...

Workaround: Only use 5 tab items (4 tab items + own more-page on fifth tab). We were already doing this on iOS due to some more-tab related bugs, so easy...

I want to add that this behaves differently (MAUI 8.0.7 but I think it was the case on MAUI 7 too) on iOS and Android. You can easily test that...

This is the work-around I ended up using: - Override your Shell's OnNavigating to trigger PopToRootAsync on Android, when navigating to the same tab which NavigationStack has more than one...

This issue has been around since Xamarin.Forms (xamarin/Xamarin.Forms#3855) This issue also causes rendering issues for the view attached in the shell tab as it is not initialized properly. For example,...