Skip to content

Intermittent issue with user/pass not being saved when entering 2FA code #3614

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

Open
misaochan opened this issue Mar 31, 2020 · 4 comments
Open
Labels

Comments

@misaochan
Copy link
Member

misaochan commented Mar 31, 2020

I received a report of an issue from a 2FA user with v2.12.3 of the app. This problem happens occasionally for her when she tries to log in with 2FA:

  1. Enter username and password
  2. App prompts you for 2FA code
  3. When you copy the 2FA code and come back to the app, the username and password is empty, requiring you to type them all over again while the 2FA timer is ticking

I have not managed to reproduce this personally, but if anyone can, please let us know how you managed it!

@misaochan misaochan added the bug label Mar 31, 2020
@sivaraam
Copy link
Member

I have a hunch that this could be happening when Android kicks the app out of memory due to low memory. I'm not very sure though.

@misaochan Can you ask the device model of that user? It might be helpful. If possible, also ask them if the phone was under memory pressure (which would hopefully be apparent by noticeable lag when coming back to the app) when they faced this issue.

@macgills
Copy link
Contributor

macgills commented Apr 6, 2020

It definitely sounds like the activity was recreated and we do not persist the state but I quickly experimented with do not keep activities turned on and my uname/pass were persisted across recreation. There must be something happening with the 2FA flow? I do not have it enabled

@misaochan
Copy link
Member Author

misaochan commented Apr 6, 2020

The user's response was: "I have a Samsung S7 Edge. No I did not notice any freeze or anything: what does happen is the keyboard of the Commons app stays visible."

So I don't think the device model is likely to be a problem - the S7 Edge is a slightly older model, but still well within the mid-range as far as specs go, so it should have enough memory for this purpose IMO?

@misaochan
Copy link
Member Author

It definitely sounds like the activity was recreated and we do not persist the state but I quickly experimented with do not keep activities turned on and my uname/pass were persisted across recreation. There must be something happening with the 2FA flow? I do not have it enabled

I rotated my device, which resulted in the activity being recreated - the username and password are persisted for me, although the 2FA code field disappears so you have to tap "Login" again for it to come back up. But that isn't a big problem and not what the user is experiencing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants