Browser extensions icon doesn't show number of logins after last update (2025.7.0)

Same here, that was so useful, please bring it back!

The team is working to resolve this one, stay tuned and thanks for your patience!

But please don’t bring back the bug. It was fixed with 2025.7.0.

Seems to be back for me:
Brave 1.80.125 (Official Build) (64-bit)
Chromium: 138.0.7204.184
(Windows 10)

1 Like

Since I updated, Bitwarden no longer works correctly in Firefox for me. I no longer see a number on the shield icon to notify me there is a known login for the current website. Also, when I create a new login or edit an existing password, Bitwarden no longer asks me whether to store or update the login.
Please HEEEEEEEEEEEEEEEELP!!!

@Sander_Bouwhuis I moved your comment into an existing topic related to the icon badge counter issue.

As for the save/update notifications, please double-check that the options “Ask to add login” and “Ask to update existing login” are both enabled (under Settings > Notifications); if they were already enabled, please follow up by starting a new forum topic regarding that issue.

Sidenote: As now (almost?) all browser extensions seem to be affected by this, I updated the title to mention just “browser extensions” (instead of “Chrome/Brave”). And I included the version number.

@grb
They are of course on. They have been for many years (ever since I switched from Lastpass).
Autofilling on page load does work, but showing a number on the icon or showing the update / add login popup stopped working since the last update (last week or so?).

Firefox 141.0.3 (64-bit)
Bitwarden extension 2025.7.1

In Firefox, it seems to have something to do with tabs. If the current tab isn’t displaying the count, switching to another tab causes the count to start working for all tabs. In fact, just opening a second tab before unlocking Bitwarden is enough for the count to start displaying correctly.

1 Like

The reason I asked is that sometimes, updates to the browser extension will cause some user preferences to be disabled.

As for the icon issues, the just released version 2025.7.1 may fix this (at least for Firefox).

I have also seen cases after upgrades where one needs to turn a setting off and then back on.

1 Like

Heeeeeeeeeeeeeeey, everything works again after the 2025.7.1 update!!!

  1. Number of logins on the icon : works
  2. Fill suggestions: works
  3. Store updated passwords : works

Thanks a bunch guys!

@Sander_Bouwhuis Sorry for delivering bad news, but I think that can’t be fixed with 2025.7.1, as this Firefox “hotfix” only contains the one fix for the crashes on Firefox:

Ok, then it must have been the fact that I completely reinstalled Bitwarden.
Are you sure about not fixing it? For me, everything works again. Maybe the bug is in the settings? After reinstalling I went through all the settings again.
There is DEFINITELY a difference since yesterday.
Also, I noticed the popup windows look different from before. They now look a lot more ‘stylish’.

Or, if the fix is not because of the settings (and considering Bitwarden now definitely looks differently), could it be that the auto update feature is not working, and I was on an old version of Bitwarden? Downloading the extension again at least updated me to the current version.

I don’t think it can be ruled out that version 2025.7.1 also fixes the icon badge counter issue (at least in Firefox), because PR #15938 (i.e., the bug fix for Issue #15899 — the firefox crashing issue) seems to be a mitigation (or reversal) of PR #14801 which has been hypothesized to be the root cause also of Issue #15810 (the badge number issue).

2 Likes

I have the same issue, it’s been a couple of weeks, any ETA for fixing?

@xwu , welcome to the community!

Did you see this post?

Has your BW extension been updated to 2025.7.1?

Chrome web store still shows 2025.7.0: https://chromewebstore.google.com/detail/bitwarden-password-manage/nngceckbapebfimnlniiiahkandclblb

1 Like

There is now a github report of it occurring with extension 2025.7.1 on Firefox and MacOS.

2 Likes

I also tried Firefox (141.0.3) on macOS today, upgraded to 2025.7.1 but same issue.
Version: 2025.7.1
SDK: ‘main (f2bc708)’
Server version: 2025.7.3

1 Like