Issue with 1Password for Safari

This discussion was created from comments split from: Safari extension often loses connection to 1password.

Comments

  • jayzed
    jayzed
    Community Member

    This issue is still persisting for me from time to time despite being on the latest beta (80700095) and on 2.3.3 of the Safari extension (and the latest Mac OS versions).

    The first report of this was back in November in this thread from the looks of it and it's almost May 2022 and it's still frustratingly still ongoing.

    Is there any progress with this bug?

    Here are the console logs:

    [Info] 📤 Sending message to native core <1713078797> (background.js, line 2)
    [Info] 📥 Received message from native core <1713078797> (background.js, line 2)
    [Info] Received from the native core (background.js, line 2)
    [Info] 📤 Sending message to native core <608033409> (background.js, line 2)
    [Info] Loaded page details in 23 ms. (background.js, line 2)
    [Info] Analyzed the page in 3 ms. (background.js, line 2)
    [Info] 📥 Received message from native core <608033409> (background.js, line 2)
    [Error] Unable to unlock account after attempting to sync updated keysets. – InvalidStateError: Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing. — background.js:2:1981365
    InvalidStateError: Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing. — background.js:2:1981365
    (anonymous function) (background.js:2:2106921)
    asyncFunctionResume
    (anonymous function)
    promiseReactionJobWithoutPromise
    promiseReactionJob
    [Info] We successfully unlocked 0 account(s) from a Desktop app with 1 unlocked and 0 locked account(s). (background.js, line 2)
    [Info] 📤 Sending message to native core <3033058503> (background.js, line 2)
    [Info] 📥 Received message from native core <3033058503> (background.js, line 2)
    [Info] Received from the native core (background.js, line 2)
    [Info] 📤 Sending message to native core <1026344308> (background.js, line 2)
    [Info] 📥 Received message from native core <1026344308> (background.js, line 2)
    [Error] Unable to unlock account after attempting to sync updated keysets. – InvalidStateError: Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing. — background.js:2:1981365
    InvalidStateError: Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing. — background.js:2:1981365
    (anonymous function) (background.js:2:2106921)
    asyncFunctionResume
    (anonymous function)
    promiseReactionJobWithoutPromise
    promiseReactionJob
    [Info] We successfully unlocked 0 account(s) from a Desktop app with 1 unlocked and 0 locked account(s). (background.js, line 2)
    [Info] 📤 Sending message to native core <634441962> (background.js, line 2)
    [Info] 📥 Received message from native core <634441962> (background.js, line 2)
    [Info] Received from the native core (background.js, line 2)
    [Info] 📤 Sending message to native core <2597027472> (background.js, line 2)
    [Info] 📥 Received message from native core <2597027472> (background.js, line 2)
    [Error] Unable to unlock account after attempting to sync updated keysets. – InvalidStateError: Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing. — background.js:2:1981365
    InvalidStateError: Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing. — background.js:2:1981365
    (anonymous function) (background.js:2:2106921)
    asyncFunctionResume
    (anonymous function)
    promiseReactionJobWithoutPromise
    promiseReactionJob
    [Info] We successfully unlocked 0 account(s) from a Desktop app with 1 unlocked and 0 locked account(s). (background.js, line 2)
    [Info] 📤 Sending message to native core <2325036515> (background.js, line 2)
    [Info] 📥 Received message from native core <2325036515> (background.js, line 2)
    [Info] Received from the native core (background.js, line 2)
    [Info] 📤 Sending message to native core <763476184> (background.js, line 2)
    [Info] 📥 Received message from native core <763476184> (background.js, line 2)
    [Error] Unable to unlock account after attempting to sync updated keysets. – InvalidStateError: Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing. — background.js:2:1981365
    InvalidStateError: Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing. — background.js:2:1981365
    (anonymous function) (background.js:2:2106921)
    asyncFunctionResume
    (anonymous function)
    promiseReactionJobWithoutPromise
    promiseReactionJob
    [Info] We successfully unlocked 0 account(s) from a Desktop app with 1 unlocked and 0 locked account(s). (background.js, line 2)
    [Info] 📤 Sending message to native core <4215683199> (background.js, line 2)
    [Info] 📥 Received message from native core <4215683199> (background.js, line 2)
    [Info] Received from the native core (background.js, line 2)
    [Info] 📤 Sending message to native core <1348133568> (background.js, line 2)
    [Info] 📥 Received message from native core <1348133568> (background.js, line 2)
    [Error] Unable to unlock account after attempting to sync updated keysets. – InvalidStateError: Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing. — background.js:2:1981365
    InvalidStateError: Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing. — background.js:2:1981365
    (anonymous function) (background.js:2:2106921)
    asyncFunctionResume
    (anonymous function)
    promiseReactionJobWithoutPromise
    promiseReactionJob
    [Info] We successfully unlocked 0 account(s) from a Desktop app with 1 unlocked and 0 locked account(s). (background.js, line 2)

  • Hi @jayzed:

    Thanks for reaching out. The issue you're experiencing seems to be separate from the issues being referenced above.

    Do you have Safari set to regularly clear your browser history? Let me know!

    Just as an additional note, I've split your post off into a new thread.

    Jack

This discussion has been closed.