"The database was terminated." error message in the browser

@VirtuaJustin

If that's the case please email us and let the team gather some logs from your device so we can better understand what's happening. Please email us using support+forum@1password.com. Be sure to use the email address tied to the account in question.

Include the following:

Your user name here in the forum. VirtuaJustin
A link to this topic. https://1password.community/discussion/comment/684173/#Comment_684173

This will help us connect the dots as they say.

Happening to me as well for the last couple of days. Following for any solution. Let me know if you need more logs.

It's particularly bad when using App Store Connect (Apple Developer). Every time I go to press release this version, the DB message would appear and I would need to log back into Apple.

@ICULikeMac it's strange that you get this error message when using App Store Connect. Could you reproduce the behavior and then send us your extension console logs so that we can investigate further?

How to send your extension console logs: https://support.1password.com/cs/extension-console-log/

Attach the logs to an email message addressed to mailto:support+forum@1password.com. With your email please include:

• A link to this thread: https://1password.community/discussion/139629/1password-for-safari-extension-v2-10-0-database-error-termination#latest
• Your forum username: ICULikeMac

You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks!

There is a really annoying bug in the latest version of 1Password:
Each and every timeI clear my browsing history (latest version of Safari, latest version of 1Password 8) a separate tab instantly opens with the following message:
"The Database was Terminated.
The database was unexpectedly terminated and may have become corrupt.
1Password in the browser was reinitialized on your behalf....
......."
This is very annoying.
I hope there is some workaround, but I am afraid this is a bug you need to fix,
Hope you can fix it soon.
Please let us know.
Thank you.

1Password Version: 8.10.4
Extension Version: 2.10.0
OS Version: 13.3.1
Browser:_ Safari

Hi @Dub, thanks for reaching out!

The error message you're encountering is expected and will appear any time you clear the Safari history/cache. The following article explains why you're seeing this and what workarounds are available:

• If you see "The database was terminated" in Safari

Let us know if you have any further questions.

Thank you for the link to the available workarounds.

I find it peculiar that 1Password never did this before the latest version. Sounds like you must have changed something in the way that 1Password operates with Safari.

You're welcome, @Dub! Were you previously clearing the history only before closing Safari? While the error message is new, clearing your history/cache in previous versions of 1Password for Safari would also clear the local copy of your information and you would be required to restart Safari in order to get things working normally again. If you had previously been clearing the history and closing Safari, once you relaunched Safari, things would be working as normal.

I, like many other folks I know always clear my history at least once a day before closing my browser. So, yes, you are correct that upon re-start everything was working just fine before and obviously everything works just fine now.
No workarounds are needed.
Bottom line: I clearly understand the change, but in my humble opinion, there should be no error message. The reasons are first that it is not an error, and second, that the message serves no useful purpose.
On top of that, the wording of the message is too ominous and confusing. The sentence in red, the words “was unexpectedly terminated” and “may have become corrupt” , as well as the recommendation to review your 1Password settings in the browser are way too ominous for something simple that is not an error.
I would recommend that the company eliminate the "error message" completely. It is clearly not needed and the words used are way too ominous and confusing to users.
Thank you again for your quick response and explanation.

@dub

Thank you for the feedback. The team is working to make the working better. I can't say that the message would not appear, but the team is looking into the best way to move forward.