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
Hi @elfenlied, sorry about the filling issues that you're seeing. I have a few questions:
Looking forward to your response!
Thanks for your reply.
When it happens, it happens on all websites.
I couldn't notice a specific action/condition that triggers it.
NordVPN via the Chrome extension, on and off, but mostly off.
@elfenlied thanks for those details. Can you create a new user profile in Chrome, install only 1Password in it, and then test to see if that makes a difference? If NordVPN is installed outside of Chrome, can you make sure to disable it and then test how things go with that as well? I look forward to hearing from you again.
@Joy_1P, done, no problem in the new user profile so far.
Also, no problem in two other profiles (I use four profiles in total, including the new empty one I just created).
I also noticed something: I can fix the problem by disabling/re-enabling 1P's extension.
@elfenlied thanks for testing things out in the new browser profile. It sounds like there may be a conflict with another browser extension, which is causing 1Password to not work properly. Depending on the other browser extension, disabling/re-enabling 1Password may help temporarily.
Could you add the extensions that you have in the original profile with the issue to your new profile? Please add them one by one and test 1Password with each to see which one results in autofill not working. I suspect that the issue is with your NordVPN extension or uBlock Origin.
I am having the same issue. I use Chrome within Wavebox.
Other 1password functions also get broken. Like getting the message 'unable to save item'.
It happens at least once a day. Chrome restart temporarily resolves these issues.
For me disabling/re-enabling 1Password does not resolve these issues.
Hey @bmesnard, I'm sorry to hear about the issues that you're encountering. The "unable to save item" error indicates that the extension is unable to sync with our servers to save your logins. Could you try the following to re-sync your account and see if that will help?
If you use the 1Password desktop app on your computer, please go back and re-enable "Integrate with 1Password app". If you do not use the 1Password desktop app, then please leave it off.
After that, please test things out by saving a new login. If there are still issues, please let us know the following:
I look forward to hearing from you.
Just a couple of details.
Right clicking on the 1Password presents the same panel as left clicking.
There is no 'Settings' visible on that panel.
'Settings...' is visible after clicking on the hamburger icon to the right of the search field.
Clicking Settings displays the Settings panel.
I do not use the 1Password desktop app.
I have disabled the app integration.
I'm not sure this will resolve the recurring issue where 1Password seems to just stop working. Credentials fields when logging in to a website are no longer recognized and the 1Password icon is not displayed. Autofill also stops working.
The only way I've found to fix this is to restart Wavebox.
This seems to happen at least once a day with both PCs and Macs.
I confirm I have the same issue. The extension was working fine until 2.7.0. This is when issues started. Basically, the extension just stops working. I can see my vault but trying to go into settings doesn't work. Autofill also stops working when in this state. I have to disable and re-enable the extension to solve the issue. This is a temporary fix as the extension will stop working again. The issue used to happen less frequently in 2.7.0. It's worst in 2.8.1. This is using Chrome 110 on a chromebook
Hey @bmesnard, @slajuene,
I'm sorry for the trouble. I think at this point it would be helpful if we could take a closer look at some logs and what may be going wrong. Could you please send over the followring:
Please attach the reports to an email message addressed to
[email protected]with a link to this thread.
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!
Ok! I'll do this the next time the issues occur.
Continually broken on Chrome for many weeks, but you're going to respond as if this is a big surprise?
Your instructions for attaching a console log don't work - file type not allowed.
Hi @jpawlicki, I'm very sorry that you've encountered an issue with filling in Chrome. Because everyone's setup is different, we have to look at each user's case individually. That means we'll sometimes repeat our questions or comments. That doesn't mean we are not paying attention. It's the opposite -- we ask because we need to know more about the issue on your end in order to help you get to a solution.
I do see that you've attached a screenshot of your logs in this thread. Before we dig into the logs, could you let us know the following:
Do you have the 1Password desktop app installed? If so, what version are you using?
What version of Chrome and the extension do you have running?
Do you have any other extensions in Chrome?
Do you use an antivirus, proxy, or VPN?
Please reach out to us at [email protected] with the details above. It would be easier to communicate via email so that we can go over account specific things if they come up. If you send an email, make sure to include a link to this thread as well as your username. After the email is sent, you'll get an automated reply with a Support ID. Please post that here so we can locate your ticket and ensure that it gets a prompt response.
I disabled uBlock Origin and did not experience the 1P bug since then.
A few days later I got a new macbook with a fresh install of macOS, on which I replicated my Chrome profile with the same extensions (1Password, Google Docs Offline, Loom, NordVPN, Return YouTube Dislike, uBlock Origin, Vue.js devtools). And I haven't experienced the 1P bug so far on the new macbook (despite having uBlock Origin enabled).
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.
@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.
@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:
As for the extension console log, I do see that we asked for it to be sent to us at [email protected] 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.
Issues recurred today.
Console log sent.
I am having similar issues as mentioned in this thread:
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.
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.
Hey @sl7123, could you right-click on the 1Password icon in your browser's toolbar, select Settings, and let us know the following:
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 [email protected] With your email please include:
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks!
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.