Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Pixel 10 Pro Issues
I recently switched from an iPhone 16 to a Pixel 10 Pro and am experiencing significant functionality issues with 1Password that need to be addressed. The autofill feature is consistently unreliable. In Chrome, username and password autofill succeeds roughly half the time. When automatic filling fails, I have to manually click and hold to select "Autofill," which still frequently doesn't populate the form fields correctly. This forces me to open the 1Password app and manually copy credentials multiple times per day, which is both inefficient and frustrating. Native app integration has similar problems. Login functionality is inconsistent at best, and browser-based authentication within apps rarely works (I've had it succeed perhaps once since switching devices). Passkey functionality is particularly problematic. 1Password consistently fails to recognize available passkeys across multiple sites. This is reproducible every time I attempt to authenticate on Microsoft's website, where the passkey option simply doesn't function. Additionally, OTP codes still require manual copying and pasting rather than seamless integration. I've been a loyal 1Password user for years without experiencing these issues on iOS. The Android performance gap is substantial enough that it's affecting my daily workflow and making me reconsider the platform entirely. Could you please confirm whether your team is aware of these Android-specific issues and provide an estimated timeline for fixes? I need to understand if these problems are being actively addressed or if I should evaluate alternative solutions. I appreciate your time and look forward to your response.
AutoFill Fail Android
What was the final resolution to the inoperability of AutoFill when using android? I have been experiencing this issue for months. It does not occur on other mobile devices or desktop apps. I have tried the suggestions in this forum to no avail. If it is still unresolved are there vulnerabilities being exposed and short as we talk further precautions until it is resoled
Feature Request: Register for the otpauth:// scheme in Android app
Android permits applications to handle intents for the otpauth:// URI scheme. Bitwarden and Red Hat's FreeOTP use this to add 2FA secrets to credentials. When combined with Circle to Search (or pasting a URI into the Android Launcher), it makes it much easier to add 2FA secrets on the same device. For example, here's a generated version of Google's classic example (otpauth://totp/Example:alice@google.com?secret=JBSWY3DPEHPK3PXP&issuer=Example): Circle To Search provides the following suggestion which can be handled by various apps: This is Bitwarden's flow: Here's the https://github.com/freeotp/freeotp-android/blob/3cff613a1b11f48877849d9724c99627492c603f/mobile/src/main/AndroidManifest.xml#L51-L63.
Bring Back the Standalone Password Generator in Android – Not Just Hidden in Login Creation
Hello 1Password team and fellow users, I'd like to revisit a long-standing feature request that I’ve found repeated in several older threads — but never fully addressed: the ability to use the password generator independently in the Android app, without being forced to create a new login item first. I’ve seen past posts where this was requested , and most responses follow a pattern: Users didn’t realize the password generator appears during login creation. A moderator kindly explains how to trigger it by creating a new item. The user says thanks, and the thread ends. However, that’s not the whole story. Many of us — myself included — already know this workaround. But the problem isn’t ignorance — it’s that it’s a poor user experience. In real-world usage, we often encounter modern and fragmented sign-up processes: Email-first → verify → redirected to create password SMS-based onboarding → password setup comes much later Multi-step captchas, in-app flows, or jumping between tabs or apps These flows don’t align neatly with creating a login item upfront. We often need a password generator midway through a process, without any context where a login makes sense yet. And faking a dummy item just to access the generator feels like a workaround that no longer fits the sophistication of 1Password’s overall design. Yes, there are third-party password generators online — but I’ve come to really trust and rely on 1Password’s generator and its history tracking, like in the browser extension. It’s streamlined, consistent, and secure — everything a good UX should be. All I’m asking is for 1Password to bring that same level of elegance and independence to the Android app. A standalone generator (like on desktop and browser) would make the mobile experience complete — and remove a daily point of friction for many loyal users. What do you think? Have you run into similar situations where the current flow just doesn't work well? Would a dedicated password generator make your Android experience smoother? Let’s hear your thoughts — I’d love to know how widespread this frustration is, and whether others would support this idea as well.
Unable to create and save a passkey in Costco android app
I am getting the error message when trying to create a passkey in the Costco android app on my Samsung S22 Ultra phone: "Unable to save passkey. For security reasons, 1Password did not save this passkey. The associated URL for this passkey does not match the selected app."Bulk-ignore weak password warnings
I appreciate the "ignore" feature for weak password warnings (some valid reasons for using it are listed here and there are some more here), but it appears that it's only possible to mark these warnings "ignored" for a single item at a time. It would be helpful to be able to select a batch of items and ignore the "weak password" warning for all of them at once.
Trouble with Bank of America app
Greetings all, I'm having trouble with my Bank of America app, in that, 1Password won't auto load into it, except every once and a while. ( Every once and while, password will load, after a failed attempt to auto load the username.) And if I try to copy and paste from 1Password, I can copy either the username or the password, but after pasting one of those, when I go back to copy and paste the remaining one, the original one I've pasted is gone. What's frustrating is, that at least once in the past, both the username and password auto loaded as expected. I'm using an Android S23 FE. Thanks.
