github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-11 02:15:43 -05:00
Code Issues 1.1k Packages Projects Releases 124 Wiki Activity

"Lock" screen: blank page when BW is reduced+reopened #1013

New Issue
Closed
opened 2025-11-26 22:36:48 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-26 22:36:48 -06:00
Owner
Copy Link

Originally created by @contribucious on GitHub (May 16, 2020).

Originally assigned to: @mpbw2 on GitHub.

Describe the Bug

When Bitwarden is minimized and then reopened (or more simply: when the "Recent apps" screen is displayed and Bitwarden reselected from this location), there is a problem with the unlock request.

ℹ️ Problem not present in the stable version.

Steps To Reproduce (prerequisite)

↪️ Set Settings > Security > Lock Options to Immediately (not required but speeds up the test).

Case one — Only "Master Password" mode

[SHOW/HIDE]

a.

Set Settings > Security >

  • Unlock with Fingerprint to Disabled and
  • Unlock with PIN Code to Disabled.

b.

Now tap the "Recents" button on your smartphone, wait 1-2 seconds and select the Bitwarden window. (Minimizing and reopening the app will do the same thing too.)

Screenshot_20200516-212614
➡️ The master password request page remains blank.

Case two — "Master Password" + Fingerprint enabled

[SHOW/HIDE]

a.

Set Settings > Security >

  • Unlock with Fingerprint to Enabled and
  • Unlock with PIN Code to Disabled.

b.

Now tap the "Recents" button on your smartphone, wait 1-2 seconds and select the Bitwarden window. (Minimizing and reopening the app will do the same thing too.)

Screenshot_20200516-212857
➡️ With this unlocking mode, a fingerprint request is correctly requested. But ...

Screenshot_20200516-212906
➡️ ... if you repeat this same operation, blank page and no request for fingerprint anymore.

Case three — "Master Password" + PIN Code enabled

[SHOW/HIDE]

a.

Set Settings > Security >

  • Unlock with Fingerprint to Disabled and
  • Unlock with PIN Code to Enabled.

b.

Now tap the "Recents" button on your smartphone, wait 1-2 seconds and select the Bitwarden window. (Minimizing and reopening the app will do the same thing too.)

Screenshot_20200516-212740
➡️ With this unlocking mode, blank page and no PIN code request.

Expected Result

Unlocking possible in these cases, without having to relaunch the app each time (to have a request again).

Actual Result

No unlocking possible in these cases. The only workaround: relaunch the app each time when the situation arises (to have a request again).

Environment

  • Battery optimization: OFF

  • Device/OS:

    • Samsung Galaxy J5 2017 (Android 9)
    • Samsung Galaxy Tab S 10.5" (Android 6.0.1)
       

  • Build Version (go to "Settings" → "About" in the app):

    • both devices listed above have been tested with:

      • stable 2.3.1 (2257) [no problem]
      • beta 2.3.1 (2413) [problem]
      • a very recent tree from this repository1 [problem]
         

1 Screenshots taken with this version (allowing me to do so by modifying the source code).

Originally created by @contribucious on GitHub (May 16, 2020). Originally assigned to: @mpbw2 on GitHub. ## Describe the Bug When Bitwarden is minimized and then reopened (or more simply: when the "Recent apps" screen is displayed and Bitwarden reselected from this location), there is a problem with the unlock request. :information_source: Problem not present in the stable version. ## Steps To Reproduce _(prerequisite)_ :arrow_right_hook: Set Settings > Security > `Lock Options` to `Immediately` (not required but speeds up the test). ## Case one — Only "Master Password" mode <details> <summary>[SHOW/HIDE]</summary> #### a. Set Settings > Security > - `Unlock with Fingerprint` to `Disabled` and - `Unlock with PIN Code` to `Disabled`. #### b. Now tap the "Recents" button on your smartphone, wait 1-2 seconds and select the Bitwarden window. (Minimizing and reopening the app will do the same thing too.) ![Screenshot_20200516-212614](https://user-images.githubusercontent.com/4764956/82129072-6f987980-97c0-11ea-8659-e50fc470005a.jpg) :arrow_right: The master password request page remains blank. </details> ## Case two — "Master Password" + Fingerprint enabled <details> <summary>[SHOW/HIDE]</summary> #### a. Set Settings > Security > - `Unlock with Fingerprint` to **`Enabled`** and - `Unlock with PIN Code` to `Disabled`. #### b. Now tap the "Recents" button on your smartphone, wait 1-2 seconds and select the Bitwarden window. (Minimizing and reopening the app will do the same thing too.) ![Screenshot_20200516-212857](https://user-images.githubusercontent.com/4764956/82129148-fbaaa100-97c0-11ea-9f99-89514f6bbd78.jpg) :arrow_right: With this unlocking mode, a fingerprint request is correctly requested. But ... ![Screenshot_20200516-212906](https://user-images.githubusercontent.com/4764956/82129215-6a87fa00-97c1-11ea-9550-51611fb791b3.jpg) :arrow_right: ... if you repeat this same operation, blank page and no request for fingerprint anymore. </details> ## Case three — "Master Password" + PIN Code enabled <details> <summary>[SHOW/HIDE]</summary> #### a. Set Settings > Security > - `Unlock with Fingerprint` to `Disabled` and - `Unlock with PIN Code` to **`Enabled`**. #### b. Now tap the "Recents" button on your smartphone, wait 1-2 seconds and select the Bitwarden window. (Minimizing and reopening the app will do the same thing too.) ![Screenshot_20200516-212740](https://user-images.githubusercontent.com/4764956/82129278-c488bf80-97c1-11ea-87e7-3472da925bec.jpg) :arrow_right: With this unlocking mode, blank page and no PIN code request. </details> ## Expected Result Unlocking possible in these cases, without having to relaunch the app each time (to have a request again). ## Actual Result No unlocking possible in these cases. The only workaround: relaunch the app each time when the situation arises (to have a request again). ## Environment - Battery optimization: **OFF** - Device/OS: - Samsung Galaxy J5 2017 (**Android 9**) - Samsung Galaxy Tab S 10.5" (**Android 6.0.1**) &nbsp; - Build Version (go to "Settings" → "About" in the app): - both devices listed above have been tested with: - **stable** 2.3.1 (2257) **[_no_ problem]** - **beta** 2.3.1 (2413) **[problem]** - **a very recent tree** from this repository<sup>1</sup> **[problem]** &nbsp; <sup>1</sup> Screenshots taken with this version (allowing me to do so by modifying the source code).
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
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#1013
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?