I have RoboForm everywhere. I exported my saved logins from RoboForm into a CSV file. It imported successfully (or so it says) into Bitwarden. The issue is that every site I visit, Roboform will correctly detect the login, but Bitwarden never prompts for a login, instead, it only asks if I want to save the info into Bitwarden. The info is already there. The only thing I can think of that’s similar is that someone mentioned the URI info has to be in Bitwarden. It’s in the .CSV file from RoboForm in the Url and MatchURL columns. It looks like the URI1 field has the URL in it, yet Bitwarden doesn’t seem to recognize anything.
Although a possibility I have NOT tried is to remove RoboForm extension (which, unfortunately because I have the “everywhere” version and the Sync for FF, it’ll uninstall on all my devices).
BTW, same issue exists with Chrome as well, so I can at least rule out the Browser as an issue.
Hi @mjonis, you can always try manually conditioning the file before import if it doesn’t seem to be working correctly. If manually conditioning, the name of the column in the .csv needs to be login_uri in the import - here are the full instructions for manually conditioning a .csv.
I’ll also share this feedback with the team to see if our mapping needs to be adjusted.
If you continue to have problems with your import after taking those steps, feel free to contact us directly for more support!
This is normal behavior. In Bitwarden, you have to initiate the auto-fill process yourself (unless you have enabled the optional function “auto-fill on page load”, which would auto-fill the login credentials without user intervention — and also without a prompt from Bitwarden). Commonly, you would trigger the auto-fill by using the keyboard shortcut Ctrl+Shift+L.
A possible cause is either that the Bitwarden browser extension is locked (it must be unlocked to recognize that the info already exists), or that your Roboform extension is interfering with the Bitwarden extension, preventing the latter from functioning properly.
When your browser is on a login page that should have been recognized, please look at the Bitwarden shield icon shown to the right of the address bar in Chrome. Does it have an overlayed “badge counter” that is displaying a number (e,g, 1), as shown below? If not, the problem is indeed caused by a failure in the URI matching, and we can take a closer look at that.
