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

FaceID not working iPhone X #589

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

Originally created by @ghost on GitHub (Apr 28, 2018).

Not sure why anything changed, but when I reinstalled Bitwarden today on my iPhone X, toggling the FaceID option forces me to enter my phone password instead of my face. When opening the app, I get "Enter iPhone passcode for 'Bitwarden'
Use Face ID to verify."

Anyone else?

Originally created by @ghost on GitHub (Apr 28, 2018). <!-- Please do not submit feature requests. The [Community Forums][1] has a section for submitting, voting for, and discussing product feature requests. [1]: https://community.bitwarden.com --> Not sure why anything changed, but when I reinstalled Bitwarden today on my iPhone X, toggling the FaceID option forces me to enter my phone password instead of my face. When opening the app, I get "Enter iPhone passcode for 'Bitwarden' Use Face ID to verify." Anyone else?
GiteaMirror commented 2025-11-26 22:22:45 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Apr 28, 2018):

We’ve had a few people report this lately. It worked fine before reinstalling?

@kspearrin commented on GitHub (Apr 28, 2018): We’ve had a few people report this lately. It worked fine before reinstalling?
GiteaMirror commented 2025-11-26 22:22:45 -06:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 28, 2018):

I last had it installed for a while and did a reset of my phone. I had it installed before and after the latest update with no issue. Not sure why a fresh install would cause this.

@ghost commented on GitHub (Apr 28, 2018): I last had it installed for a while and did a reset of my phone. I had it installed before and after the latest update with no issue. Not sure why a fresh install would cause this.
GiteaMirror commented 2025-11-26 22:22:45 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Apr 28, 2018):

I don't have a iPhone X to test with so I am unsure what could be the problem, but it's definitely not just you.

@kspearrin commented on GitHub (Apr 28, 2018): I don't have a iPhone X to test with so I am unsure what could be the problem, but it's definitely not just you.
GiteaMirror commented 2025-11-26 22:22:45 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Apr 28, 2018):

Are you sure you had the latest version before you reset your phone? Looks like there was a regression in our biometric API library: https://github.com/smstuebe/xamarin-fingerprint/issues/101

I think we upgraded to the bugged version in our latest release.

@kspearrin commented on GitHub (Apr 28, 2018): Are you sure you had the latest version before you reset your phone? Looks like there was a regression in our biometric API library: https://github.com/smstuebe/xamarin-fingerprint/issues/101 I think we upgraded to the bugged version in our latest release.
GiteaMirror commented 2025-11-26 22:22:45 -06:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 28, 2018):

Positive, it had been a bit since I have opened it before the reset so I can’t exactly pinpoint when I actually last opened it though. Not sure if it was before or after the update 5 days ago.

On Fri, Apr 27, 2018 at 11:16 PM, Kyle Spearrin notifications@github.com wrote:

Are you sure you had the latest version before you reset your phone? Looks like there was a regression in our biometric API library: smstuebe/xamarin-fingerprint#101

I think we upgraded to the bugged version in our latest release.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bitwarden/mobile","title":"bitwarden/mobile","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/bitwarden/mobile"}},"updates":{"snippets":[{"icon":"PERSON","message":"@kspearrin in #307: Are you sure you had the latest version before you reset your phone? Looks like there was a regression in our biometric API library: https://github.com/smstuebe/xamarin-fingerprint/issues/101 I think we upgraded to the bugged version in our latest release."}],"action":{"name":"View Issue","url":"https://github.com/bitwarden/mobile/issues/307#issuecomment-385138865"}}}

