You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use this plugin in a decoupled and concurrent way
The isAvailable response was sent into a loadBiometricSecret response, being secret a 'biometrics' literal. I suspect this happens from Fingerprint.java#executeIsAvailable.
I expect not to mix the responses across the different methods
Environment
Plugin version: 5.0.1
Android 13
Logs
// pseudocode
isAvailable();
isAvailable().then(() => loadBiometricSecret()).then(console.log) // sometimes logs the secret, sometimes logs 'biometric'. Maybe such 'biometric' literal comes from the previously `isAvailable` request, that resolved after this second call.
Proposal
To have different channels to resolve each type of response.
Mitigation
Having a lock for each kind of request, aiming to:
Debounce the requests of the same method
Queue the requests of different methods
It should ideally differentiate also the arguments, that's not in this proposal
Bug report
Description
isAvailable
response was sent into aloadBiometricSecret
response, beingsecret
a'biometrics'
literal. I suspect this happens fromFingerprint.java#executeIsAvailable
.Environment
Logs
Proposal
To have different channels to resolve each type of response.
Mitigation
Having a lock for each kind of request, aiming to:
This is what I have, if it helps:
The text was updated successfully, but these errors were encountered: