Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
Former Member
3 years agoAutofill stops working in Chrome until restart of Chrome
Hi,
Autofill in Chrome works normally until it doesn't. When this happens, the suggestion box does not show when I click on text inputs, and clicking "Autofill" from the extension itself does nothing either.
It works again after restarting Chrome.
1Password Version: 8.10.0
Extension Version: 2.7.0
OS Version: macOS 11.7.3
Browser:_ Chrome 110.0.5481.177
26 Replies
- steph_giles
1Password Team
Thanks @sl7123, I see our team are helping you over email.
Let us know if there is anything else we can help with at all.
- Former Member
Hi @Joy_1P,
I still have the "Integrate with 1Password app" setting disabled and I have "Automatically lock 1Password" off under Security.
I did as you asked and sent the console to the support email. The support ID I received in return is: [#YMD-45651-933].Thanks!
- Former Member
Hey @user023875823, the issue that you're experiencing is a bit different, as it is specific to the "Update on reload" setting in Chrome DevTools. This is a known issue, and I've added your post here to the internal ticket that we have opened for it. Hopefully, there will be a fix for this issue in the future.
For now, I recommend turning off the "Update on reload" setting, quitting Chrome completely, and relaunching Chrome. After you do that, you'll be able to use the extension while Chrome DevTools is open.
I hope that helps. If you have any other questions, please let us know.
ref: dev/core/core#20237
- Former Member
Hey @sl7123, could you right-click on the 1Password icon in your browser's toolbar, select Settings, and let us know the following:
- Do you still have the "Integrate with 1Password app" setting disabled?
- Do you have "Automatically lock 1Password" off under Security?
Additionally, please collect your extension console logs for us next time the issue appears: https://support.1password.com/cs/extension-console-log/
Attach the logs to an email message addressed to mailto:support+forum@1password.com. With your email please include:
- A link to this thread: https://1password.community/discussion/comment/681072/#Comment_681072
- Your forum username: sl7123
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks!
- Former Member
I am having similar issues. One thing I noticed today is that when I close the browser and open fresh, the 1password extension works great. When I open the developer tools in chrome, my 1password immediately stops working.
To test this further, I created a new profile, and added the 1password extension, and everything worked great. Then when I open the developer tools, and go to the "Application" tab, and click "Service Workers" and then check the "Update on reload" button, everything stops working for me. Doesn't matter if I uncheck the box, or close developer tools, I just get a blank box with a spinning circle in the middle when I click the extension. Closing the browser fixes the problem, until the developer tools are opened again with "Update on reload" checked.
- Former Member
I am having similar issues as mentioned in this thread:
* I use the 1password extension in Chrome (I believe it is up-to-date the version i Have is 2.8.1)
* I do not have the 1pass desktop application
* Every time I try to save a login within the browser I get "unable to save item"
* Even after I enter it manually, it does not show up in the extension (I have to do the whole sign in and out of my account in order for it to show up)
* I tried to do the steps you said about disabling the integrate with app feature. It still doesn't work.
* I was not able to find if I have 2fa enabled on it.Another issue I often have is that I try to select “use suggested password” and it never fills it in. I end up having to create my own password.
- Former Member
Issues recurred today.
Console log sent. - Former Member
@jpawlicki Thanks for your response.
There can be a bunch of different reasons why filling is not working. For one person, it may be a specific website. For a second person, it may be the interference of another extension. For a third person, it could be their browser permissions. One sweeping fix isn't going to resolve everyone's issue, which is why we have to ask questions and look into everyone's setup separately.
To be clear, there are existing filling issues that exhibit the same behavior and that occur with the same setup. However, in your case, we would need more information to see if that would apply. Here are some of the details we asked about but still do not yet have:
What specific unexpected behavior are you seeing? For example:
-Do you get an error message when trying to fill?
-Does the extension never unlock and does it freeze up?
-Do you have troubles with saving logins or generating passwords?
-Does the issue happen consistently or intermittently (such as after your computer has been idle for some time)?
-Does the issue happen on one specific website or all websites?What version of the extension do you have running?
Do you have any other extensions in Chrome?
As for the extension console log, I do see that we asked for it to be sent to us at mailto:support+forum@1password.com via email. We don't mind for it to be posted in the forum. However, we still need the details above to determine where things are going wrong. If there's anything specific that you had trouble with in regards to collecting the logs, please let us know.
- Former Member
@Joy_1P: Thanks for the very thorough reply. In my case, which I would assume to be about as generic and common as possible: Windows 11 running latest Chrome (111.0.5563.65) and the latest 1Password app available. None of the myriad complicating factors. e.g. VPN, Proxy, etc., that one may wish to point to. While everyone's setup is different, it seems unlikely that you folks wouldn't already be aware of problems with your app on the lowest-common-denominator client out there. Rather than many independent deep dives into specific client setups looking for variables, perhaps more robust testing is indicated.
P.S. Your written instructions re: console log being wrong is not a good sign. - Former Member
Wanted to mention it's been 4 days since the last 1password glitch. Fingers crossed issues are infrequent enough to be a minor annoyance with the 1password beta.