Hello Travis, [quote='897439022, DTS Engineer, /thread/837564?answerId=897439022#897439022'] When I try this approximate setup on iOS 27, the contents of the Share Sheet appears as expected. Are you able to share the code that reproduces this issue? Include the affected platforms and versions. [/quote] Unfortunately, I can't share the code due to an NDA. Also, I haven't yet been able to reproduce the bug in a sample project that I could attach to my Feedback Assistant report. [quote='897439022, DTS Engineer, /thread/837564?answerId=897439022#897439022'] One callout here: UITabBarController inherits from UIViewController, it already manages its own view and children. You might not need another view controller wrapping it. See if making the UITabBarController the root view controller makes a difference. [/quote] Thanks for pointing that out 🙏 Yes, I'm aware that I've run into broken navigation logic. I'm sure the bug is on my end. Still, I posted here because I couldn't reproduce it in the clean project and submit feedback to Apple about the unexpected broken layout of the share sheet. After all, the share sheet is Apple's own UI, and we don't control its layout – so, it seems to me, this shouldn't happen in the first place.

The same problem on Xcode 26.3 NSInternalInconsistencyException event dispatch <_MPRemoteCommandEventDispatch: <MPRemoteCommandEvent: 0x1305584e0 commandID=0DFE0944-77A1-4FCA-89ED-F82DA8F3C0B2 command=<MPRemoteCommand: 0x11a96ecb0 type=Play (0) enabled=YES handlers=[0x11ba2bde0]> sourceID=SenderDevice = <iPhone>, SenderBundleIdentifier = <com.apple.MediaRemoteUI>, SenderPID = <9154> ((null))> state:201> deallocated without calling continuation userInfo: { NSAssertFile = "_MPRemoteCommandEventDispatch.m"; NSAssertLine = 39; } Crashed: Thread 0 CoreFoundation __exceptionPreprocess + 164 1 libobjc.A.dylib objc_exception_throw + 88 2 Foundation _userInfoForFileAndLine + 0 3 MediaPlayer -[_MPRemoteCommandEventDispatch dealloc] + 144 4 CoreFoundation -[__NSArrayI_Transfer dealloc] + 84 5 libobjc.A.dylib AutoreleasePoolPage::releaseUntil(objc_object**) + 204 6 libobjc.A.dylib objc_autoreleasePoolPop + 244 7 CoreFoundation _CFAutoreleasePoolPop + 32 8 CoreFoundation __CFRunLoopPerCalloutARPEnd + 48 9 CoreFoundation __CFRunLoopRun + 1976 10 CoreFoundation _CFRunLoopRunSpecificWithOptions + 532 11 GraphicsServices GSEventRunModal + 120 12 UIKitCore -[UIApplication _run] + 792 13 UIKitCore UIApplicationMain + 336 14 MyApp static AppLauncher.launch(appDelegateClass:) + 156 (AppLauncher.swift:9) 15 MyApp main + 16 (main.swift:17) 16 (Missing) (Missing)

@DTS Engineer Ok, I followed your steps and discovered something interesting 🤓 Since my project is quite large, I initially decided to move and run the test code directly in the AppDelegate’s application(_:didFinishLaunchingWithOptions:) method. And it works! Even the UIApplication.shared.setAlternateIconName() method works as well. final class AppDelegate: UIResponder, UIApplicationDelegate { func application( _ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]? ) -> Bool { Task { _ = try! await URLSession.shared.allTasks try! await UIApplication.shared.setAlternateIconName(...) } } } Another unexplained curious thing I noticed is that after making these API calls in AppDelegate, my original code starts to work 😳 I'll provide some more information about my project, in case it helps. My project uses a modular architecture, and I use Tuist to generate the .xcodeproj and .xcworkspace files. The code that's causing the crash is located in a SwiftPM package. Additionally, the allTasks code is in one package, while setAlternateIconName() is in another. Tuist generates subprojects with statically linked frameworks from these SwiftPM packages.

@DTS Engineer thank you for your prompt response 🙏 I have macOS 15.5 and Xcode 16.4. I repeated your steps: Created a new project; Implemented the same button with the same action. Everything works fine. Moreover, all of the APIs listed above work well in other projects. It’s definitely something specific to my project. Unfortunately, I have no idea what’s causing the issue or what I need to do next.

After upgrading to Xcode 16, I have experienced some issues with the compilation time of my project. I noticed that a new step has been added called "Scan dependencies of", which was not present in Xcode 15. Additionally, there is a new CompileAssetCatalogVariant step. The ValidateEmbeddedBinary step has started to take ~15 seconds, compared to about 5 seconds in Xcode 15. I would appreciate any recommendations on what I can do with that information 🙏