I am not sure where to place this question, so i thought here since there is where the issue seems to lie. During app review, clearly the reviewers run the app though rougher scenarios, for example with 100% packet loss via Link Conditioner. So my app is working very well but i want to but protection in place, using Reachability and prudent checks.
This is one area i am finding little information one: general best practices for protection of connection issues.
So my general question here is: does anyone have useful url's or thoughts? Thus far i have:
- dropped in Reachability,
- added general calls to quickly check current status,
- activated notification of connection changes, stored in appDelegate, and internal notifications passed out to listeners,
- wrapping each possible call out to the cloud with layers of protection,
- Trying my best to protect where things are "black-boxed" (ie using Parse)...
This is all just a matter of walking all the code to protect it. What i am hoping to learn is general thoughts on how to ensure no submission rejection:
- when to allow an app to attempt connectiing forever, as seen in many apps. Am i correct in thinking this is ok, so long as your "back" button is responsive?
- when to inform users of a lack of connection? To what level. I am guessing there is no exactly correct answer here. Some methods are critical and if the connection fails or times out, failure must be displayed.
- when is it apropriate to push a static viewcontroller to the forefront to stop the app from continuing?
here i was thinking of implementing a static counter and 3 successive failures occur, stop the app? Seems arbitrary though.
It would be great to see clear Apple specs on this, and they likely exist, i simply have not found them as yet.