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

[GH-ISSUE #5844] [PM-25532] Clicking autofill still leaves password/username blank #14981

New Issue
Closed
opened 2026-04-15 01:14:24 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-04-15 01:14:24 -05:00
Owner
Copy Link

Originally created by @dg1234567 on GitHub (Sep 5, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5844

Steps To Reproduce

  1. Go to any website to sign in
  2. Click on autofill with bitwarden
  3. Scroll down to login for that website
  4. Click on the login

Expected Result

Autofills username and/or password

Actual Result

Leaves the box empty despite multiple tries however every now and then it does work

Screenshots or Videos

No response

Additional Context

No response

Build Version

© Bitwarden Inc. 2015-2025 Version: 2025.8.1 (20670) 📱 samsung SM-S931U 🤖 15@35 📦 prod 🧱 commit: bitwarden/android/release/2025.8-rc33@b497156302a73fd2b14de16106dc218c30ec1702 💻 build source: bitwarden/android/actions/runs/17277676605/attempts/1 🦀 SDK: 1.0.0-2450-9fe3aeda 🌩 Server: 2025.8.1 @ US

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Galaxy S25
ONE UI 7

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 @dg1234567 on GitHub (Sep 5, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5844 ### Steps To Reproduce 1. Go to any website to sign in 2. Click on autofill with bitwarden 3. Scroll down to login for that website 4. Click on the login ### Expected Result Autofills username and/or password ### Actual Result Leaves the box empty despite multiple tries however every now and then it does work ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version © Bitwarden Inc. 2015-2025 Version: 2025.8.1 (20670) 📱 samsung SM-S931U 🤖 15@35 📦 prod 🧱 commit: bitwarden/android/release/2025.8-rc33@b497156302a73fd2b14de16106dc218c30ec1702 💻 build source: bitwarden/android/actions/runs/17277676605/attempts/1 🦀 SDK: 1.0.0-2450-9fe3aeda 🌩 Server: 2025.8.1 @ US ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details Galaxy S25 ONE UI 7 ### 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 app:password-managerbug labels 2026-04-15 01:14:24 -05:00
GiteaMirror commented 2026-04-15 01:14:26 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Sep 5, 2025):

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

<!-- gh-comment-id:3259128143 --> @bitwarden-bot commented on GitHub (Sep 5, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-25532
GiteaMirror commented 2026-04-15 01:14:26 -05:00
Author
Owner
Copy Link

@iamperson347 commented on GitHub (Sep 7, 2025):

Seems to be happening to me quite a bit as well. Interestingly, if the vault is locked and you unlock it, after performing auto fill my inline bitwarden icon still says locked though it isn't.

<!-- gh-comment-id:3263305328 --> @iamperson347 commented on GitHub (Sep 7, 2025): Seems to be happening to me quite a bit as well. Interestingly, if the vault is locked and you unlock it, after performing auto fill my inline bitwarden icon still says locked though it isn't.
GiteaMirror commented 2026-04-15 01:14:27 -05:00
Author
Owner
Copy Link

@dg1234567 commented on GitHub (Sep 7, 2025):

I have mine set to lock immediately. I wonder if it's an issue with the inline keyboard not communicating properly with the vault?> Seems to be happening to me quite a bit as well. Interestingly, if the vault is locked and you unlock it, after performing auto fill my inline bitwarden icon still says locked though it isn't.

<!-- gh-comment-id:3263336478 --> @dg1234567 commented on GitHub (Sep 7, 2025): I have mine set to lock immediately. I wonder if it's an issue with the inline keyboard not communicating properly with the vault?> Seems to be happening to me quite a bit as well. Interestingly, if the vault is locked and you unlock it, after performing auto fill my inline bitwarden icon still says locked though it isn't.
GiteaMirror commented 2026-04-15 01:14:27 -05:00
Author
Owner
Copy Link

@cbbit commented on GitHub (Sep 7, 2025):

@dg1234567

Hi there!

Thank you for your report. Due to recent changes from the Android team, Chromium browsers now require you to choose between using Chrome/Brave autofill or by using another service (like Bitwarden).

Chromium Browser autofill:

  1. Ensure Chrome/Brave and Bitwarden are updated

  2. In Bitwarden, visit Settings > Autofill > use Chrome/Brave Autofill integration > Autofill using another service

  3. Select the restart Chrome/Brave button

Android Device autofill:

  1. In Bitwarden, visit Settings > Autofill > Autofill services > choose Bitwarden as your preferred service for passwords, passkeys, & autofill

  2. Choose between inline or popup

Troubleshooting:

If you previously changed any browser autofill feature flags, you may need to reset them now to prevent autofill from breaking with the Chrome autofill framework.

-You may need to disable/re-enable settings

-You may need to uninstall, power cycle your device, and then reinstall the app

https://bitwarden.com/help/auto-fill-android/#set-up-autofill

https://bitwarden.com/help/auto-fill-android-troubleshooting/

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:3263800472 --> @cbbit commented on GitHub (Sep 7, 2025): @dg1234567 Hi there! Thank you for your report. Due to recent changes from the Android team, Chromium browsers now require you to choose between using Chrome/Brave autofill or by using another service (like Bitwarden). **Chromium Browser autofill:** 1) Ensure Chrome/Brave and Bitwarden are updated 2) In Bitwarden, visit **Settings** > **Autofill** > **use Chrome/Brave Autofill integration** > **Autofill using another service** 3) Select the restart Chrome/Brave button **Android Device autofill:** 1) In Bitwarden, visit **Settings** > **Autofill** > **Autofill services** > choose **Bitwarden** as your preferred service for passwords, passkeys, & autofill 2) Choose between inline or popup **Troubleshooting:** If you previously changed any browser autofill feature flags, you may need to reset them now to prevent autofill from breaking with the Chrome autofill framework. -You may need to disable/re-enable settings -You may need to uninstall, power cycle your device, and then reinstall the app https://bitwarden.com/help/auto-fill-android/#set-up-autofill https://bitwarden.com/help/auto-fill-android-troubleshooting/ 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!
GiteaMirror commented 2026-04-15 01:14:28 -05:00
Author
Owner
Copy Link

