You’re now watching this thread. If you’ve opted in to email or web notifications, you’ll be notified when there’s activity. Click again to stop watching or visit your profile to manage watched threads and notifications.
You’ve stopped watching this thread and will no longer receive emails or web notifications when there’s activity. Click again to start watching.
Hello,
Since the first iOS 15 beta and even with all the next public releases, we have a very weird crash each time our app enters background.
The crash logs don't help at all unfortunately
But no other info.
We can't reproduce it on simulators or on real devices with non-production release (linked to Xcode).
But the crashes are here each time we build a release version.
Any help would be appreciated!
NB: it seems similar to this one but we are not even sure
Many of you in this thread have opened bug reports in Feedback Assistant — thank you for filing those to help us address this! We have deployed a fix to the backend services that provide crashes for your app into the Xcode Organizer, so if you receive EXC_CRASH (SIGKILL) crash reports from now on through the Organizer, those reports should be attributed with an exception code to explain why the system terminated your app.
If you still see any reports without the exception code, please post the complete crash report to this thread using the attachment feature so we can verify that the code is still missing.
How did you acquire this crash? A system termination (i.e. a SIGKILL initiated by the system) should have an additional reason code or description of the reason behind the termination.
For anyone receiving a system termination (i.e. a Exception Type: EXC_CRASH (SIGKILL)) and also seeing 0x0 in the Exception Codes line, the system should have output additional information useful for diagnosing the reason the system terminated the app, such as the exception codes 0x8badf00d, 0xdead10cc, or 0xbaadca11, as documented in Understanding the Exception Types in a Crash Report.
Please open a bug report using Feedback Assistant, as this information should never be missing from the crash report, and is crucial for identifying the source of the problem. In your bug report, please include the full Apple crash report (no reports from third-party crash reporters), as well as a description of how you received the crash report, such as through the Xcode Crashes Organizer. Once you have filed the bug report, please post the FB number here.
I also have a crash report that looks almost exactly the same. More than that, I have two more different crash reports, but all of them have zero Exception Codes and have no "Termination Reason" field.
In my case in all those crash reports I have a ton of threads that are waiting for some network operations (some Firestore stuff in my app) so my guess is that it can be related to some resource shortage (memory? descriptors? something related to threading?). But that's just a guess, I may very well be wrong.
Since first iOS 15 build we've got a lot of the same crashes. We believe iOS 15 has some regressions. There are too many EXC_CRASH (SIGKILL) without any visible reason.
@edford, I can confirm seeing crash reports with 0x0 exception codes on iOS 15. My guess it is the watchdog killing the app, but I'm not sure. Please see FB9791707.
@edford I am also seeing crash reports with 0x0 exception codes. I have a suspicion a thread other than main is the real culprit, but there's no evidence of that in the report. Please see FB9801972.
I’m also seen SIGKILL crashes with 0x0 exception codes and no termination reason. In this case, looking at the backtraces, it seems that it is originated from core data / cloudkit.
