Firstly wanted to introduce myself - i'm new to the site and am currently set to submit my first app for review.
A couple of issues I've encountered of which one I identified during testing on the simulator and the device.
Its to do with the Default.png. Basically it loads intermittently. It always loads on the very first start up of the app, but afterwards very briefly sometimes and not at all others. Has anyone seen this issue before?
Also, the project, a soundboard is 45MB and i'm aware it has to be 20MB max. It has 46 sounds and some graphics but thats it, how are people getting the size down?
Firstly wanted to introduce myself - i'm new to the site and am currently set to submit my first app for review.
A couple of issues I've encountered of which one I identified during testing on the simulator and the device.
Its to do with the Default.png. Basically it loads intermittently. It always loads on the very first start up of the app, but afterwards very briefly sometimes and not at all others. Has anyone seen this issue before?
Also, the project, a soundboard is 45MB and i'm aware it has to be 20MB max. It has 46 sounds and some graphics but thats it, how are people getting the size down?
Many thanks for your help guys.
Your app only has to be < 20MB to be downloadable over 3G. Anything above will require a WiFi connection or iTunes to download. As to your other issue, I'm not really sure.
Your app only has to be < 20MB to be downloadable over 3G. Anything above will require a WiFi connection or iTunes to download. As to your other issue, I'm not really sure.
Ah, I see.
What have people found to be the best solution for the splash screen situation. From what I've read issues with the default are common. Thanks Kalimba, much appreciated.
Excellent point. With fast app switching, your app just resumes where it last left off, so you won't see the Default.png splash screen.
Can you verify that when you don't see the splash screen, the app appears to be resuming (IOW, it is not launching)?
I think thats exactly right. I wondered if I wasnt closing memory down somewhere as when I come out of the app I return to the last point I left. Is this a straight forward resolve?
I think thats exactly right. I wondered if I wasnt closing memory down somewhere as when I come out of the app I return to the last point I left. Is this a straight forward resolve?
It sounds like your app is working as they (Apple) wanted it to, so it's probably not an issue. Scratch one bug off your TODO list!
Yeah, I suspected that. Your app will resume rather than restart if the device has it in memory still. Not something you really need to worry about, or care about unless you don't want it to do it (log-in details app etc).
I think thats exactly right. I wondered if I wasnt closing memory down somewhere as when I come out of the app I return to the last point I left. Is this a straight forward resolve?
If for some reason you must display the splash screen every time, you'll either have to modify your app to display the image over the top of the screen (e.g., in a UIImageView) when your app resumes foreground execution, or you can force it to stop supporting fast app switching altogether (see "Opting Out of Background Execution" in the iOS Application Programming Guide).
You should think really carefully before doing either of these, though, unless you have a really compelling reason. Like the others said, it's desired functionality -- the fast app switching was added in 4.0 precisely to allow users to jump back and forth between apps without losing their place. Forcing them to wait for your branding material to disappear every time they want to jump back to the app probably won't accomplish much besides annoying your users.
I think i'd rather it loaded the splash screen each time and would probably adjust with a quick fix but if its not an 'official' bug at least I know its not an issue I need to address.
The only other thing I seem to have as an issue is that some of the soundboard sounds are louder or quieter than the others. Can this be fixed in the code or does it need to be sorted with the sounds themselves?
If for some reason you must display the splash screen every time, you'll either have to modify your app to display the image over the top of the screen (e.g., in a UIImageView) when your app resumes foreground execution, or you can force it to stop supporting fast app switching altogether (see "Opting Out of Background Execution" in the iOS Application Programming Guide).
You should think really carefully before doing either of these, though, unless you have a really compelling reason. Like the others said, it's desired functionality -- the fast app switching was added in 4.0 precisely to allow users to jump back and forth between apps without losing their place. Forcing them to wait for your branding material to disappear every time they want to jump back to the app probably won't accomplish much besides annoying your users.
I see the reasoning behind it and it makes a lot of sense. It just felt somehow like the memory wasnt closing properly but as you and others have said, its how Apple want it so thats fine. Thank you.