Forum Discussion
Chrome Canary/Dev: 1Password Extension Not Opening Fully
Hi 1Password Support team,
I'm having an issue where I can open the desktop version of 1Password just fine, but the Chrome extension simply "spins" (hangs with a throbber icon). The extension intro page upon fresh install and the extension Settings page fails to load as well. This also happens with the latest version of the Beta extension for Chrome.
The above of course stops 1Password's browser autofill from working.
Environment:
Device: PC
Windows version: Windows 11 Home 24H2 (Build 26100.4351)
1Password version (desktop): 8.11.0 (81100016)- Nightly channel
Chrome version: 139.0.7241.0 (Official Build) canary (64-bit)
1Password Chrome extension version: 8.11.0.13 - Nightly channel
I do realize that based on my setup this could very well be a Chrome issue but wanted to post here just in case.
Please let me know if I can provide anything else to help troubleshoot, such as logs, etc.
Thanks!
Hello BlindWolf8 and pandaso! 👋
I'm sorry that you're running into an issue when attempting to open 1Password in Chrome. This is a known issue that is currently affecting Chrome Dev and was previously affecting Chrome Canary.
Chrome's development team is aware of the issue and a fix is already being tested in Chrome Canary version 139.0.7244.0. The fix should be released to the future Chrome Dev update soon. For the time being, switching to the stable version of Chrome (or Chrome Canary) is the best workaround.
-Dave
#38288
3 Replies
- 1P_Dave
Moderator
Hello BlindWolf8 and pandaso! 👋
I'm sorry that you're running into an issue when attempting to open 1Password in Chrome. This is a known issue that is currently affecting Chrome Dev and was previously affecting Chrome Canary.
Chrome's development team is aware of the issue and a fix is already being tested in Chrome Canary version 139.0.7244.0. The fix should be released to the future Chrome Dev update soon. For the time being, switching to the stable version of Chrome (or Chrome Canary) is the best workaround.
-Dave
#38288
Hi all,
It seems this is fixed with this combo:
1Password version (desktop): 8.11.0 (81100020)- Nightly channel
Chrome version: 139.0.7245.0 (Official Build) canary (64-bit)
1Password Chrome extension version: 8.11.0.15 - Nightly channelNot sure which update fixed it. I don't think it was Chrome.
This seems to be specifically related to Chromium 139, regardless of the channel. Currently dev and canary are on 139, and both fail. Stable and beta are on 138, which seem to be fine (from a quick check).
Edge canary seems to have similar issues, due to it using Chromium 139. Brave builds seem okay, but that's because they all use 138 (or lower).
