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

No auto-keyboard on android app start (while beeing previously logged in) #1587

New Issue
Closed
opened 2025-11-26 22:53:03 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-26 22:53:03 -06:00
Owner
Copy Link

Originally created by @mhombach on GitHub (Feb 7, 2023).

Steps To Reproduce

  1. start android app (while beeing already "logged in" but having the vault beeing locked)
  2. wait for the app to load and show the "enter password to unlock" screen

Expected Result

As it was happening in some earlier versions, the user expects the kayboard to automatically popup/appear.
The user-flow in this case is in 99.9% to instantly start typing the password. Having to tap the password-field and wait for the delay to show the onscreen-keyboard is wasting previous time.

Actual Result

Nothing happens, no onscreen-keyboard is shown

Screenshots or Videos

No response

Additional Context

No response

Operating System

Android

Operating System Version

No response

Device

Xiaomi Redmi Note 10

Build Version

2023.1.0

Beta

  • Using a pre-release version of the application.
Originally created by @mhombach on GitHub (Feb 7, 2023). ### Steps To Reproduce 1. start android app (while beeing already "logged in" but having the vault beeing locked) 2. wait for the app to load and show the "enter password to unlock" screen ### Expected Result As it was happening in some earlier versions, the user expects the kayboard to automatically popup/appear. The user-flow in this case is in 99.9% to instantly start typing the password. Having to tap the password-field and wait for the delay to show the onscreen-keyboard is wasting previous time. ### Actual Result Nothing happens, no onscreen-keyboard is shown ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Operating System Android ### Operating System Version _No response_ ### Device Xiaomi Redmi Note 10 ### Build Version 2023.1.0 ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:53:03 -06:00
GiteaMirror commented 2025-11-26 22:53:04 -06:00
Author
Owner
Copy Link

@TroyBW commented on GitHub (Feb 8, 2023):

Hi there,

Thank you for your report!

I was able to reproduce this issue, and have flagged this to our engineering team.

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

Thanks once again!

@TroyBW commented on GitHub (Feb 8, 2023): Hi there, Thank you for your report! I was able to reproduce this issue, and have flagged this to our engineering team. If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these. Thanks once again!
GiteaMirror commented 2025-11-26 22:53:04 -06:00
Author
Owner
Copy Link

@unoukujou commented on GitHub (Aug 24, 2023):

Hi there,

Thank you for your report!

I was able to reproduce this issue, and have flagged this to our engineering team.

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

Thanks once again!

6 months later. Still a problem. Keyboard should be open and text field should receive focus and ready to type in. It's the expected behavior. And was working as expected in old versions.

@unoukujou commented on GitHub (Aug 24, 2023): > Hi there, > > Thank you for your report! > > I was able to reproduce this issue, and have flagged this to our engineering team. > > If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these. > > Thanks once again! 6 months later. Still a problem. Keyboard should be open and text field should receive focus and ready to type in. It's the expected behavior. And was working as expected in old versions.
GiteaMirror commented 2025-11-26 22:53:04 -06:00
Author
Owner
Copy Link

@vvolkgang commented on GitHub (Jun 20, 2024):

Issue migrated to https://github.com/bitwarden/mobile/issues/2349

@vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/2349
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#1587
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?