xcode - Testing on Iphone gets stuck on splash screen all of a sudden?

[uncleswell]

Hey.. I've never had this issue before and I'm not sure what could have changed to start making it happen all of a sudden, but I went to go test an app in xcode on my iphone (ios5) and it builds successfully, then loads up on my phone as usual, but never gets passed the "Made with mmf2" splash screen. I've tried with multiple programs, even super simple ones, and old ones that used to work.

I'm still on MMF2DEV(253).
I don't recall making any changes to mmf or xcode that may have caused this, and it is worth mentioning the apps run just fine in the simulators.

Anyone had similar issues, or any advice?

Any help is much appreciated! thanks!

[Anders]

Does this happen if you launch the games directly on the device (not started from XCode)?

[uncleswell]

Yes, But I don't have any apps still installed since before the issue. One app that I know used to work and has not been altered acts in the same manner: stuck at splash screen. Some of the newer testing apps though, when I try to open them on the device online after xcode installed them, they open for a second and then minimize immediately as if having a memory issue.. once I go into the app from the taskbar, it remains stuck on the loading screen....................


Wait a sec, an app that I know used to work and was stuck at the splash screen(loading on device without xcode) while I was typing this message just minimized itself and when I reopened it, it began to work normally. The splash screen stayed on for about 3 or 4 minutes. Either way something weird is certainly happening. I'm going to test transfering apps onto the device via testflight.

Thanks for the input thus far sir!

Any ideas?

[uncleswell]

just tried running another one (very simple & small) standalone on the device (transfered from xcode) and it stuck on the splashscreen for about 2 minutes, then minimized itself, and every time i tried to re-open it, it instantly automatically minimized itself again and again, still on splash screen though.

[Jeff]

Reboot the device maybe?
Sometimes it just takes iOS a long time to load things -- I don't know why.
Once you build a final release build file and send it to the app store it won't be any slower then other apps as far as loading and such.

[AyreGuitar]

It's a long shot, but sometimes the provisioning profiles expire - try updating them through XCode or iPhone Development Portal. I've even had it happen with the Team Provisioning Profile that's supposed to be handled by XCode - but sometimes requires a bit of a hand.

[Anders]

It sounds like your device has some issues. Maybe it would be a good idea to sync it with iTunes and then do a complete device reset.

[uncleswell]

Jeff, you were right. It's just taking an extra long time to load all of a sudden. It takes about 10-15 minutes to move forward from the splash screen when I run MMF apps from xcode now. Very weird.

Andos, that's a difficult thing to think about doing with all the stuff I've got on here, but I might end up giving it a shot if further testing reveals that's what's needed. Thanks for the help.. If either of you run across any other potential solutions, please let me know. Thanks!

[Yuri]

I'm having the same problem ;[

When I run the "analyze" button on xcode, it gives me alot off issues, like "missing self=" and a bunch of others

Is this because i'm using the newer version of xcode for IOS 5?

Does this issues have anything to do with the extra launching time ?

Is this going to repeat at the IOS device, or just the simulator ?

[Anders]

The iOS runtime has been ported to Objective-C from C++ and that is the main reason why the many 'Analyze' warnings.

There are certain coding-guidelines for Objective-C programs that are wise to use when you create a new program from scratch to avoid common pitfalls and oversights when coding.
The iOS runtime being ported from C++ means that we do not follow those guidelines and the analyzer therefore cannot function properly and it can't do much else than give warnings.

Most warnings there come from heavily tested and proven code so don't worry. Those warnings have nothing to do with the launching time. Analyzing is just a tool available to the programmer, it does nothing to the execution of your program.