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 red...
Former Member
4 years agoThis 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).