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
When opening the android app (v1.1.4) while the app is not able to connect to the server (either because the phone is on a network which can not reach the groceries server and even if the phone is in airplane mod) the app tries to "Log in" for up to 60 seconds until the "Login offline" screen appears.
Waiting or up to 60 seconds before being able to log in is quite a lot of time if you are in the store and want to check the grocery list.
How to Reproduce
Install android app v.1.1.4
Connect to a server
Close the app (kill it)
Change network or set phone in airplane mode
Open the app
Wait up to 60 seconds before being able to continue offline (sometimes it is faster)
Expected Behavior
I would expect that the app knows way sooner that it isn't able to connect to the server (maybe after 3-5 seconds at most) and offers the user to work offline.
The text was updated successfully, but these errors were encountered:
Sorry for the delay...
Having trouble reproducing on my device -- what device are you using?
I'm trying to put some more debugging into the next release so I could get debug logs out of the android app and not just the web version.
Issue
When opening the android app (v1.1.4) while the app is not able to connect to the server (either because the phone is on a network which can not reach the groceries server and even if the phone is in airplane mod) the app tries to "Log in" for up to 60 seconds until the "Login offline" screen appears.
Waiting or up to 60 seconds before being able to log in is quite a lot of time if you are in the store and want to check the grocery list.
How to Reproduce
Expected Behavior
I would expect that the app knows way sooner that it isn't able to connect to the server (maybe after 3-5 seconds at most) and offers the user to work offline.
The text was updated successfully, but these errors were encountered: