No Crash stack logs

No Crash stack logs

There’s a variety of potential causes for this. Please post a complete crash report, per the instructions in Posting a Crash Report.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

We're experiencing thousands of NO_CRASH_LOG crashes like the one described in this thread. This all started with iOS 15 release. When you open a .crash file it shows just a couple of dyld calls and then EXC_CORPSE_NOTIFY with a system watchdog killing the app during launch after 1 minute of inactivity. Binary images section only contains .dyld and sometimes a few other system .dylib-s - no modules from our app. I'm attaching an example here? I filed a bug to Apple via feedback.apple.com, but they replied that they need system logs from affected devices, which we cannot provide because the issue (according to the Apple's Xcode reporting system) happens on our AppStore users devices, but we can't reproduce it by ourselves. My radar is still in "open" status bus since then there hasn't been any activity. I know that a lot of people also reporting this, and there're also a lot of forum discussions, eg this one: https://developer.apple.com/forums/thread/690514 Does anybody have an answer for this?

Consider this:

Termination Reason: FRONTBOARD 2343432205 

2343432205 is decimal for 0x8badf00d, which is the marker for a watchdog crash report. For general background on such crash reports, see Addressing Watchdog Terminations.

In this specific case something has gone very wrong during your app’s startup sequence. IMO this is unlikely to be your fault. Consider this:

Date/Time:           2022-07-24 11:09:56.9474 -0500
Launch Time:         2022-07-24 11:08:54.1708 -0500

You died roughly 60 seconds after starting. And this:

"Elapsed total CPU time (seconds): 199.610 (user 199.610, system 0.000), 55% CPU",
"Elapsed application CPU time (seconds): 0.506, 0% CPU"

During that 60 seconds of wall clock time something used almost 200 seconds of CPU time. So the CPU is super busy. However, that something is not your application, which only got 0.5 seconds of CPU time.

I suspect that something on the user’s phone is borked and your app is just caught up in the cross fire. To learn more you’d need to get a sysdiagnose log from an affected device taken shortly after the crash occurred, which is going to be a challenge.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

UPDATE: after iOS 16 came out, presumably due to the users updating to it from earlier versions, the number of these odd crashes gradually reduced to almost zero now.