Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Can't see the saved credentials for WiFi networks
Hi, I have the following situation: Sometimes I use my smartphone to input the name and the password for one of my WiFi networks in captive portals of some smart home devices. The problem is: I can't see my WiFi networks that I have saved in 1Password. I don't expect autofill here, just the possibility to click to open 1Password and when I search for "wifi", I get as result my networks (all them have "wifi" in their names). Please let me know if you need any screenshots. Thanks,
Still having Android Chrome issues
I'm on 8.11.6 and saw the post earlier this month around the major update to Android+Chrome autofill. I went through all of the settings in the post and it did work for a day or so but it's still broken. I changed to showing the autofill beneath the field and it does show the candidates, but when I tap on a candidate it just goes away and nothing is entered in the text field. I tried disabling autofill and re-enabling using the settings in the post but it doesn't seem to have any effect. I'm happy to provide logs, screenshots, etc to help triage this. Thanks, Derek
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.
Ongoing Autofill Issues on Android
Hi, I've been a long-time user of 1Password, and up until recently, the experience has been excellent. However, for the past few months, the Android experience has significantly deteriorated. Autofill suggestions rarely appear, and when they do, they often fail to work as expected. Most of the time, I have to long-press the input field, select “Autocomplete,” and hope the suggestions show up—which they usually don’t. Even when suggestions do appear, tapping them often results in no action at all. I frequently have to force close Chrome and reopen it just to try again, usually without success. As a result, I now almost always end up copying each field manually from the 1Password app, which is extremely frustrating. I’ve tested this with two different keyboards. My primary keyboard is SwiftKey, where the suggestions fail to appear 90% of the time. Gboard performs slightly better, but even then, tapping suggestions often does nothing. This issue has persisted for months, and it's becoming a serious pain point. I'm honestly beginning to question the value of maintaining a paid subscription if such core functionality continues to be this unreliable. Please look into this—it really needs to be addressed. Thanks.
Autofill not working on Chrome in Android
Starting about a month ago, after 1Password showed a notice that I should set updated autofill on my Android phone to 1Password, which I did, autofill options from 1Password have stopped appearing on log-in pages in Chrome on my phone, except in rare occasion. I've repeated these steps (all settings on my phone were already set correctly, but I toggled everything on and off to replicate the steps) to try to get 1Password autofill working in Chrome again, but there has been no change in the issue I'm experiencing on my phone.
Google's advanced protection
I use 1password and have enabled google's "advanced protection" (https://landing.google.com/intl/en_in/advancedprotection/). I recently attempted to restore my android phone from backup and found it impossible to logon to google without temporarily disabling advanced protection. Note that the restore logon takes place before I have 1password on the device. Google insisted that I use my passkeys which were not on the device. It also had an option to scan a QR code from another device which had the passcode, but I don't know of a way to scan this QR code from 1password. Has 1password thought of supporting this somehow, or is temporarily disabling the advanced protection the preferred solution?
Q re not filling passwords in private tabs
I am not sure if I want to use 1password in private tabs or not. The explanation that if I do, websites will be able to see my browsing history is something I am not sure about. Is this a Security issue or just a privacy issue? What is the real world danger of having 1password work in private tabs? I'm looking for examples of what bad things could happen. I prefer to use private tabs sometimes simply so my browser does not record them, but I use Brave which is very privacy oriented, and also I use Nord VPN so I am wondering if it is really important for me not to use 1password in private tabs on Brave...? I have brave set to clear cache and history on closing as well... So a) do I really need to use Private tabs, and b) do I really need to not use 1password when I do? Thanks for enlightening me on this. I'd like to use 1password on private tabs but do not want to be less secure.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."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.