github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-08 04:16:40 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

Brave Android app auto fill not working in http websites #2265

New Issue
Closed
opened 2025-11-26 23:13:41 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-26 23:13:41 -06:00
Owner
Copy Link

Originally created by @dkorecko on GitHub (Jun 24, 2025).

Steps To Reproduce

  1. Open Brave (Bitwarden installed, all methods of auto-fill enabled, Bitwarden set in Android and Brave)
  2. Navigate to any http website that you know works in Brave extension on desktop

Expected Result

Same as happens in the Brave browser with the Bitwarden browser extension, credentials should be filled in properly since it's the same website.

Actual Result

No auto-fill shows up when opening the page/clicking on any of the fields. Also, when holding down on the password field and pressing Autofill, nothing is filled in. On other sites (that have https) this does not happen on mobile. Additionally, this specific self-hosted website has no issues on Brave desktop.

Screenshots or Videos

No response

Additional Context

Same auto-fill not working happens on all my self-hosted services (only on Android).

Build Version

2025.5.0 20269

What server are you connecting to?

Self-host

Self-host Server Version

1.34.1

Environment Details

  • Device: Samsung Galaxy S24+
  • OS Version: One UI 7
  • Keyboard: Gboard
  • Browser: Brave 1.79.126, Chromium 137.0.7151.119

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 @dkorecko on GitHub (Jun 24, 2025). ### Steps To Reproduce 1. Open Brave (Bitwarden installed, all methods of auto-fill enabled, Bitwarden set in Android and Brave) 2. Navigate to any http website that you know works in Brave extension on desktop ### Expected Result Same as happens in the Brave browser with the Bitwarden browser extension, credentials should be filled in properly since it's the same website. ### Actual Result No auto-fill shows up when opening the page/clicking on any of the fields. Also, when holding down on the password field and pressing Autofill, nothing is filled in. On other sites (that have https) this does not happen on mobile. Additionally, this specific self-hosted website has no issues on Brave desktop. ### Screenshots or Videos _No response_ ### Additional Context Same auto-fill not working happens on all my self-hosted services (only on Android). ### Build Version 2025.5.0 20269 ### What server are you connecting to? Self-host ### Self-host Server Version 1.34.1 ### Environment Details - Device: Samsung Galaxy S24+ - OS Version: One UI 7 - Keyboard: Gboard - Browser: Brave 1.79.126, Chromium 137.0.7151.119 ### 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.
GiteaMirror added the app:password-managerbug labels 2025-11-26 23:13:41 -06:00
GiteaMirror commented 2025-11-26 23:13:41 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Jun 24, 2025):

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

@bitwarden-bot commented on GitHub (Jun 24, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-22981
GiteaMirror commented 2025-11-26 23:13:42 -06:00
Author
Owner
Copy Link

@Krychaz commented on GitHub (Jun 24, 2025):

Hello there,

Can you please confirm which version of Bitwarden you are self-hosting?

@Krychaz commented on GitHub (Jun 24, 2025): Hello there, Can you please confirm which version of Bitwarden you are self-hosting?
GiteaMirror commented 2025-11-26 23:13:42 -06:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Jun 24, 2025):

@Krychaz, maybe a coincidence, but 1.34.1 is also the latest Vaultwarden version.

@pamperer562580892423 commented on GitHub (Jun 24, 2025): @Krychaz, maybe a coincidence, but 1.34.1 is also the latest Vaultwarden version.
GiteaMirror commented 2025-11-26 23:13:42 -06:00
Author
Owner
Copy Link

@dkorecko commented on GitHub (Jun 24, 2025):

Yep, just a confused person, I am actually self-hosting Vaultwarden. Did not occur to me I would be posting there since this seemed like purely a client-side issue, but I also didn't notice the note in Vaultwarden to post everything there, even issues with clients.

So this can be closed here and I can go there I assume?

@dkorecko commented on GitHub (Jun 24, 2025): Yep, just a confused person, I am actually self-hosting Vaultwarden. Did not occur to me I would be posting there since this seemed like purely a client-side issue, but I also didn't notice the note in Vaultwarden to post everything there, even issues with clients. So this can be closed here and I can go there I assume?
GiteaMirror commented 2025-11-26 23:13:42 -06:00
Author
Owner
Copy Link

@Krychaz commented on GitHub (Jun 24, 2025):

Correct. Vaultwarden Github page would be the place to ask.

@Krychaz commented on GitHub (Jun 24, 2025): Correct. Vaultwarden Github page would be the place to ask.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#2265
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?