Seeing the exact same thing across 2 different Macs.
It seems the fix for this was just released:
(I’ll mark this post as the solution for now to highlight this for everyone.)
This exact same error is happening on Edge browser. And Chrome too.
Installation failed. This is NOT a fix.
This bug is now affecting Edge/Chrome.
Sorry, I can’t say anything to MacOS environments. – On Windows, the update was offered as well and went through without any problems.
Same issue. 2025.11.1 doesn’t solve it.
Today I have updated Bitwarden via the Mac App Store. While the operation was processing, I realised Safari is already launched. I quit Safari while the installation was running. My bad.
Once installation was done and me trying to use the plugin in Safari, I got a forever spinning wheel on the plugin pop-up… Please note that bitwarden.app was fully functional.
I uninstalled bitwarden via MAS and eventually I finished the task with Clean My Mac uninstall functionality. So I downloaded Bitwarden .dmg from your site and installed it. Unfortunately the plugin was not fully active in Safari. Safari said I should install it. Once I tried to do so I was brang to the MAS once again and been asked to uninstall bitwarden.app …
(Please Note: the app in the MAS is 2025.11.0 and the .dmg is 2025.11.1. My Mac is running macOS 13.7.4)
I doubt that. On Safari it seems everyone was affected with a specific “bug” that was now fixed - on the other hand, I have no issues logging in and opening extension version 2025.11.0 on Vivaldi, Chrome, Edge and Brave.
If it doesn’t work for you on Chrome and Edge, try disabling/enabling the extension (in the browser’s extension manager). If that doesn’t work, try deinstalling/reinstalling the extension while making sure that the local storage of the extension was deleted before reinstalling.
I updated a few minutes ago, everything seems to be working fine now…
Still broken here, no updates available. Never thought I’d regret bit warden. 5 days now locked out on every Mac with this infinite loading crap. Time to switch to something secure like writing my passwords on paper, in a large font, while someone is looking over my shoulder.
I cleared the storage on the Bitwarden Safari (Version 26.1 (21622.2.11.11.9)) extension and disabled and enabled the extension to no avail. I disabled the extension and uninstalled the Bitwarden app on my MacBook Air M2 running macOS Tahoe 26.1. I downloaded the most current version of Bitwarden from the company website and installed. Now the Bitwarden extension for Safari is an available extension but will not install. I can use Bitwarden from the app, but not from the Safari extension.
- macOS 12.7.6. (MacBook Pro 13” 20162 2.9 GHz Core i5)
- Safari 17.6
I installed Version 2025.11.1 from the App Store and the desktop program works fine and shows the correct version number. In Safari it shows version number 2025.11.0 and I can’t for the life of me figure out what is wrong or how to fix it.
I found (on Reddit I think) a comment that you need to remove items from the Libraries with a link to a Bitwarden page showing the path tot he correct libraries. I Uninstalled Bitwarden AGAIN and deleted the files in the Library folder and then reinstalled.
Same problem with the spinning wheel on Safari. Works fine on Firefox and Chrome.
I tried disabling the extension in Safari and restarting the computer, then reenabling the extension. It did not help either.
I was prompted that a new Bitwarden update was available, so I ran the update and restarted Bitwarden.
Version 2025.11.2
SDK ‘main (8ef7951)’
Shell 37.7.0
Renderer 138.0.7204.251
Node 22.20.0
Architecture arm64
After installing the update the Bitwarden Safari extension (2025.11.0) is still present as an available extension and the check box is checked, however, the extension is not displayed in the Safari (Version 26.1 (21622.2.11.11.9)) browser. Inactivating and activating the extension has no effect, other than opening a browser tab with instructions on how to activate the browser extension, which is not the same for Safari. Clearing the storage has no affect either. The update hasn’t fixed this issue.