[GH-ISSUE #6759] [PM-34633] Brave android autofill with popup option not working #39467

Closed
opened 2026-04-23 18:23:29 -05:00 by GiteaMirror · 10 comments
Owner

Originally created by @revolutionaryking7 on GitHub (Apr 4, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6759

Steps To Reproduce

Bitwarden I have enabled the settings " popup shows over input field" and in brave I have enabled autofill using another service but still I don't get password suggestions while clicking input field

Expected Result

Should show popup

Actual Result

Not showing

Screenshots or Videos

No response

Additional Context

No response

Build Version

21345

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Oneplus 15r, android 16

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Originally created by @revolutionaryking7 on GitHub (Apr 4, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6759 ### Steps To Reproduce Bitwarden I have enabled the settings " popup shows over input field" and in brave I have enabled autofill using another service but still I don't get password suggestions while clicking input field ### Expected Result Should show popup ### Actual Result Not showing ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 21345 ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details Oneplus 15r, android 16 ### Issue Tracking Info - [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
GiteaMirror added the bugapp:password-manager labels 2026-04-23 18:23:29 -05:00
Author
Owner

@bitwarden-bot commented on GitHub (Apr 4, 2026):

Thank you for your report! We've added this to our internal board for review.
ID: PM-34633

<!-- gh-comment-id:4186639853 --> @bitwarden-bot commented on GitHub (Apr 4, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-34633](https://bitwarden.atlassian.net/browse/PM-34633) [PM-34633]: https://bitwarden.atlassian.net/browse/PM-34633?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
Author
Owner

@pamperer562580892423 commented on GitHub (Apr 4, 2026):

Do you have a few example sites to reproduce this on?

<!-- gh-comment-id:4186920972 --> @pamperer562580892423 commented on GitHub (Apr 4, 2026): Do you have a few example sites to reproduce this on?
Author
Owner

@revolutionaryking7 commented on GitHub (Apr 4, 2026):

Do you have a few example sites to reproduce this on?

I found the cause...brave autofill integration is showing when brave stable is installed but not showing for brave beta or brave nightly...someone from BW need to add support for those 2 variants too...

<!-- gh-comment-id:4186983233 --> @revolutionaryking7 commented on GitHub (Apr 4, 2026): > Do you have a few example sites to reproduce this on? I found the cause...brave autofill integration is showing when brave stable is installed but not showing for brave beta or brave nightly...someone from BW need to add support for those 2 variants too...
Author
Owner

@MarikaBW commented on GitHub (Apr 5, 2026):

Hi there,

I attempted to reproduce your issue and was unable to do so. I think your error could have its origin in the version of Brave you are running; the Bitwarden browser extension is only supported on stable branches of browser releases.

We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/).

You can include a link to this issue in the message content.

Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/).

The issue here will be closed.

Thanks!

<!-- gh-comment-id:4188437335 --> @MarikaBW commented on GitHub (Apr 5, 2026): Hi there, I attempted to reproduce your issue and was unable to do so. I think your error could have its origin in the version of Brave you are running; the Bitwarden browser extension is only supported on stable branches of browser releases. We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/). You can include a link to this issue in the message content. Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/). The issue here will be closed. Thanks!
Author
Owner

@pamperer562580892423 commented on GitHub (Apr 5, 2026):

I think your error could have its origin in the version of Brave you are running; the Bitwarden browser extension is only supported on stable branches of browser releases.

@MarikaBW I think you meant to write "the Bitwarden Android mobile app"? (and not "the Bitwarden browser extension"?!)

<!-- gh-comment-id:4188725368 --> @pamperer562580892423 commented on GitHub (Apr 5, 2026): > I think your error could have its origin in the version of Brave you are running; the Bitwarden browser extension is only supported on stable branches of browser releases. @MarikaBW I think you meant to write "the Bitwarden Android mobile app"? (and not "the Bitwarden browser extension"?!)
Author
Owner

@MarikaBW commented on GitHub (Apr 5, 2026):

Apologies, that's correct! I meant the Bitwarden Android mobile app. Thanks for correcting me @pamperer562580892423

<!-- gh-comment-id:4189632256 --> @MarikaBW commented on GitHub (Apr 5, 2026): Apologies, that's correct! I meant the Bitwarden Android mobile app. Thanks for correcting me @pamperer562580892423
Author
Owner

@revolutionaryking7 commented on GitHub (Apr 14, 2026):

Still it is not clear why BW is supported in release version only? Why not beta or nightly? First of all , why need " use chrome/brave autofill integration"? All other password manager works without this...best example keepass dx

