Feedback ID: FB24937933
I’m seeing a persistent launch failure across multiple unrelated apps on an iPhone 15 Pro Max.
Affected apps include Telegram, Box, LinkedIn, Amazon, Apple Podcasts, Shazam, and others.
The behavior is consistent:
- I launch the app.
- The app stays on a black or frozen launch screen.
- After approximately 19–20 seconds, iOS terminates the app.
- Retrying may occasionally work temporarily, but the problem returns.
Crash reports from multiple unrelated apps show essentially the same termination:
EXC_CRASH / SIGKILL 0x8BADF00D scene-create watchdog transgression
More importantly, the main thread repeatedly shows this pattern:
xpc_connection_send_message_with_reply_sync NSXPCCONNECTION_IS_WAITING_FOR_A_SYNCHRONOUS_REPLY -[__NSURLBackgroundSession setupBackgroundSession] -[__NSURLBackgroundSession initWithConfiguration:delegate:delegateQueue:delegateDispatchQueue:]
This appears to indicate that the app’s main thread is synchronously waiting for an XPC-backed system service while creating a background NSURLSession, and the response does not arrive before the scene-create watchdog timeout.
I first reproduced this on iOS 26.6.2 and the problem still occurs after updating to iOS 27.0 (24A437).
Troubleshooting already performed:
• Force restart • Network Settings Reset • Background App Refresh disabled • VPN/proxy disabled • Affected apps deleted and reinstalled • iOS updated from 26.6.2 to 27.0
Because the same stack pattern is occurring across multiple unrelated third-party apps, as well as Apple apps such as Podcasts and Shazam, this does not appear to be isolated to a single application.
Apple Support has also told me that similar cases have been reported and that the issue may be addressed in a future software update.
Has anyone seen a system-level NSURLBackgroundSession / XPC service enter this kind of stuck state across multiple applications?
Is there a known issue involving the background URLSession service or related networking daemon that could cause synchronous XPC calls during app launch to block until the watchdog terminates the process?
I have submitted the full crash reports through Feedback Assistant under FB24937933.