My app doesn't respond on iPhone Air iOS 26.1. After startup, my app shows the main view with a tab bar controller containing 4 navigation controllers. However, when a second-level view controller is pushed onto any navigation controller, the UI freezes and becomes unresponsive. The iPhone simulator running iOS 26.1 exhibits the same problem.
The debug profile shows CPU usage at 100%.
However, other devices and simulators do not have this problem.
I am running into the same issue, have not found a solution yet. It seems to happen during the Liquid Glass animation transition.
I'm not able to disable the new Liquid Glass UI using this flag UIDesignRequiresCompatibility are you?
@viktor_runcoach and @howard_kang , thanks for both post, so when we have 2 reports is good to compare the issue. Both are using the iPhone Air simulator with iOS 26.1 and both are on Xcode 26.1. Am I correct?
https://developer.apple.com/forums/thread/809465?answerId=868722022#868722022
Can you please download Xcode 26.2 beta and try exactly the same thing?
Lets get to the bottom of this issue.
Albert Pascual Worldwide Developer Relations.
Albert, I have downloaded Xcode 26.2 (17C48), the issue exists and is isolated to the iPhone Air. Both iPhone Air 26.2 and 26.1 simulators have this issue.
Other simulators on Xcode 26.2 remain free of this issue.
Let me know if there is additional information I can provide.
@viktor_runcoach thanks for letting me know, I didn't see the issue when I use Xcode 26.2 beta and the simulator for iPhone Air, but it means I need to get a real device and start trying to reproduce it. However is very important if you can file a bug using a focus sample showing the issue.
Once you open the bug report, please post the FB number here for my reference.
If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why?
Above all, thanks for providing all this. Looking forward your bug to get to the bottom of the issue.
Albert Pascual Worldwide Developer Relations.
As ray_cai outlined the issue was related to the LaunchImage.
@howard_kang this fixed the issue for me.
LaunchImage from the Asset catalog.LaunchImage from your build settings.Launch Screen storyboard to the project.Launch screen interface file base name with the name of your storyboard Launch Screen.storyboard to your Info.plist file.