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

[GH-ISSUE #5273] Android with physical keyboard no auto fill prompt. Sporadic sucess using autofill icon in settings #50323

New Issue
Closed
opened 2026-05-01 12:29:01 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-05-01 12:29:01 -05:00
Owner
Copy Link

Originally created by @Charles226 on GitHub (May 28, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5273

Steps To Reproduce

Using a Samsung Tablet S8+ with bookcover keyboard attached. Because physical keyboard is attached there's no virtual keyboard that displays the bitwarden prompt when on login page for website. The inline autofill option on website doesn't prompt on android browsers Firefox/Samsung Internet like it does on desktop browser with extension installed. Using the auto-fill button within android settings has hit and miss results.

One UI: 6.1.1
Android: 14
Firefox: 138.0.4
Bitwarden: 2025.4.0 (20100)

  1. Go to www.linkedin.com on Firefox browser
  2. Click on sign in
  3. Click into Username/Password field (no prompt)
  4. Click on auto fill service in android settings > directs to bitwarden stored credentials for linkedin as expected. Click on credentials. Redirects back to linkedin login page but hasn't populated stored credentials into fields.

The autofill settings icon did work as expected for the bitwarden community page. However I still think the lack of autofill option when physical keyboard is attached and the failure of autofill icon within settings to populate linkedin web page merits this to be a bug report

Expected Result

2 Secnarios.

Scenario 1 - Webpage inline autofill supported

  1. Android device has physical keyboard attatchd
  2. Navigate to linkedin.com login page
  3. Bitarden auto prompts on Username/Password field within web page for stored credentials

Scenario 2 - Conistent Anroid auto-fill option setting

  1. Navigate to linkedin.com login page
  2. Swipe down in top right of android and select bitwarden autofill icon
  3. Directed to vault stored credentals for linkedin
  4. Click credentials
  5. Redirected back to linkedin page with username/password filled in

Actual Result

Scenario 1
android with physical keyboard attachd

  1. Navigate to website linkedin.com
  2. No inline auto fill option on web page
  3. No prompt for bitwarden due to virtual keyboard not displayed as physical keyboard attached

Scenario 2.
Using android autofill bitwarden settings icon

1-4 working as expected
5 - Redirect back to linkedin login page with username and password fields still empty

Screenshots or Videos

No response

Additional Context

No response

Build Version

2025.4.0 (20100)

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

Samsung Galaxy Tablet S8+
One UI: 6.1.1
Android: 14
Firefox: 138.0.4
Bitwarden: 2025.4.0 (20100)

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 @Charles226 on GitHub (May 28, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5273 ### Steps To Reproduce Using a Samsung Tablet S8+ with bookcover keyboard attached. Because physical keyboard is attached there's no virtual keyboard that displays the bitwarden prompt when on login page for website. The inline autofill option on website doesn't prompt on android browsers Firefox/Samsung Internet like it does on desktop browser with extension installed. Using the auto-fill button within android settings has hit and miss results. One UI: 6.1.1 Android: 14 Firefox: 138.0.4 Bitwarden: 2025.4.0 (20100) 1. Go to www.linkedin.com on Firefox browser 2. Click on sign in 3. Click into Username/Password field (no prompt) 4. Click on auto fill service in android settings > directs to bitwarden stored credentials for linkedin as expected. Click on credentials. Redirects back to linkedin login page but hasn't populated stored credentials into fields. The autofill settings icon did work as expected for the bitwarden community page. However I still think the lack of autofill option when physical keyboard is attached and the failure of autofill icon within settings to populate linkedin web page merits this to be a bug report ### Expected Result 2 Secnarios. Scenario 1 - Webpage inline autofill supported 1. Android device has physical keyboard attatchd 2. Navigate to linkedin.com login page 3. Bitarden auto prompts on Username/Password field within web page for stored credentials Scenario 2 - Conistent Anroid auto-fill option setting 1. Navigate to linkedin.com login page 2. Swipe down in top right of android and select bitwarden autofill icon 3. Directed to vault stored credentals for linkedin 4. Click credentials 5. Redirected back to linkedin page with username/password filled in ### Actual Result Scenario 1 android with physical keyboard attachd 1. Navigate to website linkedin.com 2. No inline auto fill option on web page 3. No prompt for bitwarden due to virtual keyboard not displayed as physical keyboard attached Scenario 2. Using android autofill bitwarden settings icon 1-4 working as expected 5 - Redirect back to linkedin login page with username and password fields still empty ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 2025.4.0 (20100) ### What server are you connecting to? EU ### Self-host Server Version _No response_ ### Environment Details Samsung Galaxy Tablet S8+ One UI: 6.1.1 Android: 14 Firefox: 138.0.4 Bitwarden: 2025.4.0 (20100) ### 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-05-01 12:29:01 -05:00
GiteaMirror commented 2026-05-01 12:29:04 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (May 28, 2025):

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

<!-- gh-comment-id:2914740453 --> @bitwarden-bot commented on GitHub (May 28, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-22137
GiteaMirror commented 2026-05-01 12:29:04 -05:00
Author
Owner
Copy Link

@rmcdowell-bitwarden commented on GitHub (May 29, 2025):

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

<!-- gh-comment-id:2918145999 --> @rmcdowell-bitwarden commented on GitHub (May 29, 2025): Hi there, I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below. Thanks!
GiteaMirror commented 2026-05-01 12:29:04 -05:00
Author
Owner
Copy Link

@brentbrownfield commented on GitHub (Jun 1, 2025):

I am experiencing a similar issue with a Galaxy S10+:
Device Model: Samsung Galaxy Tab S10+

Android Version: Android 15 with One UI 7

Bitwarden Version: 2025.4.0

Issue Description: Autofill prompts do not appear when a physical keyboard is connected, but function correctly when the keyboard is detached.

Steps to Reproduce:

  1. Connect the physical keyboard to the device.

  2. Navigate to a login page in Firefox 138.0.4.

  3. Attempt to use Bitwarden's autofill feature.

Expected Behavior: Autofill prompt should appear regardless of keyboard connection.

Actual Behavior: Autofill prompt does not appear when the physical keyboard is connected.

Additional Notes: Mention that enabling "Show on-screen keyboard" in the device settings resolves the issue, suggesting a link between the on-screen keyboard and the autofill prompt.

<!-- gh-comment-id:2927466721 --> @brentbrownfield commented on GitHub (Jun 1, 2025): I am experiencing a similar issue with a Galaxy S10+: Device Model: Samsung Galaxy Tab S10+ Android Version: Android 15 with One UI 7 Bitwarden Version: 2025.4.0 Issue Description: Autofill prompts do not appear when a physical keyboard is connected, but function correctly when the keyboard is detached. Steps to Reproduce: 1. Connect the physical keyboard to the device. 2. Navigate to a login page in Firefox 138.0.4. 3. Attempt to use Bitwarden's autofill feature. Expected Behavior: Autofill prompt should appear regardless of keyboard connection. Actual Behavior: Autofill prompt does not appear when the physical keyboard is connected. Additional Notes: Mention that enabling "Show on-screen keyboard" in the device settings resolves the issue, suggesting a link between the on-screen keyboard and the autofill prompt.
GiteaMirror commented 2026-05-01 12:29:05 -05:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Feb 11, 2026):

⚠️ Stale Issue Notice

This issue has been automatically marked as stale due to inactivity. It will be closed in 2 weeks (February 25, 2026) if no further activity occurs.

If this issue is still relevant and you would like to keep it open, please:

  • Comment on this issue to show continued interest
  • Provide any additional information or updates
  • Confirm that the issue still exists in the latest version

Thank you for your contribution to this project! 🙏

<!-- gh-comment-id:3886595338 --> @closebot-bw commented on GitHub (Feb 11, 2026): ⚠️ **Stale Issue Notice** This issue has been automatically marked as stale due to inactivity. It will be closed in **2 weeks** (February 25, 2026) if no further activity occurs. If this issue is still relevant and you would like to keep it open, please: - Comment on this issue to show continued interest - Provide any additional information or updates - Confirm that the issue still exists in the latest version Thank you for your contribution to this project! 🙏
GiteaMirror commented 2026-05-01 12:29:06 -05:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Feb 23, 2026):

🔔 Final Notice - Issue Will Be Closed Soon

This issue was previously marked as stale and will be automatically closed in 2 days (February 25, 2026) if no further activity occurs.

If you're still experiencing this issue or believe it should remain open, please comment below to prevent automatic closure.

We appreciate your understanding and contribution to keeping our issue tracker organized! 📋

<!-- gh-comment-id:3946972509 --> @closebot-bw commented on GitHub (Feb 23, 2026): 🔔 **Final Notice - Issue Will Be Closed Soon** This issue was previously marked as stale and will be automatically closed in **2 days** (February 25, 2026) if no further activity occurs. If you're still experiencing this issue or believe it should remain open, please comment below to prevent automatic closure. We appreciate your understanding and contribution to keeping our issue tracker organized! 📋
GiteaMirror commented 2026-05-01 12:29:07 -05:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Feb 25, 2026):

🔒 Issue Closed Due to Inactivity

This issue has been automatically closed due to lack of activity for an extended period. We periodically review and close inactive issues to help maintain our issue tracker and focus on current priorities.

If this issue is still relevant:

  • Please create a new issue with updated information
  • Include steps to reproduce the problem if it's a bug report
  • Mention if this issue still occurs in the latest version

Thank you for your contribution to this project. Your feedback helps us improve! 🙏

<!-- gh-comment-id:3961978744 --> @closebot-bw commented on GitHub (Feb 25, 2026): 🔒 **Issue Closed Due to Inactivity** This issue has been automatically closed due to lack of activity for an extended period. We periodically review and close inactive issues to help maintain our issue tracker and focus on current priorities. **If this issue is still relevant:** - Please create a new issue with updated information - Include steps to reproduce the problem if it's a bug report - Mention if this issue still occurs in the latest version Thank you for your contribution to this project. Your feedback helps us improve! 🙏
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#50323
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?