no connection response at startup of app..

Question

Created Jul ’15

Replies 3

Boosts 0

Participants 3

Hoping to mitigate a potential app rejection: I have noted some disparity in how the startup of an app that is missing a required net connection reacts. I have also read that Apple does not want us to exit an app directly as it looks like a crash. But to render an app in a view that says "hey, we need the net" and forcing them to swipe-kill seems less friendly than a good UIAlertView with a note about this, with the tap of Ok leading to the app closing.

Anyone know if this latter route is a sure-fire rejection?

Answered by chuckc192000 in 29175022

Apps should ONLY close by tapping the Home button.

Boost

Answer 1

KMT OP

Jul ’15

If they need the 'net, and they don't have the 'net, and the alert reminds them, and when they make that happen your app still tanks, yes, that sounds ripe for rejection, 'cause of course a bandaid doesn't make it all 'betta.

0

Answer 2

wdcurry OP

Jul ’15

Thanks KMT, perhaps i misunderstood your thoughts, but an alertView stating the requirements with an ok to close the app doesn't indicate the app tanking. In fact is feels more controlled. I guess it could lead to a "tap here when the net is back" alert which cycles back to itself if the net is not truly there, but i don't know. Given the former is on the store, perhap i will just go that route even though i do not like it. One less submission worry. cheers.

0

Answer 3

chuckc192000 OP

Jul ’15

Accepted Answer

Apps should ONLY close by tapping the Home button.

0