Fail to enable biometric unlock about buttercup-desktop

[macno]

Just tried to create a new vault (local file) and enabling biometric unlock: same failure.

I'll try to wipe out bc and reinstalling it from scratch

[perry-mitchell]

I'm not running the latest MacOS so I'm not able to test this I'm afraid. I wonder if there's something in that which would cause an incompatibility with our dependencies. I don't think we've updated anything in that area though.

Would you mind kindly trying to create a new vault, and enabling biometrics there? Just to see if it's possible at all for you?

[perry-mitchell]

@macno Any luck? Is this still occurring?

[alvin13]

Was running into the same issue. Didn't matter if it was loading an existing vault or creating a new one, same error.
However as a workaround, I removed and installed Jun 2 v2.20.3
Using this version I was able to enable the biometric unlock and then upgrade to latest and the unlock still works now.
So it seems to me that the issue occurs only on the registration to the MacOs of biometric unlock on a vault, not the biometric identification part itself.

Apple M2 Sonoma 14.2 (23C64)

[LambertPhil]

I confirme that it comes after an update. I reactivated version 2.21 and enabled biometrics on all the vaults and everything worked fine. Since then, all biometrically-enabled vaults have accepted biometric unlocking, even with the latest version.

Apple M2 Somona 14.1.2

Same issue here with latest version of Buttercup : 2.24.4 and Mac Sonoma 14.1
Unable to use Biometric unlock method on current file or even on fresh new one

[perry-mitchell]

I'm not currently running Sonoma yet, and cant' reproduce this on earlier MacOS versions. I'd appreciate if someone might debug this on Sonoma and contribute a fix, if possible.

[macno]

I've just tried to debug the issue, but after cloning the repo and starting the app via npm run start:main I was not able to reproduce the issue: after typing the password the OS prompt for enabling touchId appears correctly.
Any suggestion on how to proceed?

[perry-mitchell]

I'm now on Sonoma and haven't been able to reproduce this. Until there's a repeatable process or consistent failures there's not much to do here. I'll close for now. Thanks.

[LambertPhil]

still the same error with Somona 14.2.1 and buttercup Desktop @ v2.25.0 Core @ v7.4.0