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
Comments
-
This is happening to me too
Phone: Samsung S23 Ultra
Andriod: 14
OneUI: 6.0
1Password App: 8.10.270 -
Yeah It's still happening to me, too. It's kinda random now. Every once in a while, it happens.
0 -
I'm sorry that the issue continues to disrupt your use of 1Password. Our developers are continuing to investigate here on our end but I don't have an update to provide at the moment.
Thank you for reporting the issue and I'm sorry for the disruption to you as well. So that I can confirm that you're affected by the same issue that is being discussed in this thread, I'd like to ask you to create a diagnostics report from your Android device:
Sending Diagnostics Reports (Android)
Attach the diagnostics to an email message addressed to
support+forum@1password.com
.With your email please include:
- A link to this thread: https://1password.community/discussion/comment/707281/#Comment_707281
- Your forum username:
gavy
- Please do not post your diagnostic report to the forum. This is for your privacy and security.
Please send the entire file.
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!
-Dave
ref: dev/core/core#27518
0 -
I'm experiencing this issue randomly where my phone gets stuck on the 1Password splash screen when trying to unlock it.
This started happening when updated from Android 13 to Android 14
Phone: Poco F4 GT
Android: 14
1Password App: 8.10.321 -
Same after the update that fixed the crashing.
https://1password.community/discussion/comment/710319#Comment_710319
0 -
I'm sorry that you're also sometimes unable to unlock 1Password. I'd like to ask you to create a diagnostics report from your Android device:
Sending Diagnostics Reports (Android)
Attach the diagnostics to an email message addressed to
support+forum@1password.com
.With your email please include:
- A link to this thread: https://1password.community/discussion/comment/710711/#Comment_710711
- Your forum username:
ialexsilva
- Please do not post your diagnostic report to the forum. This is for your privacy and security.
Please send the entire file.
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!
I've replied to you here: https://1password.community/discussion/comment/711209/#Comment_711209
-Dave
0 -
Same/similar issue on pixel 8 pro
WUV-29323-725
1 -
Same issue, Pixel 6 Pro.
FQH-44137-838
0 -
Thank you for sending in the diagnostics reports. I see that the team was able to review the diagnostics reports and identify a known issue. Hopefully our development team is able to include a fix for the issue in a future update soon.
I'm sorry for the inconvenience.
-Dave
ref: dev/core/core#27518
0 -
This is happening for me as well. Pixel 8 pro. Very frustrating. Is there a resolution? Thank you
0 -
I also sent in a diagnostic. This has been happening to me for months - is there any progress on narrowing this down? I also recently updated to Android 15 Beta 3 and that did not resolve the issue, unfortunately.
0 -
This has been happening for months to me too. Pixel 6 Pro, Android 14.
0 -
@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).
0 -
@EnerJi I noticed it was fixed in beta. I'm running that for now until it's fixed in prod.
0 -
Same problem here.
Sent diagnostics. Got this code:
RXX-89911-521
Joining Beta0 -
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
0 -
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?
1 -
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.
1 -
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?
0 -
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.
0 -
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,
-- Brendan0 -
This content has been removed.