[GH-ISSUE #5424] Autofill quick setting/tile fails on passwordless pages #102321

Closed
opened 2026-06-03 02:05:43 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @aand18 on GitHub (Jun 25, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5424

Steps To Reproduce

  1. Go to https://x.com/i/flow/login
  2. Pull down the Android quick settings drawer from the top of the screen and tap Bitwarden's "Autofill" button

Expected Result

Fills in the fields present in the page (user/email in this case).

Actual Result

You get a toaster "No password fields detected".

Screenshots or Videos

Image

Additional Context

Autofill on paswordless pages used to work before the UI overhaul a few months ago, not sure why this check for a password field was recently introduced...

Build Version

2025.5.0 (20269) 📱 samsung 🤖 14@34 📦 prod 🧱 commit: bitwarden/android/release/2025.05-rc20@1e665db8aeb92989bdc7e312506cddd4887cde8e 💻 build source: bitwarden/android/actions/runs/15300207138/attempts/1

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

No response

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 @aand18 on GitHub (Jun 25, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5424 ### Steps To Reproduce 1. Go to https://x.com/i/flow/login 2. Pull down the Android quick settings drawer from the top of the screen and tap Bitwarden's "Autofill" button ### Expected Result Fills in the fields present in the page (user/email in this case). ### Actual Result You get a toaster "No password fields detected". ### Screenshots or Videos ![Image](https://github.com/user-attachments/assets/b913ce92-a46f-4b0d-98b8-844e9a7fb10e) ### Additional Context Autofill on paswordless pages used to work before the UI overhaul a few months ago, not sure why this check for a password field was recently introduced... ### Build Version 2025.5.0 (20269) 📱 samsung 🤖 14@34 📦 prod 🧱 commit: bitwarden/android/release/2025.05-rc20@1e665db8aeb92989bdc7e312506cddd4887cde8e 💻 build source: bitwarden/android/actions/runs/15300207138/attempts/1 ### What server are you connecting to? EU ### Self-host Server Version _No response_ ### Environment Details _No response_ ### 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-06-03 02:05:44 -05:00
Author
Owner

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

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

<!-- gh-comment-id:3006344316 --> @bitwarden-bot commented on GitHub (Jun 25, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-23055
Author
Owner

@cylayabw commented on GitHub (Jun 26, 2025):

Hi there!

We appreciate you letting us know of this issue. Due to the nature of autofill issues, we track them internally using different Forms depending on the platform:

mobile: https://docs.google.com/forms/d/e/1FAIpQLScMopHyN7KGJs8hW562VTzbIGL4KcFnx0wJcsW0GYE1BnPiGA/viewform

browser extension: https://docs.google.com/forms/d/e/1FAIpQLSfkxh1w6vK8fLYwAbAAEVhvhMAJwfFNDtYtPUVk1y5WTHvJmQ/viewform

In this case, we will go ahead and file an autofill report for you with the information you added here.

In the future, if you encounter any other page or app that doesn't autofill as expected, please avoid opening a new GitHub issue and go directly to the corresponding form.

This issue will now be closed.

Thanks!

<!-- gh-comment-id:3006892336 --> @cylayabw commented on GitHub (Jun 26, 2025): Hi there! We appreciate you letting us know of this issue. Due to the nature of autofill issues, we track them internally using different Forms depending on the platform: mobile: https://docs.google.com/forms/d/e/1FAIpQLScMopHyN7KGJs8hW562VTzbIGL4KcFnx0wJcsW0GYE1BnPiGA/viewform browser extension: https://docs.google.com/forms/d/e/1FAIpQLSfkxh1w6vK8fLYwAbAAEVhvhMAJwfFNDtYtPUVk1y5WTHvJmQ/viewform In this case, we will go ahead and file an autofill report for you with the information you added here. In the future, if you encounter any other page or app that doesn't autofill as expected, please avoid opening a new GitHub issue and go directly to the corresponding form. This issue will now be closed. Thanks!
Author
Owner

@aand18 commented on GitHub (Jun 26, 2025):

Ok.

I suggest you make the forms information more visible, e.g. put it as a comment in the GitHub issue template.

Too bad I can't track progress this way. Any idea when it will be fixed?

<!-- gh-comment-id:3007864965 --> @aand18 commented on GitHub (Jun 26, 2025): Ok. I suggest you make the forms information more visible, e.g. put it as a comment in the GitHub issue template. Too bad I can't track progress this way. Any idea when it will be fixed?
Author
Owner

@aand18 commented on GitHub (Aug 5, 2025):

@cylayabw any update on this regression? Is there any way for the public to get updates on these issues you track privately?

<!-- gh-comment-id:3155535346 --> @aand18 commented on GitHub (Aug 5, 2025): @cylayabw any update on this regression? Is there any way for the public to get updates on these issues you track privately?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#102321