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
There is one case where this is more than "nice-to-have":
Steps to reproduce:
A device was online and the user is experiencing the app
He locks the device
He reactivates the devices and network-access is not immediately available (e.g. searching for wifi)
A scheduled, non-user-initiated network-request occurs
Actual behavior
The devices immediately displays an error screen, cause the network connection could not be established
Expected behavior
The app should detect a network error which suggests that it might be temporary and suspend going into an error state until a user-initiated-action occurs.
Activity
luhmann commentedon Sep 18, 2017
There is one case where this is more than "nice-to-have":
Steps to reproduce:
Actual behavior
Expected behavior
luhmann commentedon Sep 19, 2017
Consider also creating a retry logic, for status codes > 500 ... issue is likely temporarily and should not require user interaction.