onyourbikes I tried and it works fine for me. Maybe you can check the Accessibility settings for app overlay permissions?
Autofill using bitwarden has gone from vanadium
- Edited
TrustExecutor OK I checked that and turned it on, and now it kind of works. It shows the overlay for bitwarden, but that just opens the app.
When using bitwarden to fill on other apps it shows the three dots next to the paste button after a long press in the text box. Then I can directly fill the log in without changing apps and manually copying/pasting. Does yours work like that? I could swear it used to do that in vanadium.
Thank you
onyourbikes autofill for BW has also disappeared for me in vanadium
When was Bitwarden last updated?
Seems like it could be a recurring issue based on this Open Issue:
https://github.com/bitwarden/mobile/issues/242
Does it work with any other browser? Be useful to see if it replicates on one to determine if it is just Vanadium when 99% of reports on their issue tracker for the same thing aren't using it.
5 days later
3 months later
Autofill has never worked in Vanadium. IDK how y'all were able to do it in the first place.
2 months later
I just checked, it works in Vivaldi browser as expected. But as far as I know, you cannot default the browser in Bitwarden to open webpages. Wonder when this issue gets solved for Vanadium.
11 days later
- Edited
I want to second this. Bitwarden autofill used to fail on all chrome based browsers when Android 13 was first released. But now, I tried using Brave on Graphene and the autofill works. Only on Vanadium did it not work.
Granted that I turned accessibility on for this to work, but even then, was expecting that to work on Vanadium. I don't mind turning this on because I trust both Graphene and Bitwarden.
Lmk if you need further info :)
This should be fixed when a release containing this PR is released:
matchboxbananasynergy pog thanks!
- Edited
matchboxbananasynergy this sort of collaborative effort across the privsec community makes the world go round. Great to see Bitwarden being this receptive.
Thanks to @flawedworld too for making the PR.
Has the app id changed for vanadium yet? I still have org.chromium.chrome on my end
Great to see projects working together!
Lusca It has, but you'll only see the change if you factory reset. On installs before the change took place, you'll see the old app ID.
matchboxbananasynergy will this be changing in the future?
I plan to factory reset anyways but I would like to know
Lusca No, existing installs are deliberately remaining on the old app ID in order to preserve app data.
7 days later
So the fix that was included in the Bitwarden update today to 2023.1 won't fix the issue of it not working on the old org.chromium.chrome?
I just installed the update and the auto fill still doesn't work. Is there a fix for the old variant?
- Edited
Bitwarden Version: 2023.1.0 (5786)
GoS: TQ1A.230105.001.A2.2023011000
Vanadium: org.chromium.chrome
Bitwarden is not auto filling in vanadium for me either.
22 days later
spiral For me the same. I am a new GrapheneOS user. I have to say, it was not easy to get a working combination of Bitwarden and autofill logon-data in any browser. I tried many browsers but only Firefox is working with Bitwarden. But ... don't forget to enable the autofill option in Bitwarden!