Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
Autofill freeze after unlock
I noticed that it began happening recently. Basically if I unlock my phone, go to a website and try using the autofill, what happens is:
- I select the credential
- The app asks for unlock (biometric)
- After that, the unlock screen fades (but the website in the background still shows with that dark shade as if the unlock dialog was still open)
- I'm stuck like this, so I need to hit the back button (android)
- Then I can select the credential (since now it's unlocked)
I'm adding a video showing it happening, the part when it's black is the unlock (biometric), and when I'm tapping around it's because the biometric has already succeeded but I can't do anything but hit the back button.
I'm on a S23 Ultra (One UI 6)
App is up to date on beta (8.10.24)
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Android 14
Browser: Brave
For me android app freezes after just touching the search bar. I have Samsung and Motorola phones running on Android 14. Both apps have these issues for last 2 weeks. I am on 1Password version 8.10.36
BrendanR1P1Password Team
Just to let everyone who was encountering this issue know, the fix for this issue was released in the latest update to the 1Password for Android app, as mentioned in the release notes on the following link - https://releases.1password.com/android/8.10/#1password-for-android-8.10.36
Thanks,
-- Brendan- 1P_Tommy
Moderator
No, there are no sure fire ways to get yourself into the situation that I am aware of. Apologies, I had gone off of a comment in our tracker that seems to mention two similar paths which may or may not be related. The current resolution the team issued may help. We're awaiting any feedback you and the other may have.
You can certainly reinstall if needed. Just take appropriate precautions and ensure you have your Secret Key and know your password. I would recommend continuing the conversation with the technical team if any issues are encountered. They may need new logs from you.
get yourself into this situation
That seems to suggest that wiping the app and fresh installing should solve it. Are there any ways one can get back into the broken state that are easy to do, or are they things like "upgrade the OS" or "migrate the app data from an old phone"?
So far 8.10.36 is working well for me, but if the issue cross up again, is a hard reinstall a fairly durable solution?
- 1P_Tommy
It looks like there was a couple of ways to get yourself into this situation and one of the latest releases (yesterday) should have helped. There are a couple of edge cases that continue to be worked on. Stay vigilant and let us know if you happen to experience the issue again.
It seems based on my initial testing that this is fixed in 8.10.36 that was just released. Is that the case or did I just get lucky?
- 1P_Tommy
I see you've been talking with one of my email colleagues. We look forward to continuing the conversation with you via email.
ref: RXX-89911-521
Same problem here.
Sent diagnostics. Got this code:
RXX-89911-521
Joining BetaEnerJi I noticed it was fixed in beta. I'm running that for now until it's fixed in prod.
mackid1993 I got a reply from support that it's fixed in beta and will roll out to stable at some point. I was also suggested a temporary workaround is to clear my app data (careful - ensure any recent changes have synced to the cloud and that you have your emergency kit or another logged in device available before you clear data or you won't be able to log in again).