@iamperson347 commented on GitHub (Sep 7, 2025):

I've tried toggling quite a few times previously and the issue sometimes temporarily resolve but come back. I've tried resetting feature flags to default (don't think I had any enabled) and retoggled autofill setting. Will monitor and write support if the issue persists.

<!-- gh-comment-id:3263818638 --> @iamperson347 commented on GitHub (Sep 7, 2025): I've tried toggling quite a few times previously and the issue sometimes temporarily resolve but come back. I've tried resetting feature flags to default (don't think I had any enabled) and retoggled autofill setting. Will monitor and write support if the issue persists.
GiteaMirror commented 2026-04-15 01:14:29 -05:00
Author
Owner
Copy Link

@innit86 commented on GitHub (Sep 18, 2025):

Happens a lot to me, too. Sometimes clicking on password first and then username helps to get autofill to work as intended.

<!-- gh-comment-id:3308223813 --> @innit86 commented on GitHub (Sep 18, 2025): Happens a lot to me, too. Sometimes clicking on password first and then username helps to get autofill to work as intended.
GiteaMirror commented 2026-04-15 01:14:29 -05:00
Author
Owner
Copy Link

@MrSourceUnknown commented on GitHub (Sep 18, 2025):

@dg1234567

Hi there!

Thank you for your report. Due to recent changes from the Android team, Chromium browsers now require you to choose between using Chrome/Brave autofill or by using another service (like Bitwarden).

Hello @cbbit, why are reports like this being closed as user error??

Even with the new "Use Chrome autofill integration" option properly enabled, making sure there are no conflicting settings and toggling the feature off and on again, the Autofill behavior still stops working constantly.

When this happens the Autofill bar shows, the account selection shows, but tapping the account doesn't populate the username and password fields at all.

The only workaround for this is Force closing either the Bitwarden app or the Browser. After that it immediately starts working again.

This should be Reopened and addressed properly!

<!-- gh-comment-id:3309176736 --> @MrSourceUnknown commented on GitHub (Sep 18, 2025): > [@dg1234567](https://github.com/dg1234567) > > Hi there! > > Thank you for your report. Due to recent changes from the Android team, Chromium browsers now require you to choose between using Chrome/Brave autofill or by using another service (like Bitwarden). > Hello @cbbit, why are reports like this being closed as user error?? Even with the new "Use Chrome autofill integration" option properly enabled, making sure there are no conflicting settings and toggling the feature off and on again, the Autofill behavior still stops working constantly. When this happens the Autofill bar shows, the account selection shows, but tapping the account doesn't populate the username and password fields at all. The only workaround for this is Force closing either the Bitwarden app or the Browser. After that it immediately starts working again. This should be Reopened and addressed properly!
GiteaMirror commented 2026-04-15 01:14:29 -05:00
Author
Owner
Copy Link

@iamperson347 commented on GitHub (Sep 18, 2025):

I entered a support ticket and they stated engineering is aware of the issue... But it definitely feels like the issue shouldn't be closed here.

<!-- gh-comment-id:3309749701 --> @iamperson347 commented on GitHub (Sep 18, 2025): I entered a support ticket and they stated engineering is aware of the issue... But it definitely feels like the issue shouldn't be closed here.
GiteaMirror commented 2026-04-15 01:14:30 -05:00
Author
Owner
Copy Link

@Tipoff4317 commented on GitHub (Sep 19, 2025):

They just released the v2025.9.0 that has this changelog:

  • Fixed an issue where autofill logins could disappear.
<!-- gh-comment-id:3310375863 --> @Tipoff4317 commented on GitHub (Sep 19, 2025): They just released the [v2025.9.0](https://github.com/bitwarden/android/releases/tag/v2025.9.0-bwpm) that has this changelog: - Fixed an issue where autofill logins could disappear.
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#14981
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?