Empty vault in Firefox Extension 2026.7.0

[FlohEinstein]

Steps To Reproduce

After updating to 2026.7.0, when logging into your vault in Bitwarden Firefox Extension, the Vault appears empty, even though you can sync it.
And of course autofill doesn't work.
Manually downgrade to 2026.6.1 via Mozilla Addons library --> versions, and it works again

Expected Result

That my passwords are in the container

Actual Result

Vault appears empty

Screenshots or Videos

Additional Context

Server version (Third-party): 2025.12.0

Operating System

Windows

Operating System Version

11 (26220.8925)

Web Browser

Firefox

Browser Version

153.0

Environment Versions

Version: 2026.7.0
SDK: 'main (3e060f8)'
Server version (Third-party): 2025.12.0

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-40921
Link (for internal use): https://bitwarden.atlassian.net/browse/PM-40921

[pamperer562580892423]

Server version (Third-party): 2025.12.0

Reported in various other issues already, e.g. #22024

This is a Vaultwarden issue - and they even have a fix for it: dani-garcia/vaultwarden#7462

[Pootch]

Same problem.. this extions and firefox gets worse every update.

[FlohEinstein]

Was just advised by pamperer562580892423
10m ago that it's a vaultwarden issue, and others reported it was well. I therefore close it as duplicate

[baaa]

Hi, although you have closed this as a vaultvarden issue, this bitwarden client can still be a lot more resilient for such a thing.

I'm reluctant to re-open it but 2026.6.1, had solved this issue and it regressed in 2026.7.0

the bitwarden crash is simply caused because some formatting change, the frontend.js either should be more resilient not to crash and display loading bars for ever, or even better should be able to say, "hey the format i was expecting is bongled, since you are using a 3rd party server there's likely a version confusion"

the ui enforces strict type verification during data parsing. It throws a fatal type mismatch exception when iterating through vault item objects (affecting both Card and standard Login item types).The engine encounters a structured JSON metadata block (JsValue(Object)) for fields where its internal type mapping strictly expects a raw encrypted string string primitive, halting the entire UI rendering engine.Extension Console Stack Trace.

Unhandled error in angular Error: Error: invalid type: JsValue(Object({"brand":"2...", "cardholderName":"2...", "code":"2...", ...})), expected a string
je bitwarden_wasm_internal_bg.js:6830
Ti bitwarden_wasm_internal_bg.js:8242
i bitwarden_wasm_internal_bg.js:8580
invokeTask zone.js:431
onInvokeTask ng_zone.ts:453

I've actually went and deleted the cards from backend, thinking may be the change only effects the cards, but than the same error surfaced for logins as well.

[FlohEinstein]

@baaa you bring up a valid point. I reopen it.

[baaa]

Thank you <3
I actually thought, I could make a really fast PR for this, but my JS-foo is not as strong it seems :)
here is some information which may or may not help in a developer who picks this up:

Server Environment Details

• Vaultwarden Server: 1.36.0 (Latest)
• Web Vault Frontend: 2026.4.1 (Latest)
• Database Backend: SQLite 3.51.3

and as mentioned before this exact setup is completely fine with 2026.6.1 and gets broken (again) with 2026.7.0

[pamperer562580892423]

• Vaultwarden Server: 1.36.0 (Latest)
• Web Vault Frontend: 2026.4.1 (Latest)
• Database Backend: SQLite 3.51.3

and as mentioned before this exact setup is completely fine with 2026.6.1 and gets broken (again) with 2026.7.0

@baaa ... did you see that the corresponding Vaultwarden issue (dani-garcia/vaultwarden#7462) mentions a fix - e.g. in this comment - and that it is working again with :testing?!

[pamperer562580892423]

@baaa you bring up a valid point. I reopen it.

@FlohEinstein Actually, I think it's not bad that this issue is open, because it may prevent another 20-40 duplicate issues... but my prediction would be that Bitwarden will close it again, as those points probably don't classify as a bug... (not to mention that you're all using Vaultwarden)

[TeraJaQ]

same issue on the windows app...i've performed the downgrade to 2026.6.1 and it works

https://github.com/bitwarden/clients/releases#release-desktop-v2026.6.1

[softyoda]

Who in there push in prod (in firefox auto update) a broken update ? An AI ? There are no verification for such push of JS code that self loop? This doesn't spread thrust. (yea ranting comment, but you get the point, the public may see it this way)

Edit : seem to be from vaultwarden side 🤔