Recently we've started to see crash reports with the following:
Exception Type: 00000020
Exception Codes: 0x000000008badf00d
Exception Note: SIMULATED (this is NOT a crash)
Highlighted by Thread: 0
Application Specific Information:
com.mycompany.myapp failed to scene-update after 10.00s
These crash reports are coming from iOS devices being used by our users 'out in the wild'.
I've dealt with crash reports with failed to scene-update
before (usually just some process taking too long that is called from a system callback that shouldn't block), but I've not seen either SIMULATED (this is NOT a crash)
or Highlighted by Thread
before.
Does anyone know exactly what these new bits of information mean? Do they simply refer to the failed to scene-update
issue or do they convey any additional meaning. Also does anyone know if there are other possible values for Exception Note
?
Your iPhone hides away a list of app crashes. The Analytics Data section keeps a list of app crashes. You can tap on any of them to see more details about what happened.
Tombstone crash logs are written when a native crash in C/C++ code occurs in an Android application. The Android platform writes a trace of all the running threads at the time of the crash to /data/tombstones, along with additional information for debugging, such as information about memory and open files.
Understanding a Crash ReportHead to your Game Panel and to the left, press FTP File Access and log in. Once in FTP File Access, you will see a folder named `crash-reports`. Go ahead and click that. Looking inside of that directory you will notice a file or multiple files.
According to Apple (see the Tech Notes under Other Exception Types), the exception code 8badf00d
means
the application took too long to launch, terminate, or respond to system events.
Also it is suggested that whatever is on Thread 0
should be moved to a background thread.
Now in regards to Exception Note: SIMULATED (this is NOT a crash)
, iOS won't crash your app if you're running with a debugger and/or in a simulator, therefore it gives you the hint that the app is running SIMULATED
and this is NOT a crash
. But you should review the part that causes the warning as your app will most likely be terminated if it blocks the main thread for too long.
From Apple's developer website.
If this field contains SIMULATED (this is NOT a crash) then the process did not crash, but was killed at the request of the system, typically the watchdog.
Understanding and Analyzing Application Crash Reports (developer.apple.com)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With