Issue with Browser Extension: Multiple Passwords Required
I use the 1password browser extension for Arc Browser, but it is essentially from the Chrome Web Store. I ran into a problem recently where I need to put in password for 1password extension multiple times to unlock it.
I was able to capture each step:
1) This is what it looks like after I had already input password once. This is the second time I saw this.2) This is after I put in password in the first screenshot (1). There was still a lock next to the little icon in the email box still, clicking that and this is what popped up.3) THEN, this is after I had put in the password after screenshot (2).4) After (3), you can still see that the icon has a lock next to it still. After this attempt, the 1password extension has finally been unlocked.This issue occurs inconsistently. Sometimes it only took me once or twice. This example is definitely close to the maximum number of tries I've experienced so far. Relatively new issue–I'll say it started about 2-3 weeks ago. Before then, it worked seamlessly.
I'd really appreciate if anyone can point to where the issue might come from. I can't certainly rule out that the browser is not the source of the bug, but I'm unsure.
Hardware & Software versions:
- MacBook Pro 14-inch, 2021
- macOS: Sequoia 15.4.1
- Arc Version 1.91.2 (62278)
- Chromium Engine Version 135.0.7049.116
- 1Password for Mac Version 8.10.74
- 1Password Extension version 8.10.72.27
Hello rpornmon! 👋
I'm sorry that you're running into issues when unlocking 1Password using your account password. As a start, can you make sure that the 1Password desktop app is set to run in the background on your Mac:
- Open and unlock 1Password for Mac.
- Click on 1Password next to the Apple logo in the menu bar.
- Click Settings.
- Make sure that "Keep 1Password in the menu bar" is turned on.
If the option was already turned on, or you still see the issue after turning it on, then do you happen to run any other Chromium browsers on your Mac such as Chrome or Microsoft Edge? If you do then do you see the same issue there?-Dave