[GH-ISSUE #559] [Bug][IOS] Bitwarden crashes after enabling fingerprint #48880

Closed
opened 2026-05-01 07:05:26 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @urvish0215 on GitHub (Jul 13, 2019).
Original GitHub issue: https://github.com/bitwarden/android/issues/559

After enabling the fingerprint option in the Bitwarden app, Bitwarden locks the vault and asks for fingerprint, and when you fingerprint-unlock it, it crashes immediately.
Then if you reopen the app again, it will ask you for your fingerprint, and when you fingerprint-unlock it, it crashes again. Repeat and same result.

But if you use cancel the fingerprint request and password-unlock it, it works properly.Then If you lock it again, fingerprint-unlock also starts working properly.

You can replicate this issue by disabling the fingerprint option in the bitwarden app and then re-enabling it.

Device Details:
Iphone 6s, IOS 12.3.1, bitwarden 2.1.0

Originally created by @urvish0215 on GitHub (Jul 13, 2019). Original GitHub issue: https://github.com/bitwarden/android/issues/559 After enabling the fingerprint option in the Bitwarden app, Bitwarden locks the vault and asks for fingerprint, and when you fingerprint-unlock it, it crashes immediately. Then if you reopen the app again, it will ask you for your fingerprint, and when you fingerprint-unlock it, it crashes again. Repeat and same result. But if you use cancel the fingerprint request and password-unlock it, it works properly.Then If you lock it again, fingerprint-unlock also starts working properly. You can replicate this issue by disabling the fingerprint option in the bitwarden app and then re-enabling it. Device Details: Iphone 6s, IOS 12.3.1, bitwarden 2.1.0
Author
Owner

@kspearrin commented on GitHub (Jul 13, 2019):

I have not been able to replicate the issue on iPhone 6S. Could you try reinstalling and see if that changes anything?

<!-- gh-comment-id:511161445 --> @kspearrin commented on GitHub (Jul 13, 2019): I have not been able to replicate the issue on iPhone 6S. Could you try reinstalling and see if that changes anything?
Author
Owner

@urvish0215 commented on GitHub (Jul 13, 2019):

I deleted and reinstalled the app. Bug still exists but goes away if you change the lock option to anything other than “immediately”.

It looks like this bug only happens if you set the lock option to “immediately” instead of a time.

<!-- gh-comment-id:511161803 --> @urvish0215 commented on GitHub (Jul 13, 2019): I deleted and reinstalled the app. Bug still exists but goes away if you change the lock option to anything other than “immediately”. It looks like this bug only happens if you set the lock option to “immediately” instead of a time.
Author
Owner

@kspearrin commented on GitHub (Jul 14, 2019):

OK, I can reproduce it with "immediately" lock options. Should be fixed next version. Thanks.

<!-- gh-comment-id:511163366 --> @kspearrin commented on GitHub (Jul 14, 2019): OK, I can reproduce it with "immediately" lock options. Should be fixed next version. Thanks.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#48880