Number of matching logins not shown in Bitwarden extension icon badge counter overlay

There was bug affecting the display of the matching logins counter on the Bitwarden browser extension in version 2025.5.x (Github Issue #15001 — previously discussed in another forum thread) as well as in versions 2025.7.x-2025.8.x (Github Issue #15810 — previously discussed in another forum thread).

There have been recent reports of such a bug resurfacing again in version 2025.12.0 for some users. Comments about this issue made on other threads have been moved into this topic, to consolidate the discussion and collect evidence in one location.

1 Like

HISTORY IS NOW REPEATING ITSELF WITH 2025.12.0

2 Likes

how so? 2025.12.0 seems to be working fine so far.

NOT FOR ME. (ANY IDEA WHY CAPSLOCK NEEDS TO BE ON?)

This might just be a corrupted data file on your PC. The solution to that is uninstalling the extension, removing the local data storage and reinstalling.

1 Like

I can confirm yes, bug is back in 2025.12.0

Lock, and unlock vault number will appear…and then randomly disappear again later.

@bilogic @southerndoc @DenBesten @silversword I moved your discussion into this recent thread about the icon badge counter bug in 2025.5.x (Github Issue #15001) that appears to have resurfaced for some users.

2 Likes

That is a related open GitHub issue… the “original” or main one for the icon badge counter bug was this, I think: Number of login autofill suggestions badge on extension icon disappears · Issue #15810 · bitwarden/clients · GitHub

Moved the recent comments into a new topic (this one), to avoid confusion.

For me, the problem with this bug is not that the number of matching logins is not shown in the icon badge, the problem is (as it was with the previous bug) that the keyboard shortcut to autofill does nothing at all until I autofill with the mouse (clicking on the icon badge and then on that beloved tiny “Fill” button in the item list).

I am used to using the keyboard shortcut mainly, so having to fumble with my mouse to continue working is a bit irritating for me.

IIRC, this bug was back with 2025.11.X.

1 Like