“Visual Studio Maui IOS”

Same here. Updated xcode & simulator yesterday and out of sudden ios apps when started show a white screen for seconds before the main application screen (i.e. a splashscreen) appears. Added print() to trace but it looks the delay happens not in user code. Looks like loading libs during the startup process takes ages before user code starts running.

So the only workaround would be for me an iBeacon put in the car - powered on while driving. There IOS recognices and is able to wake up the app - is this correct. Any examples how to? Thanks Robert

Additional information The app was developed using Unity. After contacting Unity, they indicated that based on the crash logs, it is highly likely that a “Segmentation Fault” occurred. I suspect the “Segmentation Fault” is caused by insufficient memory, but is it possible that memory usage has increased significantly in iOS 26.4 compared to previous OS versions?

I’m experiencing the same issue on my end. Can’t test with iOS 26.3 anymore, but it works as expected on iOS 18.7.2 and macOS 15.7.4. On iOS 26.4 I’m not receiving any remote notifications, so updates are only fetched when I relaunch the app. Using CKSyncEngine under the hood.

Thank you very much for your time. The issue is still unresolved. I tried using the Instruments memory tool and enabled malloc scribble, but unfortunately, the crash has not been reproduced yet. By the way, there is a crash on the iOS 26 system, and the crash stacks for iOS 26, 18, and 17 are the same as the ones I sent earlier. I noticed that on systems below iOS 17, the crash stack has changed to a different form, and the crash occurs in [AXSpeechThread main] (in libAXSpeechManager.dylib). I have attached the crashes for iOS 26 and iOS 16. Could you please provide guidance? iOS16-AXSpeechThread-Crash.txt iOS26-crash.txt

OK by this: I tried deleting iOS 18 runtime via Xcode Settings > Components, and even removed iOS 26 runtime then re-downloaded it. But the iOS 18 runtime keeps auto-reappearing right after! I also ran sudo rm -rf against the iOS 18 asset folder, and it just throws a permission error—totally useless. I checked the Info.plist under /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime/cc1f035290d244fca4f74d9d243fcd02d2876c27.asset/ and confirmed this folder is exactly the orphaned iOS 18.0 simulator runtime. I’m trying to delete this specific cc1f035290d244fca4f74d9d243fcd02d2876c27.asset folder but hit a wall with system permissions. I found this exact issue is already being discussed in the Apple Developer Forum thread here: Orphaned 9GB Simulator Runtime in /System/Library/AssetsV2 - Cannot Delete (SIP protected). It’s clearly a bug on Apple’s side with MobileAsset lifecycle management—these large orphaned simulator runtime assets get stuck in SIP

Thanks for the post. Unfortunately, there is no direct, programmatic way within the iOS SDK to automatically wake or launch your app specifically when the iPhone connects to CarPlay or a standard car Bluetooth system. Its important to mention your app is completely sandboxed from knowing anything about the CarPlay lifecycle. As a user, you can create a shortcut on your device. Open the Shortcuts app and go to the Automation tab. Tap + and select CarPlay or Bluetooth and select. The menu could be a little different. Set it to Connects and choose Run Immediately so it doesn't ask for permission every time like shortcuts do. For the action, they can select Open App and choose the app you want to run on the iOS device. Hope that give you an idea. I hope people do not provide you with ideas using Core Motion or Core Location to wake your app in the background when the user starts moving in a vehicle. It is advisable to avoid those options due to the potential issues they may cause. Albert
  Worl

All apps should build with the latest SDK, so you have access to the latest APIs, regardless of the distribution mechanism used. Regarding the UIDesignRequiresCompatibility questions, it's useful to see how this was described in the WWDC25 Platforms State of the Union: As you evaluate your app's UI and the time you need to adopt the new design, we're providing an option to continue to use your app's current design with Xcode 26. We intend this option to be removed in the next major release. Hopefully you're on your way with the adoption of the new design already, or have upcoming plans to tackle it. You'll have to look at your own specific situations and determine how long you can continue using it for specific hot fix situations against the above statements and the timing of your own planned adoption of the new design. What are the potential issues if a team continues development on Xcode 16 while others have migrated to Xcode 26? For example, could there be compatibility, build, or integration challenges in