EXC_BAD_ACCESS (SIGABRT), ios crash log

Question

I have some problem with my iPhone/ipad app. its published in app store, but now it seems like a few users experiences crashes when they try to start the app. Sometimes it h

Answer 1

EXC_BAD_ACCESS is thrown when something at scripting level gone wrong (e.g. null reference exception, but could be any other exception).

I've developed an in-game dev console where I forward all the debug logs thrown by Unity and our scripts (see the nice callback Unity offers http://docs.unity3d.com/Documentation/ScriptReference/Application.LogCallback.html).

Building the game as a Development Build (check build settings), Symlinking the Unity libraries and also checking script debugging if you need to, you can try to reproduce the steps that got your app to crash for some users. This way, it won't crash on iOS when an exception occurs.

Take a look at this DebugConsole implementation, which can be integrated really fast (despite you need some minor changes to forward Unity Logs too) and can do the job for you: https://gist.github.com/darktable/1412228

In our dev builds we no longer get a crash unless our app abuses memory. Even in that case you can track what happend.