Skip to main content
June 17, 2022
Question

Unable to auto-fill generated passwords

  • June 17, 2022
  • 43 replies
  • 3397 views
  1. When a form asks me to "create password" I can see the 1Password dropdown with a suggested password, but clicking that item does nothing (see screenshot 1).
  2. If I go into the Chrome extension and try to copy the generated password, I get an error saying unable to save generated password (see screenshot 2).



1Password Version: 8.7.1
Extension Version: 2.3.5
OS Version: macOS 12.4 (21F79)

43 replies

June 26, 2022

Facing same problem. Just started using 1password. Anyone can help?

I am using Mozilla Browser 101.0.1

I wasn't trying to create any new account, but rather changing password of an existing account, but the problem is same.

August 25, 2022

Same problem here, using the Chrome extension. This feature has never worked for me in 1Password 8 (after several months of use). I've tried it on multiple Windows computers.

Same behavior as reported above ("Use Suggested Password" does nothing and the Copy button says "Unable to save generated password").

August 29, 2022

Same, on Firefox Nightly 106.0a1 (2022-08-26) (64-bit), on Windows 10 Build 19044. Unlike for tmsaylor (above), this feature has worked for me before, although I hadn't tried it in the past few months.

Interestingly, it worked without issue when I signed up for an account on the 1Password forums just now! I may have restarted 1Password after the last failure; it's difficult to tell. (The relevant site's change-password page had some unrelated fun bugs that I initially misattributed to 1Password misbehaving.)

Jack_P_1P
1Password Employee
August 30, 2022

Hi @selenography / @tmsaylor / @himanshuk303 / @parekh:

By any chance do you happen to have Travel Mode enabled? Let me know.

Jack

August 30, 2022

Nope! Travel Mode is not on, and I'm pretty sure it never has been.

Jack_P_1P
1Password Employee
August 30, 2022

Hi @selenography:

Thanks for checking! In that case, I'd like to ask you to create a console log from 1Password in your browser: Save a console log for 1Password in your browser

Please email it to support+x@1password.com, and include a link to this thread: https://1password.community/discussion/130930/unable-to-auto-fill-generated-passwords#latest as well as your username selenography. After emailing in, you'll receive a reply from BitBot with a support ID that looks like [#ABC-12345-678]. Post that here and I'll be able to locate your email and make sure it's made it to the right place. Thanks!

Jack

August 30, 2022

Oh wow. Yes, in my case travel mode is indeed on (seen by signing into my account on the 1Password website). I didn't even realize I had that enabled. Disabling it solved this problem for me! Thanks @Jack_P_1P! Probably still a bug, since my vault is marked safe for travel, but easy to work around in my case.

Jack_P_1P
1Password Employee
August 30, 2022

Hi @tmsaylor:

1Password in the browser stores your password history (including the site they're generated on) in a hidden vault, so that they're available across all your devices. As it currently stands, that hidden vault is never marked as safe for travel, so 1Password in the browser is unable to save newly generated passwords to that hidden vault. This is something we're continuing to discuss internally, but for the time being, generating a password in 1Password in the browser requires Travel Mode to be disabled.

Jack

August 30, 2022

@Jack_P_1P I see, thanks for the explanation. Just thinking about that scenario... It's probably better in that case to skip the hidden vault but otherwise proceed. The other option would be to not auto-suggest passwords in that case, but when manually generating passwords, to allow the "Copy" button to work (bypassing the hidden vault there as well) rather than giving a confusing error.

In my case, I can just disable travel mode.

August 30, 2022

@Jack_P_1P : Unfortunately, I've restarted and updated Firefox since then — the logs for that incident are gone. I was also unable to reproduce the behavior upon revisiting the site.

I'll keep this in mind, though, and should be able to capture logs if and when it happens again.