You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a page is pushed to the stack from a 5th menu point (or more) in a Tabbar, it is not possible to add another page to the stack. No exceptions, no errors - execution just stops! When "go back" is pushed, the label in tabbar is overwritten with the name of the page when returned to mainpage! If the same page is pushed (GotoAsync()) from a menu point 1-4 on the tabbar no issue. The issue exist on IOS, not on Android nor Windows.
Steps to Reproduce
Use attached repro. Deploy on IOS and select a Tab "Working 1". Press "Go to second page"., then press "Go back". Everything works fine.
Select Tab "Not working 1". Press "Go to second page" Nothing happens. The press < More. Observer Tab label has changed from "not working 1" to SecondPage.
Description
When a page is pushed to the stack from a 5th menu point (or more) in a Tabbar, it is not possible to add another page to the stack. No exceptions, no errors - execution just stops! When "go back" is pushed, the label in tabbar is overwritten with the name of the page when returned to mainpage! If the same page is pushed (GotoAsync()) from a menu point 1-4 on the tabbar no issue. The issue exist on IOS, not on Android nor Windows.
Steps to Reproduce
Use attached repro. Deploy on IOS and select a Tab "Working 1". Press "Go to second page"., then press "Go back". Everything works fine.
Select Tab "Not working 1". Press "Go to second page" Nothing happens. The press < More. Observer Tab label has changed from "not working 1" to SecondPage.
Link to public reproduction project repository
https://github.com/SorenBech2/ShellTestMAUI9
Version with bug
9.0.10 SR1
Is this a regression from previous behavior?
No, this is something new
Last version that worked well
No response
Affected platforms
iOS
Affected platform versions
IOS 17, 18
Did you find any workaround?
No
Relevant log output
The text was updated successfully, but these errors were encountered: