[Customer] Mobile User was logged out AGAIN when being in the train

[hoangdat]

Description

User was logged out AGAIN when being in the train

Expected result

User was not logged out, even if no network.

• In case of no network, should keep the refreshToken and try again
• In case of error 500 with /refreshToken, should keep the refreshToken and try again
• In case of interceptor, try to improve error handling for interceptor

Current behavior

Sometimes app still be disconnected.

Cc @chibenwa

[chibenwa]

If an unexpected error happens during the refresh we can likely also to a red error toast to the user.

[chibenwa]

Please also describe precisely the error handling we have when refreshing the access token.

[dab246]

If an unexpected error happens during the refresh we can likely also to a red error toast to the user.

Currently, if it's not a 401 error, we'll toast the error message to the user.

[dab246]

Please also describe precisely the error handling we have when refreshing the access token.

When the request has a 401 error, the call the refresh token function to get a new token.

When the refresh token function has an error ServerError (500) or TemporarilyUnavailable (503), then show a toast to notify the user of the error, otherwise log in again

[chibenwa]

I was logged out AGAIN whe being in the train
v 0.19.13
I remind you this is MU top priority
Protip: If refreshing tokens fails because of bad network, toast a red error, and retry on next iteration
Can you please create an issue on this and staff someone on it?

Another remark: in case of logout because of 401 can't we remember that we are on prem, and the guy mail address? Then we also simplify a lot the user flow in case logout still happen, and avoid the 'use company server' page.