>>I always wonder about this crazy stuff when I go to release soon.<<
Me too.
When this happens on a mac/pc, I can get debug logs, I can dial in, I can root about.
Nothing similar on an iPad.
I suppose if it actually crashed, I might get a crash log. But it isn’t crashing, just stopping.
Leaves me feeling very out of control …
[import]uid: 108660 topic_id: 24156 reply_id: 98818[/import]
Tell the customer with the black screen to reboot (completely power down and back up) their iPad. Hold the “Home” and “Sleep/Wake” buttons down at the same time for a couple of seconds, then slide the red “Slide to power off” button. Then press the “Sleep/Wake” button by itself to power back up.
I haven’t had to do this at all since 5.1, but it was an occasional problem with various games with earlier versions of iOS. The customer may still be running an older version of the operating system.
Good luck!
[import]uid: 5540 topic_id: 24156 reply_id: 98827[/import]
I finally tracked this down, and of course the issue was my code.
It took a helpful customer to tell me step by step what they had done.
One button in the app attempted to create a non-essential file.
If the file existed at startup, the contents were used, if not, the app used internal defaults.
Only some of the folk using the app have ever used the button.
And the NEXT time they use the app, it dies because the file was malformed.
On first install, everything works, so it was near impossible to to duplicate, as I could go to any machine and demonstrate it started properly.
Very luckily, this file is created in the Documents folder AND I have exposed that through iTunes, so my workaround is simply to delete the corrupted file.
I’ve uploaded a fixed version to Apple.
Mystery solved.
[import]uid: 108660 topic_id: 24156 reply_id: 99016[/import]
It’s so great to hear you nailed it. Your perseverance prevailed!
Naomi [import]uid: 67217 topic_id: 24156 reply_id: 99029[/import]