I’m running a development build with script debugging enabled.
On an iPhone 5 it loads and runs no problem.
iPhone 4 after the loading screen is done (the Unity splashscreen) the game shuts down immediately, sometimes it shuts down very shortly after displaying a bit of the game world, no errors or warning messages displayed whatsoever, even xcode doesn’t report anything.
How can I track the source of this bug or at least trace it?
Edit: I have confirmed all the scripts execute once including an update and fixed update, so where else could it be going wrong?
1 Answer
1
Try flagging “Development Build” when exporting to get a more verbose output through the xcode debugger. Inspect the output from xcode, there is not such thing as not output whatsoever - the problem is that you probably have to look at the output log quite carefully as it is spammed by hundreds of system messages and sometimes it is easy to miss errors. Try filtering the output to /Unity or /Dalvik.
And something a bit more focused - I had the same problem where my game would run fine on windows and iPad, but would crash on iPhone4. Apparently it was a null ref, which was not handled very gracefully on iOS but for some reason was squelched on windows and did not crash on iPad. Might be a paid, but try looking for null refs, if you’re using MonoDevelop you can toggle breakpoint on exception ( I think it’s under Run → Exceptions ), so you can try seeing if there are any exceptions which don’t get logged.
Yep have it flagged as development and I explored the log in excruciating detail, absolutely nothing. I set a script to run first and one to run last printing out for updated/fixed updates and starts and they both literally ran once for each before it crashed otu. Whatever is going wrong is going wrong after the first update routine... maybe during the rendering phase?
– chillypacman