Hi,
I have reported the issue using the Feedback Assistant (FB14808233)
Thanks
tomzion
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Thank you for your feedback. This issue has not occurred in previous iOS versions before iOS 18, so this change is unexpected. Placing the child view controller within each tab’s view controller is not feasible for my project’s architecture. Could you please clarify how placing the child view controller "in a parent above the UITabBarController (as a sibling)" would work in resolving this issue? I appreciate your insights.
I’ve tried placing the child view controller "in a parent above the UITabBarController (as a sibling)" by embedding the tab bar in a nav controller. This works, but I’m unsure of its impact on my app. Is this the correct approach? Also, why does adding a child VC to the tab bar controller now cause issues in iOS 18, and why didn't this happen in previous versions?
I'm experiencing a regression with the solution of placing the child view controller "in a parent above the UITabBarController (as a sibling)". Could you provide insight into what changes were made in iOS 18 that might be causing this new behavior?