Protect what matters – even after you're gone. Make a plan for your digital legacy today.
How to use Passkeys on Temp Device
If i made a passkey for some site on my phone, lets say github, and then I needed to log into github from someone else's computer, there's a way to do that. you click passkey on different device, then it generates a QR code that you scan with your phone, then my phone asks for a thumbprint or my PIN and then i click yes and the site logs in. not my favorite user flow, but it exists and it works now lets assume instead that my github passkey is in 1password. my 1password is not on the device that i need to log in on. how do i log into github now? since 1password works pretty different on PC and on Android, if the answer is different i'd like both.
App freezes after fingerprint on S26 Ultra (One UI 8.5)
System Information: Device: Samsung Galaxy S26 Ultra OS: One UI 8.5 (Android 16) security patch 2026-02-05 1Password Version: 8.12.6 & 8.12.8 Description: The 1Password app freezes/hangs immediately after a successful biometric (fingerprint) or device passcode authentication when opening the app directly. Key Findings & Troubleshooting: Autofill Works: The "Autofill" service works perfectly with biometrics. The issue only occurs when opening the 1Password app UI itself. Animation Conflict: The app works normally only when "Remove animations" is enabled in Android Accessibility settings. If system animations are on, the app deadlocks after the biometric prompt disappears. Regression Check: I have another S23 Ultra running 1Password 8.12.4 (on an older One UI version) which works flawlessly. Steps to Reproduce: Open 1Password app on S26 Ultra (One UI 8.5 security patch 2026-02-05). Authenticate via fingerprint. The biometric dialog disappears, but the app UI remains frozen and unresponsive.
[Bug] "Title" field triggers password input, disabling non-English keyboards
Environment: App Version: 8.12.8 BETA OS: Android 16, OneUI 8.0 Keyboard: Gboard Description: When creating or editing a Login item in the 1Password Android app, tapping the "Title" field incorrectly triggers Gboard's strict password mode. Because Android handles password fields with extreme strictness, this forces the keyboard into an English-only QWERTY layout and completely disables the ability to use other language inputs (such as Chinese Pinyin). This is clearly an unintentional inputType configuration bug rather than a deliberate privacy feature. Tapping the "Username" field directly below it correctly triggers a standard incognito text mode (similar to Chrome incognito tabs). The Username field protects privacy by preventing dictionary learning, but still respects the user's active keyboard language and allows normal typing. The Title field should behave exactly the same way. Steps to Reproduce: Open the 1Password Android app and tap to add a new Login item (or edit an existing one). Tap into the Title text field. Observe: Gboard switches to a strict password layout (disallowing language switching or non-QWERTY input). Tap into the Username text field. Observe: Gboard switches to a standard incognito layout, safely preventing dictionary learning while still allowing language switching and normal typing. Technical Context & Suggested Fix: The "Title" field appears to be incorrectly assigned an inputType of TYPE_TEXT_VARIATION_PASSWORD (or similar). The "Username" field is already using the correct implementation—likely utilizing IME_FLAG_NO_PERSONALIZED_LEARNING combined with a standard text class. The Title field needs to be updated to match the Username field's configuration so international users can type vault item names in their native languages without being locked into English QWERTY. Impact: This causes severe friction for non-English users or anyone utilizing a multilingual keyboard setup, as it makes typing native-language titles for vault items incredibly frustrating or impossible without external workarounds.Collection resets randomly in 1Password for Android
On Android it does happen most of the time, but not always. I have selected a collection. Whenever I have to enter my account password to the-login to 1P, and often also after the automatic locking of the app, the whole account is selected instead of my previously chosen collection. The steps are mainly Open the 1P app Select the collection Leave the phone alone for some time, e.g. some minutes or hours Open and unlock the app again The collection is not selected anymore
What Setting Controls a Log In every 14 days?
Hello and good afternoon, Periodically my laptop or phone asks for my password sign in every 14 days-in addition to each sign in for each use daily. I checked my permissions, which are "balanced." I've looked in vain to adjust it or turn it off. I'm not even sure how to accurately describe it in a topic sentence. Any guidance on help articles or settings is appreciated. Thank you.
Search shortcut via "Items"
There's a small, but annoying interaction for me when using the app. I always click on "items" (down on the screen) to search for a password. I then need bring my hand up to click up into the search and then bring my hands down again to type. I would really love it if clicking the "Items" menu item at the bottom would focus the search if you were already in that tab. So i could keep my hands on the bottom the whole time and go right into the search. It seems natural to me. First click on "Items" brings up the tab and then second click will focus on the search. I know it's a small thing, but i would really improve my experience as a user. Thank you.
Apply passkeys even if the app name isn't a perfect match
I don't think it's a technical limitation, but let me know if I'm mistaken. 1password refuses to use passkeys on apps that don't fully match the name and signature of the app where the passkey was created, which makes zero sense to me. I have certain apps that share the same user account and I also frequently use modified APKs for convenience. I understand the security risks related to using a passkey on a modded app, for example, but this seems like something the user should have control over. Just display a warning and allow to override it if needed. 1password should be making the decision of where I do or do not apply my credentials.