Mobile Developer Checklist
Suggest a change
Thank you for helping us improve the quality of Unity Documentation. Although we cannot accept all submissions, we do read each suggested change from our users and will make updates where applicable.
For some reason your suggested change could not be submitted. Please try again in a few minutes. And thank you for taking the time to help us improve the quality of Unity Documentation.
Checklist for crashes
- Disable code stripping (and set “slow with exceptions” for iOS)
- Follow the instructions on Optimizing the Size of the Built iOS Player (iphone-playerSizeOptimization) to make sure your game does not crash with stripping on iOS.
- Verify it is not because of out of memory (restart your device, use the device with maximum RAM for the platform, be sure to watch the logs)
Editor.log - on the editor
The Debug messages, warnings and errors all go to the console. Also Unity prints status reports to the console - loading assets, initializing mono, graphics driver info.
If you are trying to understand what is going on look at the editor.log. Here you will get the full picture, not just a console fragment. You can try to understand what’s happening, and watch the full log of your coding session. This will help you track down what has caused Unity crash to crash or find out what’s wrong with your assets.
Unity prints some things on the devices as well; Logcat console for android and Xcode gdb console on iOS devices
Debugging on Android
- Use the DDMS or ADB tool
- Watch the stacktrace (Android 3 or newer). Either use c++filt (part of the ndk) or the other methods, like: http://slush.warosu.org/c++filtjs to decode the mangled function calls
- Look at the .so file that the crash occurs on:
libunity.so - the crash is in the Unity code or the user code
libdvm.so - the crash is in the Java world, somewhere with Dalvik. So find Dalvik’s stacktrace, look at your JNI code or anything Java-related (including your possible changes to the AndroidManifest.xml).
libmono.so - either a Mono bug or you’re doing something Mono strongly dislikes
- If the crashlog does not help you can disassemble it to get a rough understanding of what has happened.
- use ARM EABI tools from the Android NDK like this: objdump.exe -S libmono.so >> out.txt
- Look at the code around pc from the stacktrace.
- try to match that code within the fresh out.txt file.
- Scroll up to understand what is happening in the function it occurs in.
Debugging on iOS
Xcode has built in tools. Xcode 4 has a really nice GUI for debugging crashes, Xcode 3 has less.
Full gdb stack - thread backtrace all
Enable development build and script debugging. Now uncaught null ref exceptions will be printed to the Xcode console with the appropriate managed call stack.
Try turning the “fast script call” and code stripping off. It may stop some random crashes, like those caused by using some rare .Net functions or reflection.
- Try to figure out which script the crash happens in and debug it using mono develop on the device.
- If the crash seems to not be in your code, take a closer look at the stacktrace, there should be a hint of something happening. Take a copy and submit it, and we’ll take a look.
Mobile Developer Checklist