Matched Credentials Fail to Appear after Syncing Vault, Regardless of Browser

[btbutts]

Select Topic Area

✅ Code Contribution Proposal

Code Contribution Proposal

Quick Note:

This is a bug report. There seems to be a sort of circular reference between the Bitwarden GitHub and the Bitwarden Community page in that the Bitwarden Community page redirects to GitHub to post a bug but GitHub reads (I guess) that you should go to Bitwarden Community if you want to do anything other than Code Contribution Proposals, without actually referencing code you want to write?? Well I don't know what the actual fix is for this issue so it would be nice if there was a clear place to simply report bugs as a business user.

The Bug:

If there's a specific page I should copy this to beyond the Bitwarden Community homepage: https://community.bitwarden.com/, please let me know and I'll move it.

There seems to be an issue with Bitwarden browser extension after syncing, in that it will fail to show any credential matches after syncing. This is true regardless of if I sync within the browser extension, or the MacOS app. I can wait for multiple minutes after syncing, refresh the page, and no matches will appear.

1. I started testing this using the GitHub login page. I synced the MacApp to ensure that no login's appeared, even though I did initially have a match. So after syncing, I verefied after clicking the Bitwarden icon in the username form box that there were indeed no credential matches.
2. I then synced again from the browser extension. Still no matches.
3. Then I changed the match type for the GitHub URL in the MacOS app from the Default setting to Base Domain. However, Default is actually globally set to Base Domain anyways, so these should be, obstensibly, the same setting.
4. I then immediately have a credential match.
5. Then I synced again from the browser extension, once again there's no match.

It doesn't mater how many times I repeat this cycle, syncing from the MacOS app or the browser extension, and I've tested Chrome, Edge, and Safari, whenever I syncronize the vault, my credential matches disappear until I alternate the match type between Default and Base Domain after syncing.

I can change the match type in the MacOS app and the match will appear nearly instantly in the browser extension. The same is true if I change the match type in the browser extension itself after syncing. I get the same result.

Here's a OneDrive link to a video that shows this behavior. I have redacted sensitive info from it. (You should probably not try to stream it in Safari... MS Stream video playback doesn't always work well in Safari)

I can't say what the solution to this problem is but clearly something is breaking down after syncing that recovers once a change to the vault is made. It's one thing to modify a newly added credential if the URL fails to match. However, Bitwarden shouldn't stop matching credentials (for whatever reason) after syncing.

[github-actions[bot]]

✨ Thank you for your code contribution proposal! While the Bitwarden team reviews your submission, we encourage you to check out our contribution guidelines.

Please ensure that your code contribution includes a detailed description of what you would like to contribute, along with any relevant screenshots and links to existing feature requests. This information helps us gather feedback from the community and Bitwarden team members before you start writing code.

To keep discussions focused, posts that do not include a proposal for a code contribution will be removed.

• 💡 For feature requests and general discussion, please visit the Bitwarden Community Forums.
• ℹ️ For questions and support, visit the Bitwarden Help Center.
• 🐛 To report a potential bug, please visit the corresponding repo. Server | Clients | iOS | Android

Thank you for contributing to Bitwarden!

[btbutts]

Now I find the issues board after submitting this code proposal... moving to issues and closing this...