-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fingerprint not working on some devices #37
Comments
Hi, same problem on: Cheers |
Galaxy S8+ here. Fingerprint unlock was throwing this same error. I was going to start digging in the code, but before I did, I started searching for this error and came across a blog post saying that this message can pop up if lock screens are disabled or if fingerprints are added after the master key is created. I'm not an android dev, but I am a dev, so this had me starting to play with things. I first deleted my fingerprints in my phone and readded them. I removed all iris scanning (I was previously using it, but stopped, so I deleted the biometric data). I then opened the app and still had the error. I logged into the database, went to database settings, turned off finger prints then turned it back on. To my surprise, it prompted me to use my fingerprint to verify. Once I did, it is now working! I had a Galaxy S7 previously while using this app and fingerprints were enabled. Could this be a migration from one phone to another issue? |
Per your request, copy/pasted from #98: At Fingerprint Rotionderdelen.init()[0x000d0] Note that the Nokia 8 integrated the fingerprint sensor in the (capacitive) home button. Placing a finger on the sensor results in returning to the home screen |
logcat from #90 |
From #135, closed as duplicate of this issue:
|
Just wanted to update that @thecodemonk's suggestion:
worked for me as well on my Pixel 2 (see #62). The automatic app migration from my old phone to my new phone must have saved some sort of device-specific ID? Anyways, just wanted to share my experience. |
thanks for the feedback. I purchased an HTC U11 device hoping I could reproduce the issue (as @Airwave1981 has reported to have the issue there) but was not able to do so. So maybe this really simply means you have to re-enable fingerprint? |
Perhaps. I don't know if there's a way to disable the fingerprint option on app migration to a new phone (new hardware ID or something)? That might force us into realizing that we need to re-enable it? |
I tried turning the fingerprint option off and on on my Nokia 8 and it
worked.
Op 2 dec. 2017 17:07 schreef "poblabs" <notifications@github.com>:
Perhaps. I don't know if there's a way to disable the fingerprint option on
app migration to a new phone? That might force us into realizing that we
need to re-enable it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AZD2H0KvOS1rZbLxd2NQTR94nuVuiyG_ks5s8XXNgaJpZM4PyJfm>
.
|
Same with my pixel 2. Disable fingerprint and re-enable helped. |
You're geniuses, guys! Thank you! It works for OnePlus 5 (app was restored via Google Sync from Sony Z5 Compact). |
Jipii, yes disable and enable fingerprint again also now worked for me HTCU11!!! Now everything is fine. Thanks a lot. Cheers |
Nice! I had the same issue and I cold fix it with the trick found in this thread :-) OnePlus 3T Oxygen OS 5.0 (Android 8.0.0) |
Fails to init cipher
The text was updated successfully, but these errors were encountered: