Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Network Error Handling #2

Open
shivshav opened this issue Sep 16, 2015 · 0 comments
Open

Network Error Handling #2

shivshav opened this issue Sep 16, 2015 · 0 comments

Comments

@shivshav
Copy link
Owner

How should we react when we get an error?

  • Retrofit
    • Network
      • Timeout, pi not running, etc.
    • Http (status code != 2xx)
      • Unauthorized, not found, server error, etc.
    • 'ParseError'
      • Unable to parse response from network

What do we do with the subscription? (See Below)

* Cancel it?
* Resume?
* Exponential backoff? Then what?
* Move to "off mode" interval?

When do we alert the user?

After the first failure.

  • Alert the user with a Snack bar message
    • Snackbar action will be "Retry"
      • If user interacts, we go to exponential backoff until we hit "off" mode, then go to retry and wait
      • Else, flip FAB to "Refresh/Retry" button and wait

What do we set the bottom toolbar to?

  • Mode
    • "Technical Difficulties"
    • "NETWORK UNAVAILABLE"
    • "SOUS VIDE NOT FOUND"
  • Dialogbox?
    • Maybe after the retry(see above)
    • "Unable to connect. Please make sure the sous vide is running"
  • FAB
    • Make into refresh/retry button(?)
@shivshav shivshav added this to the 1.0 Release milestone Sep 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant