EXC_BAD_ACCESS (SIGABRT), ios crash log

。_饼干妹妹 提交于 2019-11-30 22:02:23

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.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!