Unity iOS Crash Report API Unable to Detect Memory Crashes?

Unity Engine
,
1

I am using Unity’s CrashReport API in order try to recover crash information from users in the wild. I have followed the instructions to change the ENABLE_CUSTOM_CRASH_REPORTER define from 0 to 1 in the CrashReporter.h file in the XCode project.

I have been able to use the API to successfully recover reports for NullReferenceExceptions. However, when I purposely caused a memory crash (using our debug menu), the API seemed to be unable to detect that this crash happened.

Is this a known limitation of the Unity CrashReport API? It would be nice if Unity could support saving reports for memory crashes.

2

Yes, this is a known limitation. Crash reporting relies on the fact that application is notified by OS that something bad has happened and it will crash, but in the case of too high memory consumption iOS just kills it, so there’s no way to catch it.

3

And even Xcode doesn’t get proper notification about that. It just seem that someone pressed stop in xcode, instead of NOT ENOUGH MEMORY TO RUN YOUR APP message which would really be helpful.