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

[GH-ISSUE #5444] Autofill Prompt Flickers and Disappears on Android 15 with Chrome #21526

New Issue
Closed
opened 2026-04-16 22:03:47 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-16 22:03:47 -05:00
Owner
Copy Link

Originally created by @zeewer on GitHub (Jun 29, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5444

Steps To Reproduce

On the specified device and OS, open the Google Chrome browser.
2. Navigate to any website with a login form (e.g., a banking site, or even https://vault.bitwarden.com).
3. Tap on the password input field.

Expected Result

The Bitwarden autofill prompt should appear above the keyboard and remain stable, allowing the user to click it to unlock the vault and fill the credentials.

Actual Result

The Bitwarden autofill prompt appears for a fraction of a second and then immediately disappears. It is not possible to interact with it.

To make the prompt appear correctly, I have to alternately tap the username and password fields multiple times. After several attempts, the prompt sometimes stabilizes, allowing me to click it.

Screenshots or Videos

https://github.com/user-attachments/assets/d4d4d5b9-94b3-4d36-b3a2-e8721b3afade

Additional Context

This issue appears to be specific to Google Chrome.

  • The autofill functionality works perfectly as expected in the Firefox browser on the same device.
  • This suggests a potential compatibility issue between Bitwarden's autofill service, the latest version of Chrome, and possibly the specific implementation of Android 15 (MIUI) on this device.

Build Version

2025.5.0 (20269)

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

  • Device: Redmi Note 13 Pro 5G (Model: 2312DRA50G) **
  • OS version: Xiaomi HyperOS 2.0.10.0.VNREUXM
  • Operating System: Android 15 (Build: AQ3A.240912.001)
  • Problematic Application: Google Chrome (Version: 137.0.7151.115)
  • Bitwarden Version: 2025.5.0 (20269)

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 @zeewer on GitHub (Jun 29, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5444 ### Steps To Reproduce On the specified device and OS, open the Google Chrome browser. 2. Navigate to any website with a login form (e.g., a banking site, or even https://vault.bitwarden.com). 3. Tap on the password input field. ### Expected Result The Bitwarden autofill prompt should appear above the keyboard and remain stable, allowing the user to click it to unlock the vault and fill the credentials. ### Actual Result The Bitwarden autofill prompt appears for a fraction of a second and then immediately disappears. It is not possible to interact with it. To make the prompt appear correctly, I have to alternately tap the username and password fields multiple times. After several attempts, the prompt sometimes stabilizes, allowing me to click it. ### Screenshots or Videos https://github.com/user-attachments/assets/d4d4d5b9-94b3-4d36-b3a2-e8721b3afade ### Additional Context This issue appears to be specific to Google Chrome. * **The autofill functionality works perfectly as expected in the Firefox browser on the same device.** * This suggests a potential compatibility issue between Bitwarden's autofill service, the latest version of Chrome, and possibly the specific implementation of Android 15 (MIUI) on this device. ### Build Version 2025.5.0 (20269) ### What server are you connecting to? EU ### Self-host Server Version _No response_ ### Environment Details * **Device:** Redmi Note 13 Pro 5G (Model: 2312DRA50G) ** * OS version: Xiaomi HyperOS 2.0.10.0.VNREUXM * **Operating System:** Android 15 (Build: AQ3A.240912.001) * **Problematic Application:** Google Chrome (Version: 137.0.7151.115) * **Bitwarden Version:** 2025.5.0 (20269) ### 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-16 22:03:47 -05:00
GiteaMirror commented 2026-04-16 22:03:50 -05:00
Author
Owner
Copy Link

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

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

<!-- gh-comment-id:3016626307 --> @bitwarden-bot commented on GitHub (Jun 29, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-23146
GiteaMirror commented 2026-04-16 22:03:51 -05:00
Author
Owner
Copy Link

@rmcdowell-bitwarden commented on GitHub (Jun 30, 2025):

Hi there!

Thank you for your report, it seems like it is a duplicate of this one https://github.com/bitwarden/android/issues/5278.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these.

This issue will now be closed.

Thanks!

<!-- gh-comment-id:3018131586 --> @rmcdowell-bitwarden commented on GitHub (Jun 30, 2025): Hi there! Thank you for your report, it seems like it is a duplicate of this one https://github.com/bitwarden/android/issues/5278. If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these. This issue will now be closed. Thanks!
GiteaMirror commented 2026-04-16 22:03:51 -05:00
Author
Owner
Copy Link

@zeewer commented on GitHub (Jun 30, 2025):

Hi, the diference is that, for me, it works in Firefox without problem.

The other user reported that it doesn't work in any browser.

Best regards,
Zeljko

pon, 30. lip 2025. 09:44 rmcdowell-bitwarden @.***> je
napisao:

rmcdowell-bitwarden left a comment (bitwarden/android#5444)
https://github.com/bitwarden/android/issues/5444#issuecomment-3018131586

Hi there!

Thank you for your report, it seems like it is a duplicate of this one
#5278 https://github.com/bitwarden/android/issues/5278.

If you wish to add any further information/screenshots/recordings etc.,
please feel free to do so at any time in there - our engineering team will
be happy to review these.

This issue will now be closed.

Thanks!

—
Reply to this email directly, view it on GitHub
https://github.com/bitwarden/android/issues/5444#issuecomment-3018131586,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BUCXTG6U254CPP35RHTMLSD3GDTETAVCNFSM6AAAAACAMDGQVWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMJYGEZTCNJYGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:3018315716 --> @zeewer commented on GitHub (Jun 30, 2025): Hi, the diference is that, for me, it works in Firefox without problem. The other user reported that it doesn't work in any browser. Best regards, Zeljko pon, 30. lip 2025. 09:44 rmcdowell-bitwarden ***@***.***> je napisao: > *rmcdowell-bitwarden* left a comment (bitwarden/android#5444) > <https://github.com/bitwarden/android/issues/5444#issuecomment-3018131586> > > Hi there! > > Thank you for your report, it seems like it is a duplicate of this one > #5278 <https://github.com/bitwarden/android/issues/5278>. > > If you wish to add any further information/screenshots/recordings etc., > please feel free to do so at any time in there - our engineering team will > be happy to review these. > > This issue will now be closed. > > Thanks! > > — > Reply to this email directly, view it on GitHub > <https://github.com/bitwarden/android/issues/5444#issuecomment-3018131586>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BUCXTG6U254CPP35RHTMLSD3GDTETAVCNFSM6AAAAACAMDGQVWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMJYGEZTCNJYGY> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
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#21526
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?