Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Former Member
3 years ago1Password Android app exits immediately after Login on Android UpsideDownCake (Android 14)
Since we installed the Android UpsideDownCake update, the 1Password app on our two PIxel 4a 5G phones consistently exits immediately after we input the UserID/Password, or Fingerprint to login to the app. I understand that the problem may well reside within the beta Andoid update, but it does have a catastrophic effect on out ability to use 1Password on those devices, and others may want to be forewarned that there is an issue.
1Password Version: 8.10.4
Extension Version: Not Provided
OS Version: Android UpsideDownCake
Browser:_ Not Provided
14 Replies
- GreyM1P
1Password Team
@ResolutePixel – You're welcome! :)
- Former Member
Wow! Awesome! I didn't even know that was there. That's perfect. Thank you
- GreyM1P
1Password Team
@ResolutePixel
Our Development team have written a fix for that particular bug and it'll hopefully be published soon. Sorry about that!
In the meantime, you could change your autofill suggestions to appear below the form, rather than on the keyboard, which may help:
- Open and unlock 1Password.
- Tap the account/collection icon in the top-right corner.
- Tap Settings > Autofill.
- Tap "Display autofill prompts", then select "Below the fields they relate to".
- Former Member
Just got an update to one password on the Google Play store I'm still on Android 14 beta but now where my microphone icon is on my gboard keyboard. I have the one password icon on everything so it overrides my ability to dictate anything. I have to turn one password off for passwords in the settings to be able to use dictation
- GreyM1P
1Password Team
@ResolutePixel – Thanks for checking this, and yes, we can confirm that auto-fill works in Chrome in Android 14 Beta 3. :)
- Former Member
Hey everyone just installed the latest beta update and 1 password is now auto filling in Chrome now!!
- Former Member
Another update. One password was working earlier today on Chrome and then I just noticed a minute ago it wasn't. So I checked my ringtone and phone notification screen and they're separated again. Seems to be some sort of linkage between that it seems but it shouldn't considering. One is for ringtones and notification volumes the others for chrome directly
- Former Member
So interesting starting yesterday while I was driving home I was getting Bluetooth crashing and system UI crashing I went to restart my phone and it never came back up for over an hour The one thing I noticed today after it was doing it again and I rebooted my phone that one password now fills everything in on Chrome Yay!
But strangely the one reason I installed this Android 14 beta was to have the separated ringtone and notification volume sliders which are no longer working
- Former Member
Thanks @ResolutePixel and 1P_Timothy It's been all working well for me since the beta update following Anrdoid 14 beta 2. Thanks for the feedback on the issue.
We've been merrily using beta level Android releases for several years, and that was the first time we got a bit burned, at least for a short while.
- 1P_Timothy
Community Manager
Hi @ResolutePixel, thanks for joining the conversation!
The issue referenced above has now been resolved and you should no longer see this crash with current beta or production versions of 1Password for Android.
Thanks for including these details about the filling issue that has emerged with Android 14 beta 2. Hopefully an update from the Chrome or Android teams will be available soon to address this.
For anyone reading through this thread, the Autofill issue appears to be isolated to Chrome while running Android 14 beta 2. So, using another supported browser should allow you to fill as expected.
Let us know if you have any questions or if there's anything we can help with!