Open adamwolf opened 6 years ago
@dreeves not sure what to label this as. thoughts?
Good question. It's a potential bug and the first step is easy so let's try labeling it BUG and PEA.
User got bit by this this week.
We do not handle 401 or unauthorized responses after login in a user-facing way.
A user ran into this again today.
This has been happening to a good handful of users in the last month or two.
The iOS app appears not to suffer from this. Upon successful login, the api token is persisted locally and used for subsequent api calls.
As far as I know, the token is not reset by changing password in the web interface.
(Might be worth checking out how the app handles the case that the cached api token no longer is valid, when the user resets it in the webapp. Re: iOS app)
I am not sure the app shows any sort of error when the user resets their password and doesn't change it in Beeminder.
From dup gissue:
Replicata
TODO