Hey everyone, running into a brutal crash/freezing loop on WhatsApp for iOS and need some technical advice.
The app UI displays, but all touch interactions inside the app are dead. iOS system UI (Control Center, notifications, app switcher) works perfectly.
The issue started immediately after I received \~100+ media messages in a group. iPhone 16 Pro, iOS 26.6, WhatsApp 26.33.73.
Troubleshooting I've already tried (none worked):
* Offload & reinstall via Settings
* Updated to the latest version from the App Store
* Full device restart
* Exited the problematic group and cleared its media from the linked macOS app
* Airplane mode launch with a 10+ minute wait
* Background App Refresh and cellular data disabled before launch
The macOS desktop app works perfectly and stays in sync. Notifications still arrive on the phone, but tapping them opens the app into the same frozen state.
The constraint: I have \~20 GB of unsynced local chat history on this device. I cannot delete the app or risk a full wipe.
What the logs show:
I pulled the .ips crash report from Analytics data and watched Console during launch. iOS kills WhatsApp with SIGKILL after "Failed to terminate gracefully after 5.0s". The main thread is parked in `__DISPATCH_WAIT_FOR_QUEUE__` inside a Core Data fetch:
`-[NSManagedObjectContext executeFetchRequest:error:]`
`-[NSPersistentStoreCoordinator _routeHeavyweightBlock:]`
A few frames down: `WAMediaIsStreamable` and `WAStreamingMediaKeyForFileHash`. Plus 511 threads on `net.whatsapp.sidecar_async`, all waiting on the same queue. So the main thread is stuck on a heavyweight Core Data fetch tied to media, and the watchdog kills the app.
After the offload + reinstall, Console added a new failure:
`container_create_or_lookup_app_group_path_by_app_group_identifier: client is not entitled`
`Application context data is nil`
`Couldn't read values in CFPrefsPlistSource (Domain: group.net.whatsapp.WhatsApp.shared) ... detaching from cfprefsd`
My reading: the reinstall broke the entitlement link to the existing App Group container, so the fresh binary can't open the old database at all.
A friend in the same group got the same media flood and his WhatsApp works fine. He has \~25 GB, so it's not purely a database size issue.
What I'm looking for: advanced, non-destructive recovery methods. Specifically:
- Has anyone recovered from "client is not entitled" on an App Group container without deleting the app?
- Deep cache/database clearing tricks, background process tricks, or Siri/URL schemes to force-open a specific, non-frozen screen?
- If I delete and reinstall, does iOS ever preserve the App Group container? Pretty sure the answer is no, but I want confirmation before I nuke 20 GB.