You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 19, 2020. It is now read-only.
a. should retry a few times
b. then fall back to case 1
No location provider
a. should cause a "no location provider available message"
b. should check for a location provider every time we request it
c. should show the previous temp if available and pretend the world is flat? (discuss!)
d. should we use Play Services only (pros: setup a min distance before triggering an update, cons: less devices, maybe)? (discuss!)
e. optionally to d., should we migrate to Android-LocationHub (tests needed)? (discuss!)
No location available
a. should be protected by "no location provider available" (see 3)
b. should use the previous location? (discuss!)
The text was updated successfully, but these errors were encountered:
Let's discuss a little bit all the foreseeable source of errors we currently have/handle/don't give a f---.
No network: should cause "no network available" (or disregard if a previous value is available, discuss!)
Poor network / connection timeouts / network f---up
a. should retry a few times
b. then fall back to case 1
No location provider
a. should cause a "no location provider available message"
b. should check for a location provider every time we request it
c. should show the previous temp if available and pretend the world is flat? (discuss!)
d. should we use Play Services only (pros: setup a min distance before triggering an update, cons: less devices, maybe)? (discuss!)
e. optionally to d., should we migrate to Android-LocationHub (tests needed)? (discuss!)
No location available
a. should be protected by "no location provider available" (see 3)
b. should use the previous location? (discuss!)
The text was updated successfully, but these errors were encountered: