For anyone facing a similar issue, we found that the crash logs were not helpful. They were both misleading and lacked the necessary detail to diagnose the problem. To uncover the actual cause, we had to connect a user's personal device to Xcode and inspect the console directly. This revealed the true error, which was not captured in the standard crash reports. There really needs to be a better mechanism for users to securely share these logs with developers in cases like this, without requiring direct access to their device. In our case, the console logs indicated that corrupted data stored in the Keychain was causing the app to crash when accessed. Importantly, this had nothing to do with the didFinishLaunchingWithOptions method, despite what the crash logs initially suggested.
Topic:
App Store Distribution & Marketing
SubTopic:
General