This just started happening when I upgraded to 3.0.0f1 from the one before it (I think it was 3.0.0b7, I’ve grabbed every update as soon as available).
So I can build and run in the target via Xcode, and it works fine. However if I try to run it standalone, I get the splash screen for the usual amount of time, and then instant death, back to the app icons.
I’ve tried fully shutting the device down, fully uninstalling the app from the device, to no avail.
A bit frazzling. Anyway, any similar experiences? If not already known, I wonder how I can help get it fixed. it’s especially odd that it runs fine via the debugger and dies when standalone. How the heck to debug such an issue.
Whatever the glitch, it went away when I disabled Decompress On Load for a music clip (shouldn’t have been enabled to begin with). It also reduced the load time appreciably. I suspect that the long load time isn’t well tolerated by something, though not sure why this particular Unity release.
Yep you are right. There is a built in timeout in iOS which will terminate any app that is unresponsive for a period of time at start-up. This is a safety measure to catch apps that have locked up or take too long to load and leave the device unresponsive.
You’re best bet is to load into an empty unity scene (which will be plenty fast), then from that scene do your main load (the one that takes the most time) straight away after that.
This way the app will boot up into its run loop fast ( so won’t be killed by the iOS ) and you can still load all the content you need.