<!-- gh-comment-id:4243245742 --> @revolutionaryking7 commented on GitHub (Apr 14, 2026): Still it is not clear why BW is supported in release version only? Why not beta or nightly? First of all , why need " use chrome/brave autofill integration"? All other password manager works without this...best example keepass dx
Author
Owner

@pamperer562580892423 commented on GitHub (Apr 14, 2026):

First of all , why need " use chrome/brave autofill integration"? All other password manager works without this...best example keepass dx

From what I know (only another user): No, almost no other password manager now works "without this". Those were Chromium-changes, affecting all password managers in regards to how autofill works (or rather: it doesn't work without this new requirement from the browsers to use).

KeePassDX is different, because it uses autofill via an own keyboard. Bitwarden doesn't - and most other password managers don't - use an own keyboard component (on mobile) for autofill, therefor the new "browser autofill integration" is needed for autofill.

<!-- gh-comment-id:4243787670 --> @pamperer562580892423 commented on GitHub (Apr 14, 2026): > First of all , why need " use chrome/brave autofill integration"? All other password manager works without this...best example keepass dx From what I know (only another user): No, almost no other password manager now works "without this". Those were Chromium-changes, affecting all password managers in regards to how autofill works (or rather: it doesn't work without this new requirement from the browsers to use). KeePassDX is different, because it uses autofill via an own keyboard. Bitwarden doesn't - and most other password managers don't - use an own keyboard component (on mobile) for autofill, therefor the new "browser autofill integration" is needed for autofill.
Author
Owner

@pamperer562580892423 commented on GitHub (Apr 14, 2026):

@revolutionaryking7:

Still it is not clear why BW is supported in release version only? Why not beta or nightly?

Well, in a way, the BW setting for the "autofill integrations" is only a way to initiate this from the BW app. In fact, that changes a setting in the browser - and though there is no menu point for Brave Beta or Brave Nightly in the BW app, you can change that setting in Brave Beta and Brave Nightly yourself:

(Brave Beta/Nightly) --> Settings --> Autofill services --> Autofill using another service --> allow Brave to restart

PS: It should be enough to change that setting in the browser.

<!-- gh-comment-id:4244255888 --> @pamperer562580892423 commented on GitHub (Apr 14, 2026): @revolutionaryking7: > Still it is not clear why BW is supported in release version only? Why not beta or nightly? Well, in a way, the BW setting for the "autofill integrations" is only a way to initiate this from the BW app. In fact, that changes a setting in the browser - and though there is no menu point for Brave Beta or Brave Nightly in the BW app, you can change that setting in Brave Beta and Brave Nightly yourself: (Brave Beta/Nightly) --> Settings --> Autofill services --> Autofill using another service --> allow Brave to restart PS: It should be enough to change that setting in the browser.
Author
Owner

@revolutionaryking7 commented on GitHub (Apr 15, 2026):

@revolutionaryking7:

Still it is not clear why BW is supported in release version only? Why not beta or nightly?

Well, in a way, the BW setting for the "autofill integrations" is only a way to initiate this from the BW app. In fact, that changes a setting in the browser - and though there is no menu point for Brave Beta or Brave Nightly in the BW app, you can change that setting in Brave Beta and Brave Nightly yourself:

(Brave Beta/Nightly) --> Settings --> Autofill services --> Autofill using another service --> allow Brave to restart

PS: It should be enough to change that setting in the browser.

Yes I changed the settings to autofill using another service, but in beta popup not showing on clicking password field whereas in nightly it works after reloading or clicking multiple times on username/password field.

Regarding keepass dx, the popup working in all variant of brave .

<!-- gh-comment-id:4249734923 --> @revolutionaryking7 commented on GitHub (Apr 15, 2026): > [@revolutionaryking7](https://github.com/revolutionaryking7): > > > Still it is not clear why BW is supported in release version only? Why not beta or nightly? > > Well, in a way, the BW setting for the "autofill integrations" is only a way to initiate this from the BW app. In fact, that changes a setting in the browser - and though there is no menu point for Brave Beta or Brave Nightly in the BW app, you can change that setting in Brave Beta and Brave Nightly yourself: > > (Brave Beta/Nightly) --> Settings --> Autofill services --> Autofill using another service --> allow Brave to restart > > PS: It should be enough to change that setting in the browser. Yes I changed the settings to autofill using another service, but in beta popup not showing on clicking password field whereas in nightly it works after reloading or clicking multiple times on username/password field. Regarding keepass dx, the popup working in all variant of brave .
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#39467