When I enable Fingerprint Unlock and put my finger on the scanner I get the following message: "Fingerprint Unlock could not be enabled because an error occured: javax.crypto.AEADBadTagException".
1Password Version: 6.2b3
Extension Version: Not Provided
OS Version: Android 6.0.1
Sync Type: Dropbox
@injectx That doesn't look very good :/ Hopefully this will be fixed soon. By the way what device do you have?
We recently made changes so this error message is more descriptive for us to understand what’s going on. Sorry for the scare! Could you tell us what device you are using?
Same issue this side. I'm using oneplus 2 on android 6.0.1. My fingerprint works for other apps though.
Thanks for reporting this issue, @hellrokr. I'd like to ask you to create a Diagnostics Report from your Android device:
Then attach the entire file to an email to us: [email protected]
Please do not post your Diagnostics Report in the forums, but please do include a link to this thread in your email, along with your forum handle so that we can "connect the dots" when we see your Diagnostics Report in our inbox.
A short note here once you've sent the Report in will help us to keep an eye out for it. :)
Once we see the report we should be able to better assist you. Thanks in advance!
Hi peri, i want to send a diagnostics report but the option in 1password only allows me to send a email to u guys. I though it was sending some sort of error code or log? Am i doing something wrong? Thanks.
Hey @injectx. This sounds like an issue with some non-Gmail clients, since attachments are handled differently throughout email applications. Could you use the Gmail client to send us the diagnostics report?
Alternatively, you can copy and paste the content of the diagnostics report from the preview page. To copy and paste the contents of the diagnostics report, here's what you will need to do:
I look forward to the report. Thanks!
Thank you for your reply Peri, I've just sent the diagnostic report!
Thanks! We'll take a look and get back to you. :)
That's said, i think that you can create an enhancement request to improve the Email diagnostics :)
I have exactly the same problem with my OnePlus 2 which i just updated to the latest OxygenOS 3.0 Beta 1
Our development team is looking into this issue. Thanks for letting us know that you are seeing it too @TomPollok.
@Spinacle We plan to make improvements in this area! :)
@saad thanks for the quick reply. ill also send a diagnostics file to [email protected]
Thanks @TomPollok. You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here so we can track down the report and link it to this issue.
@saad the number is: [#EFY-67561-736] thank you for caring.
Thanks @TomPollok! ref: EFY-67561-736
Hi Peri, how are thing going? Just wanted to let you know that in the latest OxygenOS 3 build the fps option still isn't working (same error message). It was working however on a different ROM (CyanogenMod 13) for the OnePlus 2.
Hi i also updated to OxygenOS 3 Beta and i have exact the same error.
Thanks for the update @injectx. This error is related to the cryptographic cipher we are using with Fingerprint Unlock. We are still looking into the issue. Hope to have an update soon!
Thanks for letting us know @dendirk!
Any news on this issue?
I reached out to the team. We don't have an update to the fix for this particular error yet.
You're very welcome! :)
New 1Password user here, exact same problem :(
Hello. I am using ONEPLUS 2. also having similar issue with the fingerprint scanner.
let me know if any updates on this
I'm guessing this is something OnePlus has to solve. My banking App also supports the fps but also doesn't work (unknown error). Guess we'll have to wait for the next OTA..
It works fine for me on my nexus 6p
@injectx: The Dashlane Android app works perfectly using fingerprint authentication, on the current Oxygen 2 build. I've been using it for weeks. It's definitely something to do with 1Password's implementation.
We have indeed noticed this issue occurring on OnePlus devices. Our developers are aware of the issue. We'll let you know when we have any updates!