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

I have been struggling with this Ventura Safari Cache issue for some time I have followed this blog plus, I have been communicating with support@1password.com, via several 1P agents.

The last agent make an amazing admission, he said....While I don't imagine we'll completely get rid of this message".

This is a COMPLETELY UNSUPPORTABLE POSITION for 1P to take

1P MUST COMPLETELY FIX THIS 1P8 SAFARI CACHE ISSUE

What on earth is going on at 1Password?????

It appears that major software issues are not able to be fixed ????

What does Dave Teare and Jeff Shiner think about this? I copied them both on my last email.

As 1P8 remains unstable, trust declines. It looks like I am stuck with the stable 1P7 (a so called now "unsupported platform" according to one of the support agents).

How is that 1P7 7.9.10 is OK but 1P8 is not?

Thanks amid

I just tried the 1P8 app and its Safari Extension on a Mac with macOS Monterey 12.6.5 (latest version).

The Safari Cache issue is also present on MacOS Monterey 12.6.5 with Safari 16.4.1

There is no Isolation Mode in macOS Ventura 13.3.1 (latest version). There is a function called Lockdown Mode specifically for cyber attacks but I have not activated this. This should be irrelevant for 1P8.

See screen shot.

Thanks amcd

@William46 and @PatMax

I'm sorry that you're see an error message that says "The database was terminated" when using 1Password. Please take a look at this article for steps on how to avoid the issue: If you see "The database was terminated" in Safari

If the workarounds described in that guide don't work for you then please let me know. 🙂

-Dave

@amcd

I see that my colleague responded to you a few hours ago. Please continue the conversation over email as the support team there will be in the best position to help you as they have access to your ongoing conversation.

-Dave

ref: BEW-87598-384

Sorry Dave.. I have tested all the suggested workarounds in the blog and others sent by email.

All seem like temporary, inconvenient "patches".

Firefox and Chrome Safari extensions work so I guess there must be a solution for 1P.

Please confirm that you guys will finally solve 1P* Safari Extension Issues

Still happening for me. Found this thread through a search so might be missing some context but anyway I'm running the latest 1Password and Safari crashes basically every time I visit App Store Connect after login. Which is pretty much the most important site I use and this has been happening for at least a couple weeks.

I'm experiencing the "database was terminated" message from the Safari plugin also. This only occurs on the appstoreconnect.apple.com site with Safari. I login with 1password inserting credentials, and when appstoreconnect redirects to the next page I get the error, and the extension is disabled from that point until safari is restarted.

1Password: 8.10.6
Safari: 16.4
MacOS 13.3.1(a)

1Password for Safari working fine on other sites. Switched to Chrome to go to appstoreconnect, which feels wrong, but it works.

@"Will Price" and @robkerr

It sounds like you're both running into a known issue where the "Database is terminated" error occurs on specific websites such as https://appstoreconnect.apple.com/. Our developers are aware of this issue and are investigating. I've added your reports to the internal work item open for the issue.

While our developers look into this, I recommend that you temporarily use a different browser to sign into https://appstoreconnect.apple.com/. I'm sorry for the trouble.

-Dave

ref: dev/core/core#21638

I have been experiencing this same problem when I clear my history in safari. While it is helpful that 1Password has suggested ways to deal with this, they seem very cumbersome, especially if the items you are removing from history number in the hundreds, as is the case for me. Rather than taking these measures, I simply delete the 1password for safari download after clearing the history and then reinstall it. It seems, at least to me, a much simpler workaround. Hopefully, 1password can be fixed so that no workarounds are needed. I still love my 1password. Couldn't do without it, notwithstanding this little glitch.

I have been experiencing the same issues for the last few days on Safari on Mac. I do not clear history or cookies, so the issue is not because of that action. Developers please address, as this is becoming more and more irritating.