Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Former Member
4 years agoUnable to Save New Logins Firefox
Won't save new login. I don't frequently need to save new logins, so unclear how often/long this is an issue--but definitely not the smooth flow I expect.
See screenshot:
1Password Version: 8.9.7
Extension Version: 2.4.7
OS Version: macOS 12.6
Browser:_ Firefox 105.0.3
15 Replies
- ag_mike_d
1Password Team
Hello all,
Thanks for your messages here. I'm sorry for the troubles you've been encountering. For those that are not aware, we're looking further into this issue further and I've included each user's details where necessary.
Currently, we've had word that locking and unlocking the extension or app helps, but can also suggest removing the
Betaextension from your browser and install theProductionrelease, to help while the team investigates.Your patience is appreciated.
ref: dev/core/core#17386
- jschusslerNew Contributor
Piling on. This is really a drag....
- FedupDedicated Contributor
I ditched the beta extension from all my browsers. It has too many issues and support has yet to reply to my thread from 2 weeks ago. Luckily I was able to revert back to the non beta extension and my issues disappeared.
- Former Member
I reported the same problem although with Firefox on Windows.
https://1password.community/discussion/133409/clicking-on-suggested-password-does-nothingStill no fix :(
- OlivierPDedicated Contributor
Hello,
the 1Password's Extension beta seems to lost communication capabilities after a while...
Same issue as mentioned here :
- https://1password.community/discussion/134625/issue-not-able-to-save-new-logins-in-chrome-based-browsers#latest
- https://1password.community/discussion/134108/icloud-com-no-autofill-possible-for-apple-id#latest
- https://1password.community/discussion/134174/not-able-to-save-new-logins-in-vivaldi#latestWaiting for a reply and/or fix from the team...
The workaround is to lock and then unlock 1P: it will then work for some little time.
Alternatively: Switch back to the production version of the extension (it works in this one).