Basically, when I navigate to the URL in a browser window, auto fill works, username / password fields are detected, all is well. When I open the PWA, auto fill rarely works (maybe 1 in 25) and using the accessibility tile, pops a toast msg that says the username/ password field can’t be detected.
It’s very confusing! Why would it work in the PWA from time to time, but mostly auto fill / accessibility methods do not work?
I’ve noticed this with all my PWA’s and it’s very frustrating having to open bitwarden, search for the entry, copy the password, type my username and then paste the password.
You are talking about the Bitwarden mobile app, aren’t you? (I’m not completely sure, as you used the tag for the browser extension)
Could you share one or two examples of PWAs where it didn’t work? (maybe harmless popular ones, that are easily accessible even if one wouldn’t have an account there, so that we can try to reproduce)
Yes it is the android mobile app, sorry about that. The 2 I have set up as PWAs are directenergy.ca (utilities provider) and frigate (self hosted NVR). All sites have SSL and public domains.
They were all installed using the “add to homescreen" option.It’s only on android, desktop works fine.
Edit: I did go through the new “auto-fill in chrome/brave” and also turned everything off and went through setting it up again (auto-fill and accessibility)
Before I did that I was having issues with regular websites, now it’s just the PWAs.
@baudneo Sorry, I’m off now any moment, so just one short snippet:
I just tested it on https://account.directenergy.ca and could autofill some test credentials (username and password) without any problem (Android 15, works on both Chrome and Vivaldi for me).
PS: FYI, I used https://account.directenergy.ca/ as URI, with my default match detection “Host”.
If you open/unlock the BW app first, then open the PWA, then it usually works - at least for me. Other way around it hardly ever works in my experience.