github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-08 04:16:40 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[Version 2024.4.0] Unlock with PIN function doesn't work anymore #1860

New Issue
Closed
opened 2025-11-26 22:59:56 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-26 22:59:56 -06:00
Owner
Copy Link

Originally created by @lflaurflorin on GitHub (Apr 27, 2024).

Steps To Reproduce

  1. Go to 'SETTINGS' (Bitwarden Android App)
  2. Click on 'ACCOUNT SECURITY'
  3. Scroll down to 'Unlock with PIN code'
  4. Enable it and set a PIN

Opening the app and using the set up PIN won;t be recognized (PIN incorrect error)
This used to work in previous versions.

For the moment the Fingerprint option unlock still works, I am using it at the moment,
but I think it is less secure than PIN. Hopefully the source of the bug can be identified.

Thank you for this wonderful product and service!

Expected Result

The PIN that was set up was supposed to unlock the vault.

Actual Result

The message is displayed, even if the correct PIN that was set up, is supplied top the app. Internet connection is also active.

Screenshots or Videos

No response

Additional Context

I tried the latest beta version in Android as of today.
I also tried the latest stable version as of today.
The issue appears in both versions.

Operating System

Android

Operating System Version

Android 14

Device

Samsung Galaxy A53

Build Version

Version 2024.4.1 (10283)

Beta

  • Using a pre-release version of the application.
Originally created by @lflaurflorin on GitHub (Apr 27, 2024). ### Steps To Reproduce 1. Go to 'SETTINGS' (Bitwarden Android App) 2. Click on 'ACCOUNT SECURITY' 3. Scroll down to 'Unlock with PIN code' 4. Enable it and set a PIN Opening the app and using the set up PIN won;t be recognized (PIN incorrect error) This used to work in previous versions. For the moment the Fingerprint option unlock still works, I am using it at the moment, but I think it is less secure than PIN. Hopefully the source of the bug can be identified. Thank you for this wonderful product and service! ### Expected Result The PIN that was set up was supposed to unlock the vault. ### Actual Result The <PIN Incorrect> message is displayed, even if the correct PIN that was set up, is supplied top the app. Internet connection is also active. ### Screenshots or Videos _No response_ ### Additional Context I tried the latest beta version in Android as of today. I also tried the latest stable version as of today. The issue appears in both versions. ### Operating System Android ### Operating System Version Android 14 ### Device Samsung Galaxy A53 ### Build Version Version 2024.4.1 (10283) ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:59:56 -06:00
GiteaMirror commented 2025-11-26 22:59:57 -06:00
Author
Owner
Copy Link

@SergeantConfused commented on GitHub (Apr 28, 2024):

Hello @lflaurflorin,

Thank you for reporting this. I tested this on Android 12 with Bitwarden 2024.4.0 (Google Play Store) by configuring a PIN (1234) and deactivating (Unlock with biometrics) and then dismissing Bitwarden from the background; Afterwards, I was able to unlock Bitwarden using the PIN (1234) as expected. I recommend that you try this out in a fresh new installation on the latest stable version; Please uninstall Bitwarden off your device, turn the phone off and back on, and then install Bitwarden anew from the Google Play Store.

If this behaviour persists, please feel free to create a Support ticket so we'd have a look at this together, and please also include a link to this GitHub report in the body of your ticket.

Alternatively, you can seek assistance from other Bitwarden users in our Community Forums, if you wish.

We use GitHub to track bugs and other development related matters; This GitHub report will be closed at this point.

Thank you again,

