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

Keyboard submit button do not work on master password or PIN field #1952

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

Originally created by @user-naa on GitHub (Aug 6, 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. Lock vault with password or PIN
  2. Click unlock input field and enter password/PIN
  3. Press submit button on your keyboard

Expected Result

Nothing happens

Actual Result

Password should be verified and vault unlocked of password correct

Build Version

2024.7.3 (18938)

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 @user-naa on GitHub (Aug 6, 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. Lock vault with password or PIN 2. Click unlock input field and enter password/PIN 3. Press submit button on your keyboard ### Expected Result Nothing happens ### Actual Result Password should be verified and vault unlocked of password correct ### Build Version 2024.7.3 (18938) ### 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 bug label 2025-11-26 23:02:52 -06:00
GiteaMirror commented 2025-11-26 23:02:52 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Aug 6, 2024):

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

@bitwarden-bot commented on GitHub (Aug 6, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-10658
GiteaMirror commented 2025-11-26 23:02:52 -06:00
Author
Owner
Copy Link

@qwexter commented on GitHub (Aug 7, 2024):

Yes, it's work as is and I try to fix it in this screen with some minor improvements.
We got an answer from dev team, this behavior must be synced with UX\UI team (It's my guess, I don't know what's MAUI mean)

@qwexter commented on GitHub (Aug 7, 2024): Yes, it's work as is and I try to fix it in this screen with some minor improvements. We got an answer from dev team, this behavior must be synced with UX\UI team (It's my guess, I don't know what's MAUI mean)
GiteaMirror commented 2025-11-26 23:02:53 -06:00
Author
Owner
Copy Link

@qwexter commented on GitHub (Aug 7, 2024):

Or I leave here)

Description: The current app does not work properly with Keyboard Actions, which can make it difficult to use certain features, such as:

PIN code input screen: If you press the "Done" button on your keyboard, the keyboard will close, and you'll need to press the CTA (Call-to-Action) button again.
Master password setup: Similarly, when using Keyboard Actions on this screen, the app does not recognize the "Done" button press.
Proposal: I suggest adding support for Keyboard Actions in the following scenarios:

Single CTA button: When there's only one possible action on a screen (e.g., a single button to confirm), allow users to trigger it using a keyboard action.
Multiple input fields: If there are multiple input fields on a screen, use Keyboard Actions to focus on the next field after completing each one, and finally perform the CTA action.

Why is this important? By implementing these improvements, we can enhance the overall user experience of our app, making it more intuitive and efficient for users to interact with it.

As is Can be
keyboard_actions_as_is keyboard_actions_can_be
@qwexter commented on GitHub (Aug 7, 2024): Or I leave here) Description: The current app does not work properly with Keyboard Actions, which can make it difficult to use certain features, such as: PIN code input screen: If you press the "Done" button on your keyboard, the keyboard will close, and you'll need to press the CTA (Call-to-Action) button again. Master password setup: Similarly, when using Keyboard Actions on this screen, the app does not recognize the "Done" button press. Proposal: I suggest adding support for Keyboard Actions in the following scenarios: Single CTA button: When there's only one possible action on a screen (e.g., a single button to confirm), allow users to trigger it using a keyboard action. Multiple input fields: If there are multiple input fields on a screen, use Keyboard Actions to focus on the next field after completing each one, and finally perform the CTA action. Why is this important? By implementing these improvements, we can enhance the overall user experience of our app, making it more intuitive and efficient for users to interact with it. | As is| Can be | |--------|--------| |![keyboard_actions_as_is](https://github.com/user-attachments/assets/c2154718-e865-4217-b5a7-1323521fc0b1)|![keyboard_actions_can_be](https://github.com/user-attachments/assets/cf24b2d2-6d1a-4c4f-8ea6-4b36b7ce4496)|
GiteaMirror commented 2025-11-26 23:02:53 -06:00
Author
Owner
Copy Link

@qwexter commented on GitHub (Aug 7, 2024):

@SaintPatrck maybe this issue and my ideas help you with MAUI and other things.

@qwexter commented on GitHub (Aug 7, 2024): @SaintPatrck maybe this issue and my ideas help you with MAUI and other things.
GiteaMirror commented 2025-11-26 23:02:53 -06:00
Author
Owner
Copy Link

@micahblut commented on GitHub (Aug 27, 2024):

Fixed with #3691
Thank you @qwexter

@micahblut commented on GitHub (Aug 27, 2024): Fixed with #3691 Thank you @qwexter
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 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#1952
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?