NO_CRASH_STACK

Developer Tools & Services General
gabriel_araujo_spectora OP
Created Aug ’24
Replies 1
Boosts 0
Views 267
Participants 2

Yesterday 08/07/2024 we started to have a lot of NO_CRASH_STACK on our app released trough testflight, the release was created and released on the 07/30/2024 and is widely used by the beta testers. But for some reason this crash started to happen yesterday and we are not sure what the root cause is, we haven't made available any new builds under the same version or something, the only thing we did was to release a new version so the users can update from but it doesn't seem that the crash is happening on this new version only on the one from the 30th. Any idea what could be happening??

Replies  1
Boosts  0
Views  267
Participants  2
DTS Engineer OP
Apple
Aug ’24

This means your app crashed extremely early in its lifecycle, before execution reached your main function. A common culprit here is that your app has initializers that run pre-main. There is still data in the complete crash report that is still useful. If you right click on the crash and show it in Finder, you can navigate down into the Xcode crash point bundle and dig out the raw crash report file. Once you do so, please post it here — Posting a Crash Report explains how to do so.

—Ed Ford,  DTS Engineer

0
NO_CRASH_STACK
First post date Last post date
 
 
Q