Hi, it's great to see finally Bitwarden autofill worked with Vanadium. However, now I can't use the autofill on Brave anymore. The bitwarden vault wont show up at the top of my keyboard.

Previously, it worked for Brave but not Vanadium. Ever since it's fixed for Vanadium, I've had issues with Brave. Does anyone else have the same problem?

Edit: bitwarden works on brave on my stock android

Hey there. Can you let us know what your autofill settings look like for Bitwarden? (A screenshot would be ideal - here are steps on how to attach one in the forum: https://discuss.grapheneos.org/d/72-discussion-forum-markdown-syntax-and-image-support-via-our-media-proxy)

What I think is likely happening here is that you were using Bitwarden's accessibility setting for Autofill, and stopped using it when Vanadium got Autofill support, which made it stop working on Brave.

EDIT: My theory seems very likely after finding this - https://github.com/brave/brave-browser/issues/25955

My guess is that you were using the accessibility option for Bitwarden, which Vanadium no longer needs because it has proper Autofill support, and when you disabled that option, you lost the ability to do Autofill in Brave.

Marking as solved as this is likely the cause. If it isn't, let us know.

    matchboxbananasynergy you're right in saying that I used to turn the accessibility setting on and then turned it off now that vanadium supports autofill. Is there a solution to this? I'd rather not use accessibility and give BW permissions more than necessary.

    My BW autofill settings are now only with autofill service and use inline autofill. The accessibility and drawover are off.

    Edit: my stock android BW also doesnt have accessibility on to make BW works on Brave. So I'm guessing what you explained only applied to Graphene when it was on then turned off.

      Update: I tried reinstalling BW and then Brave hoping that it "forgets" the accessibility was ever turned on, but it still doesn't work.

      20 days later
      2 months later
      4 months later
      • [deleted]

      • Edited

      It still doesn't work ! 🙄
      Play services installed
      Bitwarden does not have overlay nor accessibility, only the two first permissions.
      Nevers used overlay and accessibility.

      For what it's worth, Proton has said autofill is an issue specifically with Graphene devices using Brave. I wish Proton, Brave, Bitwarden, Graphene could work together to fix it, assuming they're not.

      2 months later
      a month later

      Can confirm this issue (auto-fill does not work in Brave browser but does in Vanadium). This also appears to be a commonly reported issue both here and on Brave's forums:

      https://discuss.grapheneos.org/d/1435-bitwarden-not-working-in-vanadium-brave
      https://discuss.grapheneos.org/d/6803-brave-password-autofill-from-bitwarden-stopped-working
      https://discuss.grapheneos.org/d/6539-bitwarden-and-brave
      https://community.brave.com/t/autofill-not-working-reliably-with-bitwarden-or-keepass2android/70464/18

      I reached out to Bitwarden for support and after troubleshooting and confirming that auto-fill from Bitwarden appears to work fine in Vanadium, it was their opinion that the issue is with GrapheneOS. @matchboxbananasynergy is it appropriate to open an issue here for this? Thanks!

        I'm not sure its a graphene issue. Bitwarden autofill works on pretty much every browser ive tested on graphene, except brave. That would mean its a brave issue. I Dont believe brave on graphene supports inline autofill

        I think this quote by a GrapheneOS developer might clarify the situation somewhat:

        They could add native autofill support. They appear to only have Google autofill API support, which means you need sandboxed Google Play. It's possible that feature broke with sandboxed Google Play at some point but we aren't aware of it and Brave not having working autofill isn't enough to assume it's the problem.

          Relaks I have sandboxed play services installed, and it still doesnt work. I am fairly certain this problem lies on braves end

          Relaks Thank you! Sorry I missed that. I agree a lot of the evidence points towards Brave. I only started here on the advice of Bitwarden's support. I'll see if this issue can get any attention from Brave's community.