[iOS] Appshell tabs not appearing on iOS after screen rotation #13621
Labels
area-controls-shell
Shell Navigation, Routes, Tabs, Flyout
fixed-in-8.0.0-preview.4.8333
Look for this fix in 8.0.0-preview.4.8333!
platform/iOS 🍎
t/bug
Something isn't working
version/ios-16
Milestone
Description
I have raised this previously in the xamarin forms repo. But I have tested MAUI and it is also an issue here, so I thought I would raise it here also.
The Xamarin issue can be found at (with some screenshots):
xamarin/Xamarin.Forms#15684
I have also asked on the Micrososft Q & A for any possible workaround here:
https://learn.microsoft.com/en-us/answers/questions/1180648/xamarin-and-maui-shell-tabs-not-rendering-correctl
The tab views don't render correctly after rotating an iOS device on version 16.3 (from portrait to horizontal and back to portrait).
If you have a shell app with multiple tabs at the top, it initially loads all the data and allows the user to select the tabs.
Rotating to landscape seems fine.
Rotating back to portrait causes all but the first tab to disappear. The user can no longer select the tab.
Rotating back to landscape causes the tabs to appear again.
Portrait however will only show the first tab.
Steps to Reproduce
Create a new Shell project
Add a tab with 2 or more items. e.g:
<Tab Title="Items" Icon="icon_about.png"> <ShellContent Title="About" Icon="icon_about.png" Route="AboutPage" ContentTemplate="{DataTemplate local:AboutPage}" /> <ShellContent Title="Browse" Icon="icon_feed.png" ContentTemplate="{DataTemplate local:ItemsPage}" /> </Tab> </TabBar>
3)Rotate the device to landscape, then rotate back to portrait. Only the first tab is visible on the top.
Link to public reproduction project repository
https://github.com/developerfiveneosoftware/iosTabBug
Version with bug
7.0 (current)
Last version that worked well
Unknown/Other
Affected platforms
iOS
Affected platform versions
ios 16+
Did you find any workaround?
No workaround yet.
It seems to work on iOS 15
Relevant log output
No response
The text was updated successfully, but these errors were encountered: