I’m seeing what looks very similar to Feedback ID FB24937933 on an iPhone 12 Pro Max running iOS 27.0.1. The two apps I can reproduce it most consistently with are Robinhood Banking 2.23.1 and Duolingo 7.142.0. Symptoms App opens to the splash/logo screen and hangs. After roughly 20 seconds, iOS kills it. Robinhood Banking briefly worked after forcing a sign-out and reauthentication, then the problem returned. Most other apps now work normally. Timeline I was on a Caribbean cruise Sept. 27–Oct. 2, including Jamaica and the Bahamas. I used ship Wi-Fi and different networks while in port. Robinhood Banking was still working while I was in the Bahamas. The issue started the day I got back, Oct. 2. At first, App Store updates were also hanging and not starting. Troubleshooting already done Normal restart and force restart Airplane Mode Wi-Fi only / cellular only Multiple unrelated Wi-Fi networks Separate mobile hotspot DNS changes, then back to Automatic No VPN Private Relay / Limit IP Address Tracking disabled for testing Checked app/location permissions Freed storage Fully deleted and reinstalled the affected apps Signed out/in where possible Reset network settings OTA iOS update attempted, but it sat on “Update Requested” for hours Updated successfully to iOS 27.0.1 through Windows Robinhood confirmed there is no account restriction Removed old trusted devices and fully reauthenticated Regular Robinhood works normally and the physical card still works Crash logs Both apps are being terminated with EXC_CRASH / SIGKILL / 0x8BADF00D. Robinhood shows a scene-create watchdog timeout after about 20 seconds. Duolingo’s watchdog event is slightly different, but the important part is that both apps’ main threads are blocked in the same path while iOS is setting up a background NSURLSession and waiting for a synchronous XPC response. That common stack across two unrelated apps is what makes this look system-level rather than app-specific. At this point I’ve reproduced it across different networks, after reinstalling the apps, after reauthentication, after a network reset, and after updating iOS through a computer. The cruise may be unrelated, but it’s the only major change immediately before this started. Has anyone found a way to reset or restart whatever iOS service handles background NSURLSession/XPC traffic without erasing the phone?