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.

        2 months later

        I finally manage to make Bitwarden autofill work in Brave without Gplay services.
        I had to set brave://flags #enable-autofill-virtual-view-structure on enable without compatibility check.

        Then you'll have a new Autofill Options in the General settings that allows you to switch from Brave Autofill to Android Autofill.

          user Ive repeated these steps, but do not see an option to switch to android autofill in the brave settings anywhere