I use Firefox an Chrome most of the time. By far, Chrome is my main browser. I use MacOS and Windows 10 and 11 for my three daily drivers. This symptom appears on all machines I use on all browsers, and has been an issue for a couple of months now.
Here’s the issue:
When my browser is on a site like Microsoft.com, and I want to find a credential for a site like Google.com, if I search MyLogin@Gmail.com, oftentimes the result will never show anything other than results that belong to Microsoft.com. Sometimes I can get the Google.com result to show.
If I’m on a tab with no site, things are quite a bit more reliable, but there are frequent times when I cannot get any search results at all. If I do a search, all I can see is everything.
Right now, for example, I’m in Firefox, I’m on a blank tab, when I opened the Bitwarden browser extension to get a credential for a site, I didn’t receive any answers to my search, I was only shown everything in my Bitwarden, which is thousands of entries.
Of course, I was going to get a screenshot of this and now it’s working. I’ll try to get that done the next time see this issue.
Have you clicked the V button to expand the “All Items” section?
What search expression?
FYI, generally, if you need a credential, you should not need to do any searching. If the website URL has been correctly stored in your vault login items, and if there are no problems with your settings for URI Match Detection, then Bitwarden should make the relevant login credentials available automatically (without searching).
For some sites, I may have HUNDREDS of credentials. Or if I’m on a site and I want to find a credntial for an app outside of the browser, I may do a search in the app, but only receive answers that involve the site, or the answers I receive are all entries in the database.
I was able to get an example:
I’m on Grok, I want a credential for ChatGPT for another tool. So, I search Chat GPT. The suggested results are Grok and a bunch of credit cards. None of which involve the string “chatgpt.” Then, down below I can scroll “all items.” The search results won’t refine out ChatGPT unless I go to a blank tab (even then, I may not get the answer I’m looking for).
Do all 34 of your grok.com vault items contain the string chatgpt? If none of them contain chatgpt in any field that you can see when you edit the item, then you may have found a bug. As a possible work-around, please try one or more of the following search expressions instead (and let me know if there is any improvement):
So here’s the same setup, on Grok.com, searching for ChatGPT, you can see that I get a totally different set of (correct, at this point) answers. The only thing that has changed is that I’m now on Windows, and it’s later in the day.
+chatgpt returns nothing.
+chatgpt* returns the one ChatGPT entry that I have in BitWarden.
+*chatgpt returns the same ChatGPT entry.
+chatgpt returns the same ChatGPT entry.
It does look like there’s a bug when using the Chrome extension on macOS. Is it reproducible? If you go to grok.com and enter chatgpt in the search, do you see your 34 Grok accounts every time (while on your mac)? When you’re on your Windows system, do you never experience this issue (On this site, or on any other sites)?
Also, what you reported here is a little confusing:
Did you also include the prefix character > in each of those searches (e.g., >+chatgpt*, not just +chatgpt*)? And was the last search actually >+*chatgpt* with leading and trailing wildcard characters (as requested), or did you in fact repeat the first search and get a different result (as suggested by your comment)?
Please try these searches also on your macOS system while on the grok.com site.
This search comes from a Windows 10 instance. Here I’m trying to look for an Apple credential for another tool, but I cannot get it to show me anything other than autofill suggestions for Grammarly and credit cards… even though there’s nothing on the page that’s asking for a payment. Next is favorites, after that is the entire library.
I tried all of the text commands to see if I could pull out answers for Apple, but nothing changed.
I think that you may have posted two identical screenshots by mistake, but from your description it sounds like a bug. I recalling seeing some bug report in which search results fail to appear if the browser extension has been used for an extended period of time (which is possibly why restarting the browser would have helped).
However, I do not recall this bug also causing irrelevant autofill suggestions to be displayed. Out of curiosity, what setting do you have for “Default URI Match Detection” (in Settings > Autofill)?
Edited to Add:
Please check the following two bug reports and see if they match the problem you are encountering. If you have additional information to contribute, consider posting in the open Github issue:
In addition, since your two screenshots show searches for apple and Apple respectively, the following Github issue may be relevant:
Both of the searches for “Apple” were done from Windows via Chrome.
The behavior exhibits in Firefox and Chrome and on MacOS and Windows. All of my Linux instances are terminal-only; I suppose I could probably spin something up with a GUI to do some testing there.
Looking at the GIT posts “Search does not find login with exact name match,” and “Browser extension search not searching properly,” I don’t think any of those are a match.
The behavior is intermittent.
If I tab to a blank tab, that generally fixes the problem (but I don’t think it always fixes the problem).
In the examples here, it’s more like the search is not even running. Input what I want to search for, press enter, there’s a little ‘blink’ of sorts as if the data in the window changed to show my search results, but in the end, I’m seeing either A), no results, just everything in my library, or B) only results that are relevant to the tab that I’m on.
I might be mistaken here, but I don’t think this has been going on for more than a few months.
I will also say, though, I have noticed “Search does not find login with exact name match” for many years now, and just learned to deal with it. I’m pretty sure I even started a bug report for it.
Just the same, if you have not already done so, it would be worthwhile trying both the capitalized and non-capitalized version of your search term next time that you encounter this issue.
In that case, it may be appropriate to file a new bug report.
