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

When autofilling on Android, Bitwarden forgets that it's autofilling if you switch to another app or the home screen #1895

New Issue
Closed
opened 2025-11-26 23:00:58 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-26 23:00:58 -06:00
Owner
Copy Link

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

Steps To Reproduce

  1. Configure Bitwarden to require master password to unlock and to lock immediately if you leave the app.
  2. Go to any app with a login screen, page, or dialog box
  3. Try to autofill with Bitwarden via Android's autofill framework. Because Bitwarden is locked, this will open a Bitwarden activity that will ask for the user to input the master password.
  4. Either switch to another app, or return to the homescreen.
  5. Return back to the previous app where you were autofilling with Bitwarden. It should be displaying the unlock screen still.
  6. Enter your master password and press the "Unlock" button.

Expected Result

This should still result in Bitwarden continuing the autofill flow, where it tries to pull up exact and best matches for the given URI, along with an option to search for other entries that didn't get matched to use for autofill purposes.

Actual Result

Bitwarden seems to forget that it's trying to autofill; instead, it behaves as if you opened the Bitwarden app directly and takes you to the main screen, where you can access your vault, the password generator, options, and so on. You have to press the back button to exit out of the Bitwarden activity to get back to the original app where you were trying to invoke autofill, and then try autofill again, this time without leaving the app or the Bitwarden activity half-way through the autofill process.

Screenshots or Videos

No response

Additional Context

No response

Operating System

Android

Operating System Version

LineageOS 21 (Android 14)

Device

OnePlus 8

Build Version

2024.5.1

Beta

  • Using a pre-release version of the application.
Originally created by @jabashque on GitHub (Jun 5, 2024). ### Steps To Reproduce 1. Configure Bitwarden to require master password to unlock and to lock immediately if you leave the app. 2. Go to any app with a login screen, page, or dialog box 3. Try to autofill with Bitwarden via Android's autofill framework. Because Bitwarden is locked, this will open a Bitwarden activity that will ask for the user to input the master password. 4. Either switch to another app, or return to the homescreen. 5. Return back to the previous app where you were autofilling with Bitwarden. It should be displaying the unlock screen still. 6. Enter your master password and press the "Unlock" button. ### Expected Result This should still result in Bitwarden continuing the autofill flow, where it tries to pull up exact and best matches for the given URI, along with an option to search for other entries that didn't get matched to use for autofill purposes. ### Actual Result Bitwarden seems to forget that it's trying to autofill; instead, it behaves as if you opened the Bitwarden app directly and takes you to the main screen, where you can access your vault, the password generator, options, and so on. You have to press the back button to exit out of the Bitwarden activity to get back to the original app where you were trying to invoke autofill, and then try autofill again, this time _without_ leaving the app or the Bitwarden activity half-way through the autofill process. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Operating System Android ### Operating System Version LineageOS 21 (Android 14) ### Device OnePlus 8 ### Build Version 2024.5.1 ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 23:00:58 -06:00
GiteaMirror commented 2025-11-26 23:00:59 -06:00
Author
Owner
Copy Link

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

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

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