Some background. I left Bitwarden two or so years ago for another password manager because on iOS autofill always felt poorly supported, as it always required much more clicks than in any other manager.
Now, after every password manager from the top five introduced new prices this year and my current one went beyond reasonable, I started looking around and wondered whether Bitwarden had improved its autofill since I left it. I was genuinely surprised to find it hadn’t, even after the team had made a switch to a native application.
For example, iOS has QuickType keyboard suggestions for passwords/2FA codes, and every other password manager does support this except Bitwarden.
Why does this problem persist for years? Why can the team rewrite the whole app but can’t support this standard QuickType autofill? This is unacceptable considering that some applications implement aggressive security practices and ask users for credentials/totp every 15-20 minutes or so (PayPal, for instance).
I do have proper entry in Bitwarden. I double-triple-fourth-checked. It simply doesn’t work.
When I click Passwords field, I indeed can pick the entry from Bitwarden, like the help page suggests, but this shouldn’t be like that as any other password manager doesn’t need this. Also, in this way only login/password filling is supported, not passkeys.
I even added a passkey on a ebay.com site using my iOS browser.
This behavior is quite inconsistent. It doesn’t work for ebay and some other apps as I remember, but works for other like browser (which is third-party, btw). I even reinstalled the ebay app. Nothing helps. The very same behavior I observed in 2024 when switched from Bitwarden because I literally said “enough, it doesn’t work as it should”.
Now I would switch back, but I don’t wish to pay for the app that simply doesn’t have its primary functionality working well.
Holy-moly… I found the cause… I typed in URL manually when created a login entry and it had no https:// scheme part! It was just ebay.com, not https://ebay.com. After adding scheme into the URL it immediately started working.
In the browser, your default URI match detection method is probably set the “Base Domain”, whereas it seems to be more restrictive (probably “Host”) on your phone.
I was doing all that on my iOS with both eBay and browser apps. I even posted a screenshot here to show this, so both were served by the same iOS Bitwarden app with identical settings. I also tinkered with changing from “base domain” to “host only” and others, no luck. Why in the end both apps behaved differently — no clues.
Hey Zakton, thats a great finding. Thanks a lot for investigating the issue. We are tracking this as a bug and you can expect a fix that defaults any site without scheme to https in one of the upcoming releases.
Passwords”:
