github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-14 22:25:22 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

Bitwarden does not autofocus on Master Password field upon opening app #1924

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

Originally created by @jabashque on GitHub (Jun 28, 2024).

Bitwarden Beta

  • I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in bitwarden/mobile

Steps To Reproduce

  1. Configure Bitwarden to allow neither biometric unlocking nor pin unlocking.
  2. Close Bitwarden entirely. (Clear Bitwarden from the app switcher, and even force stop Bitwarden for good measure.)
  3. Open Bitwarden.

Expected Result

The Master Password field should immediately get focus once the app is loaded, resulting in the keyboard popping up.

Actual Result

The Master Password field does not immediately get focused on, and so the user has to tap on the Master Password field manually.

Screenshots or Videos

No response

Additional Context

This is a nitpick, but it would be good to have this to match the behavior of the old MAUI app.

Build Version

2024.6.1 (11139)

Environment Details

Device: OnePlus 8
OS: LineageOS 21 (Android 14 QPR3)

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 @jabashque on GitHub (Jun 28, 2024). ### Bitwarden Beta - [X] I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in [bitwarden/mobile](https://github.com/bitwarden/mobile) ### Steps To Reproduce 1. Configure Bitwarden to allow neither biometric unlocking nor pin unlocking. 2. Close Bitwarden entirely. (Clear Bitwarden from the app switcher, and even force stop Bitwarden for good measure.) 3. Open Bitwarden. ### Expected Result The Master Password field should immediately get focus once the app is loaded, resulting in the keyboard popping up. ### Actual Result The Master Password field does not immediately get focused on, and so the user has to tap on the Master Password field manually. ### Screenshots or Videos _No response_ ### Additional Context This is a nitpick, but it would be good to have this to match the behavior of the old MAUI app. ### Build Version 2024.6.1 (11139) ### Environment Details Device: OnePlus 8 OS: LineageOS 21 (Android 14 QPR3) ### 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 2025-11-26 23:01:51 -06:00
GiteaMirror commented 2025-11-26 23:01:52 -06:00
Author
Owner
Copy Link

@SergeantConfused commented on GitHub (Jun 29, 2024):

Hello @jabashque,

Thank you for your report. I see what you mean and have flagged it to the Engineering department.

Thank you again,

@SergeantConfused commented on GitHub (Jun 29, 2024): Hello @jabashque, Thank you for your report. I see what you mean and have flagged it to the Engineering department. Thank you again,
GiteaMirror commented 2025-11-26 23:01:52 -06:00
Author
Owner
Copy Link

@jabashque commented on GitHub (Aug 14, 2024):

Hi, after qwexter's changes in 2024.8.0, Bitwarden now autofocuses on the Master Password field on startup if Bitwarden wasn't open previously or was fully stopped. However, if I return to home or switch to another app, then return to Bitwarden, the focus on the Master Password is lost again and I have to manually tap on it to refocus it. I compared against the MAUI app, and the MAUI one always refocuses on the Master Password field, even if you switch away from Bitwarden to something else and then back to Bitwarden.

Hopefully, this can be addressed to ensure full parity with the old MAUI app.

@jabashque commented on GitHub (Aug 14, 2024): Hi, after qwexter's changes in 2024.8.0, Bitwarden now autofocuses on the Master Password field on startup if Bitwarden wasn't open previously or was fully stopped. However, if I return to home or switch to another app, then return to Bitwarden, the focus on the Master Password is lost again and I have to manually tap on it to refocus it. I compared against the MAUI app, and the MAUI one always refocuses on the Master Password field, even if you switch away from Bitwarden to something else and then back to Bitwarden. Hopefully, this can be addressed to ensure full parity with the old MAUI app.
GiteaMirror commented 2025-11-26 23:01:52 -06:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Aug 12, 2025):

⚠️ Stale Issue Notice

This issue has been automatically marked as stale due to inactivity. It will be closed in 2 weeks (August 26, 2025) 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! 🙏

@closebot-bw commented on GitHub (Aug 12, 2025): ⚠️ **Stale Issue Notice** This issue has been automatically marked as stale due to inactivity. It will be closed in **2 weeks** (August 26, 2025) 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 2025-11-26 23:01:52 -06:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Aug 23, 2025):

🔔 Final Notice - Issue Will Be Closed Soon

This issue was previously marked as stale and will be automatically closed in 3 days (August 26, 2025) 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! 📋

@closebot-bw commented on GitHub (Aug 23, 2025): 🔔 **Final Notice - Issue Will Be Closed Soon** This issue was previously marked as stale and will be automatically closed in **3 days** (August 26, 2025) 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 2025-11-26 23:01:52 -06:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Aug 26, 2025):

🔒 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! 🙏

@closebot-bw commented on GitHub (Aug 26, 2025): 🔒 **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#1924
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?