@SergeantConfused commented on GitHub (Apr 28, 2024): Hello @lflaurflorin, Thank you for reporting this. I tested this on Android 12 with Bitwarden 2024.4.0 (Google Play Store) by configuring a PIN (1234) and deactivating (Unlock with biometrics) and then dismissing Bitwarden from the background; Afterwards, I was able to unlock Bitwarden using the PIN (1234) as expected. I recommend that you try this out in a fresh new installation on the latest stable version; Please uninstall Bitwarden off your device, turn the phone off and back on, and then install Bitwarden anew from the Google Play Store. If this behaviour persists, please feel free to create a [Support ticket](https://bitwarden.com/help/) so we'd have a look at this together, and please also include a link to this GitHub report in the body of your ticket. Alternatively, you can seek assistance from other Bitwarden users in our [Community Forums](https://community.bitwarden.com/c/support/), if you wish. We use GitHub to track bugs and other development related matters; This GitHub report will be closed at this point. Thank you again,
GiteaMirror commented 2025-11-26 22:59:57 -06:00
Author
Owner
Copy Link

@alexisshaw commented on GitHub (Apr 29, 2024):

Hi,

I would like to report the same issue on my samsung S24 ultra with the same version.

Reinstalling the app, with or without restarting the phone in-between does not work. My phone does not have biometrics enabled.

As a developer myself, I think this is an actual bug and not a support issue, and dismissing it as only a support issue is problematic.

To add additional context, it appears that even disabling the pin lock, and using the master password to unlock is also broken on my device. Logging out and logging in afresh works, but not unlocking with either a pin or a master password.

@alexisshaw commented on GitHub (Apr 29, 2024): Hi, I would like to report the same issue on my samsung S24 ultra with the same version. Reinstalling the app, with or without restarting the phone in-between does not work. My phone does not have biometrics enabled. As a developer myself, I think this is an actual bug and not a support issue, and dismissing it as only a support issue is problematic. To add additional context, it appears that even disabling the pin lock, and using the master password to unlock is also broken on my device. Logging out and logging in afresh works, but not unlocking with either a pin or a master password.
GiteaMirror commented 2025-11-26 22:59:57 -06:00
Author
Owner
Copy Link

@DunklerPhoenix commented on GitHub (May 1, 2024):

I have the same problem under android

@DunklerPhoenix commented on GitHub (May 1, 2024): I have the same problem under android
GiteaMirror commented 2025-11-26 22:59:58 -06:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (May 13, 2024):

@SergeantConfused Hi, I think something got mixed up here. I encountered the issue myself with the BETA (!). You seem to have tested it with the last release (2024.4.0) while @lflaurflorin wrote the problem occurred on 2024.4.1 = BETA, though didn't check the "pre-release/Beta" field...

The issue seems to be related to the beta...

I'm on a Fairphone 5 and still on Android 13. And this issue caused me deinstalling the beta more or less immediately.

PS: And the title of the thread/"issue" seems to be wrong then, because - as I wrote above - it is not about the 2024.4.0 (current Android release), but about the 2024.4.1 (BETA!).

@pamperer562580892423 commented on GitHub (May 13, 2024): @SergeantConfused Hi, I think something got mixed up here. I encountered the issue myself with the BETA (!). You seem to have tested it with the last release (2024.4.0) while @lflaurflorin wrote the problem occurred on 2024.4.1 = BETA, though didn't check the "pre-release/Beta" field... The issue seems to be related to the beta... I'm on a Fairphone 5 and still on Android 13. And this issue caused me deinstalling the beta more or less immediately. PS: And the title of the thread/"issue" seems to be wrong then, because - as I wrote above - it is not about the 2024.4.0 (current Android release), but about the 2024.4.1 (BETA!).
GiteaMirror commented 2025-11-26 22:59:58 -06:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (May 14, 2024):

@SergeantConfused ... but, there is also another open issue (https://github.com/bitwarden/mobile/issues/3214), where others (and me) describe the same issue, so this issue here maybe can remain as "closed" because it is a "duplicate"...

@pamperer562580892423 commented on GitHub (May 14, 2024): @SergeantConfused ... but, there is also another open issue (https://github.com/bitwarden/mobile/issues/3214), where others (and me) describe the same issue, so this issue here maybe can remain as "closed" because it is a "duplicate"...
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#1860
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?