Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
Former Member
4 years agoSafari extension often loses connection to 1password
Since a while and also with the latest beta release 80400053 my 1password extension for Safari (15.1) often stops working.
It always looks like 1password was locked. When really locked it still redirects me to the 1password app to enter my Passphrase but then it still looks locked in Safari and doesn't even redirect to 1password anymore.
Reloading the page does not work. Clicking aways from the login form and clicking on it again does not help.
Sometimes it helps to deactivate the 1password Safari extension and reactivate it again. But sometimes even that does not help.
Everything should be on the latest version (1password, Safari extension, Safari and macOS).
1Password Version: 8.4.0
Extension Version: 2.1.4
OS Version: macOS 12.0.1
- Ryan_ParmanFrequent Contributor
The most recent update the Mac App Store shows me for the 1P(8) extension for Safari is from 2022-03-16.
It appears to be v2.3.1.
- PeterG_1P
1Password Team
Hi Ryan_Parman, thanks for the info here (and sorry for the persistence of this issue).
Does this still occur for you with the
2.3.2
update, which came out on March 24? If so, feel free to contact us at thatsupport+x@1Password.com
address, and the extensions team will let you know what information to send so they can dissect the dynamics of the issue. We'd like to resolve this for you!I'd bet that a console log from Safari would be a good start. Here's how you can get that information: https://support.1password.com/cs/extension-console-log/#safari
Thanks, and we'll look forward to checking this out for you!
- Ryan_ParmanFrequent Contributor
Just saw the post by PeterG_1P from February 18. I'm happy to send information, but I don't know what information to send.
I'm still seeing this in the latest release of the Safari extension available as of today's date. I've been keeping an entire separate window open for the last month+ with the suggestion that @felixfbecker posted on February 10. I periodically switch to it and hit Command-R when 1Password gets dementia.
- jayzedNew Contributor
This issue continues to happen to me on 2 different Macs, even after fully uninstalling both 1P 8 and the Safari extension. Here is the console log (which I have also sent in as a Bug report as per PeterG_1P request above)
[Warning] 80 console messages are not shown.
[Info] [OP] Locked at Sat Feb 26 2022 14:17:00 GMT+1100 (AEDT) (background.js, line 2)
[Warning] Safari produced an unexpectedly shaped message (background.js, line 2, x2)
[Info] Receivedfrom the native core (background.js, line 2)
[Info] [OP] Locked at Sat Feb 26 2022 14:51:59 GMT+1100 (AEDT) (background.js, line 2)
[Info] Receivedfrom the native core (background.js, line 2)
[Info] [OP] Locked at Sat Feb 26 2022 14:51:59 GMT+1100 (AEDT) (background.js, line 2)
[Info] Not attempting to connect to desktop app: already connected or connecting to desktop app (background.js, line 2, x3)
[Info] 📤 Sendingmessage to native core <707160253> (background.js, line 2)
[Info] 📥 Received messagefrom native core <707160253> (background.js, line 2)
[Info] Receivedfrom the native core (background.js, line 2)
[Info] 📤 Sendingmessage to native core <2025600326> (background.js, line 2)
[Info] 📥 Received messagefrom native core <2025600326> (background.js, line 2)
[Info] Hooray!; Unlocked account PPS53VXGAVCODPWVZIWHON6P3I with MUK; 🎉 (background.js, line 2)
[Info] We successfully unlocked 1 account(s) from a Desktop app with 1 unlocked and 0 locked account(s). (background.js, line 2)
[Info] [LM] Started Desktop Lock Monitor at 1645848063057 (connected to desktop app). (background.js, line 2)
[Info] 📤 Sendingmessage to native core <2901677244> (background.js, line 2)
[Info] 📥 Received messagefrom native core <2901677244> (background.js, line 2)
[Info] 📤 Sendingmessage to native core <2946709676> (background.js, line 2)
[Info] 📥 Received messagefrom native core <2946709676> (background.js, line 2)
[Info] 📤 Sendingmessage to native core <3402263088> (background.js, line 2)
[Info] 📥 Received messagefrom native core <3402263088> (background.js, line 2)
[Info] 📤 Sendingmessage to native core <813517965> (background.js, line 2)
[Info] 📥 Received messagefrom native core <813517965> (background.js, line 2)
[Info] 📤 Sendingmessage to native core <2522112351> (background.js, line 2)
[Info] 📥 Received messagefrom native core <2522112351> (background.js, line 2)
[Info] 📤 Sendingmessage to native core <3656797539> (background.js, line 2)
[Info] 📥 Received messagefrom native core <3656797539> (background.js, line 2)
[Info] 📤 Sendingmessage to native core <2655344962> (background.js, line 2)
[Info] 📥 Received messagefrom native core <2655344962> (background.js, line 2)
[Info] 📤 Sendingmessage to native core <1851863100> (background.js, line 2)
[Info] 📥 Received messagefrom native core <1851863100> (background.js, line 2)
[Info] 📤 Sendingmessage to native core <4029709604> (background.js, line 2)
[Info] 📥 Received messagefrom native core <4029709604> (background.js, line 2)
[Info] 📤 Sendingmessage to native core <447283188> (background.js, line 2)
[Info] 📥 Received messagefrom native core <447283188> (background.js, line 2)
[Info] 📤 Sendingmessage to native core <722264043> (background.js, line 2)
[Info] 📥 Received messagefrom native core <722264043> (background.js, line 2)
[Error] WebSocket connection to 'wss://b5n.1password.com/PPS53VXGAVCODPWVZIWHON6P3I/6CUZPGVAU5EY3OAA5H4SKR4NDU/w2ul7tgpfbojn7vao6zbeczadm' failed: The operation couldn’t be completed. Socket is not connected
[Info] 📤 Sendingmessage to native core <3523365369> (background.js, line 2)
[Info] 📥 Received messagefrom native core <3523365369> (background.js, line 2)
[Info] [LM] User went inactive. Posting lock notification. (background.js, line 2)
[Info] [LM] Stopped. (background.js, line 2)
[Info] [OP] Locked at Sat Feb 26 2022 15:12:08 GMT+1100 (AEDT) (background.js, line 2)
[Warning] Promise timed out. (background.js, line 2)
[Error] Unhandled Promise Rejection: undefined
(anonymous function) (background.js:2:1992183)
asyncFunctionResume
(anonymous function)
promiseReactionJobWithoutPromise
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Unhandled Promise Rejection: undefined
(anonymous function) (background.js:2:1992183)
asyncFunctionResume
(anonymous function)
promiseReactionJobWithoutPromise
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Unhandled Promise Rejection: undefined
(anonymous function) (background.js:2:1992183)
asyncFunctionResume
(anonymous function)
promiseReactionJobWithoutPromise
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Exception while handling request
(anonymous function) (background.js:2:1986854)
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Unhandled Promise Rejection: undefined
[Warning] Promise timed out. (background.js, line 2)
[Error] Exception while handling request
(anonymous function) (background.js:2:1986854)
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Unhandled Promise Rejection: undefined
(anonymous function) (background.js:2:1992183)
asyncFunctionResume
(anonymous function)
promiseReactionJobWithoutPromise
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Unhandled Promise Rejection: undefined
(anonymous function) (background.js:2:1992183)
asyncFunctionResume
(anonymous function)
promiseReactionJobWithoutPromise
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Exception while handling request
(anonymous function) (background.js:2:1986854)
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Exception while handling request
(anonymous function) (background.js:2:1986854)
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Exception while handling request
(anonymous function) (background.js:2:1986854)
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Exception while handling request
(anonymous function) (background.js:2:1986854)
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Exception while handling request
(anonymous function) (background.js:2:1986854)
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Unhandled Promise Rejection: undefined
[Warning] Promise timed out. (background.js, line 2)
[Error] Unhandled Promise Rejection: undefined
(anonymous function) (background.js:2:1992183)
asyncFunctionResume
(anonymous function)
promiseReactionJobWithoutPromise
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Unhandled Promise Rejection: undefined
(anonymous function) (background.js:2:1992183)
asyncFunctionResume
(anonymous function)
promiseReactionJobWithoutPromise
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Exception while handling request
(anonymous function) (background.js:2:1986854)
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Unhandled Promise Rejection: undefined
[Warning] Promise timed out. (background.js, line 2)
[Error] Unhandled Promise Rejection: undefined
(anonymous function) (background.js:2:1992183)
asyncFunctionResume
(anonymous function)
promiseReactionJobWithoutPromise
promiseReactionJob
[Info] Not attempting to connect to desktop app: already connected or connecting to desktop app (background.js, line 2)
[Info] Decided not to attempt reconnection to the desktop app. (background.js, line 2)
[Warning] Promise timed out. (background.js, line 2)
[Error] Unhandled Promise Rejection: undefined
(anonymous function) (background.js:2:1992183)
asyncFunctionResume
(anonymous function)
promiseReactionJobWithoutPromise
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Unhandled Promise Rejection: undefined
(anonymous function) (background.js:2:1992183)
asyncFunctionResume
(anonymous function)
promiseReactionJobWithoutPromise
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Exception while handling request
(anonymous function) (background.js:2:1986854) - PeterG_1P
1Password Team
Hi folks, thanks for your reports here. We'd love to get some more info on this.
For anyone who's willing, we'd love to hear from you at support+x@1Password.com, so that our extensions team can both help you personally as well as gather info that can be used for a comprehensive solution to this problem. Thank you again for your reporting here, and we'll be happy to hear from you and further investigate the issue on your behalf!
@felixfbecker Ryan_Parman jayzed @youngers @wkuehner
- jayzedNew Contributor
Same problem here as well. It's driving me crazy since installing the 1PW beta version. I have to restart my computer a couple of times a day every time the Extension loses connection with the browser. The "command+\" keyboard also stops working as does the 1P button on the Safari title bar.
The only way to fill in anything in the browser is by going into the full 1P app and manually copy and paste each item into the fields in the browser window.
Hopefully this gets fixed during the beta phase because if this is still present on public release the crowds will be very very angry.
- PeterG_1P
1Password Team
Hi @felixfbecker, thank you for providing these details. We'll keep working to sort out the issue - thank you for this contribution, and your patience!
ref: dev/core/core#8209
- Ryan_ParmanFrequent Contributor
Ooh! Pro tip. Love it!
- Former Member
This happens to me multiple times a day. Safari is my primary browser.
The steps I do to resolve it consistently are: In menu bar open Develop menu > Web Extension Background Pages > 1Password for Safari - Background Page, then when the debugger window is open, use Cmd+R to reload the background page. This reloads the background page of the Safari extension and it reconnects successfully.
These are the logs present in the debug console for the background page when this happens:
[Log] 👋 Initializing 1Password (background.js, line 2)
[Info] channel: stable (background.js, line 2)
version: 2.2.3
build: 20195 (15.4)
browser: Safari (15.4)
os: MacOSX (10.15.7)
[Info] 💫 Looking for desktop app com.1password.1password (background.js, line 2)
[Info] 👍 Finished initializing 1Password (background.js, line 2)
[Info] 📤 Sending <NmRequestAccounts> message to native core <2093971424> (background.js, line 2)
[Info] 📥 Received message <NmRequestAccounts> from native core <2093971424> (background.js, line 2)
[Info] 📤 Sending <NmRequestAccounts> message to native core <957699306> (background.js, line 2)
[Info] 📥 Received message <NmRequestAccounts> from native core <957699306> (background.js, line 2)
[Info] We successfully unlocked 0 account(s) from a Desktop app with 0 unlocked and 2 locked account(s). (background.js, line 2)
[Info] 📤 Sending <NmShowUnlock> message to native core <2586477481> (background.js, line 2)
[Info] 📥 Received message <Nothing> from native core <2586477481> (background.js, line 2)
[Info] Loaded page details in 60 ms. (background.js, line 2)
[Info] Analyzed the page in 2 ms. (background.js, line 2)
[Info] 📤 Sending <NmShowUnlock> message to native core <1499905082> (background.js, line 2)
[Info] 📥 Received message <Nothing> from native core <1499905082> (background.js, line 2)
[Warning] Promise timed out. (background.js, line 2)
[Error] Exception while handling request <get-frame-manager-configuration>
(anonymous function) (background.js:2:1986854)
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Exception while handling request <get-frame-manager-configuration>
(anonymous function) (background.js:2:1986854)
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Exception while handling request <get-frame-manager-configuration>
(anonymous function) (background.js:2:1986854)
promiseReactionJob
[Warning] Promise timed out. (background.js, line 2)
[Error] Exception while handling request <get-frame-manager-configuration>
(anonymous function) (background.js:2:1986854)
promiseReactionJob
[Info] Not attempting to connect to desktop app: already connected or connecting to desktop app (background.js, line 2, x2)
[Info] 📤 Sending <NmShowUnlock> message to native core <2603009564> (background.js, line 2)
[Info] 📥 Received message <Nothing> from native core <2603009564> (background.js, line 2)
[Info] 📤 Sending <NmShowUnlock> message to native core <2217158872> (background.js, line 2)
[Info] 📥 Received message <Nothing> from native core <2217158872> (background.js, line 2)
[Info] Not attempting to connect to desktop app: already connected or connecting to desktop app (background.js, line 2)
[Info] 📤 Sending <NmShowUnlock> message to native core <549139247> (background.js, line 2)
[Info] 📥 Received message <Nothing> from native core <549139247> (background.js, line 2)
[Info] 📤 Sending <NmShowUnlock> message to native core <2692533038> (background.js, line 2)
[Info] 📥 Received message <Nothing> from native core <2692533038> (background.js, line 2)`
I really hope this can help the 1Password dev team debug and solve this issue.
One more detail just in case it is relevant: I use both Safari and Safari Technology Preview at the same time (with the Safari extension installed in both).