@ghost commented on GitHub (Apr 28, 2018): Positive, it had been a bit since I have opened it before the reset so I can’t exactly pinpoint when I actually last opened it though. Not sure if it was before or after the update 5 days ago. On Fri, Apr 27, 2018 at 11:16 PM, Kyle Spearrin <notifications@github.com> wrote: > Are you sure you had the latest version before you reset your phone? Looks like there was a regression in our biometric API library: [smstuebe/xamarin-fingerprint#101](https://github.com/smstuebe/xamarin-fingerprint/issues/101) > > I think we upgraded to the bugged version in our latest release. > > — > You are receiving this because you authored the thread. > Reply to this email directly, [view it on GitHub](https://github.com/bitwarden/mobile/issues/307#issuecomment-385138865), or [mute the thread](https://github.com/notifications/unsubscribe-auth/ALINEZt2drbuvIo8GsOp3nJiCNzLMFwEks5ts-0qgaJpZM4TrN9F). > > {"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bitwarden/mobile","title":"bitwarden/mobile","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/bitwarden/mobile"}},"updates":{"snippets":[{"icon":"PERSON","message":"@kspearrin in #307: Are you sure you had the latest version before you reset your phone? Looks like there was a regression in our biometric API library: https://github.com/smstuebe/xamarin-fingerprint/issues/101 I think we upgraded to the bugged version in our latest release."}],"action":{"name":"View Issue","url":"https://github.com/bitwarden/mobile/issues/307#issuecomment-385138865"}}}
GiteaMirror commented 2025-11-26 22:22:46 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Apr 28, 2018):

Or maybe the latest iOS version now requires that we request permission now in the Info.plist, which we don't do:

See: https://github.com/smstuebe/xamarin-fingerprint#ios

Looks like it was something added in iOS 11.3. Maybe when you reset you went to 11.3?

@kspearrin commented on GitHub (Apr 28, 2018): Or maybe the latest iOS version now requires that we request permission now in the Info.plist, which we don't do: See: https://github.com/smstuebe/xamarin-fingerprint#ios Looks like it was something added in iOS 11.3. Maybe when you reset you went to 11.3?
GiteaMirror commented 2025-11-26 22:22:46 -06:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 28, 2018):

I usually update the day iOS releases their updates, but again there’s a chance I had not opened the app before the Bitwarden update or the 11.3.1 update.

Sent from ProtonMail Mobile

On Fri, Apr 27, 2018 at 11:20 PM, Kyle Spearrin notifications@github.com wrote:

Or maybe the latest iOS version now requires that we request permission now in the Info.plist, whichw e don't do:

See: https://github.com/smstuebe/xamarin-fingerprint#ios

Looks like it was something added in iOS 11.3. Maybe when you reset you went to 11.3?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bitwarden/mobile","title":"bitwarden/mobile","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/bitwarden/mobile"}},"updates":{"snippets":[{"icon":"PERSON","message":"@kspearrin in #307: Or maybe the latest iOS version now requires that we request permission now in the Info.plist, whichw e don't do: See: https://github.com/smstuebe/xamarin-fingerprint#ios Looks like it was something added in iOS 11.3. Maybe when you reset you went to 11.3?"}],"action":{"name":"View Issue","url":"https://github.com/bitwarden/mobile/issues/307#issuecomment-385139022"}}}

@ghost commented on GitHub (Apr 28, 2018): I usually update the day iOS releases their updates, but again there’s a chance I had not opened the app before the Bitwarden update or the 11.3.1 update. Sent from ProtonMail Mobile On Fri, Apr 27, 2018 at 11:20 PM, Kyle Spearrin <notifications@github.com> wrote: > Or maybe the latest iOS version now requires that we request permission now in the Info.plist, whichw e don't do: > > See: https://github.com/smstuebe/xamarin-fingerprint#ios > > Looks like it was something added in iOS 11.3. Maybe when you reset you went to 11.3? > > — > You are receiving this because you authored the thread. > Reply to this email directly, [view it on GitHub](https://github.com/bitwarden/mobile/issues/307#issuecomment-385139022), or [mute the thread](https://github.com/notifications/unsubscribe-auth/ALINEaQz6te_d01GI0FPbOz0fmUVeJ-Bks5ts-35gaJpZM4TrN9F). > > {"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bitwarden/mobile","title":"bitwarden/mobile","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/bitwarden/mobile"}},"updates":{"snippets":[{"icon":"PERSON","message":"@kspearrin in #307: Or maybe the latest iOS version now requires that we request permission now in the Info.plist, whichw e don't do: See: https://github.com/smstuebe/xamarin-fingerprint#ios Looks like it was something added in iOS 11.3. Maybe when you reset you went to 11.3?"}],"action":{"name":"View Issue","url":"https://github.com/bitwarden/mobile/issues/307#issuecomment-385139022"}}}
GiteaMirror commented 2025-11-26 22:22:46 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Apr 28, 2018):

Fixed in next version. Thanks.

@kspearrin commented on GitHub (Apr 28, 2018): Fixed in next version. Thanks.
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#589
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?