fix: correctly handle pin flows #297
Conversation
Signed-off-by: Jan <[email protected]>
| } catch (e) { | ||
| setIsProcessing(false) | ||
| if (e instanceof InvalidPinError) { | ||
| if (shouldUsePin) { |
There was a problem hiding this comment.
Doest this also handle the biometric prompt canceled / incorrect error?
There's two biometric errors. Not sure if they're handled somewhere higher/ lower. It would probably be good if we can create a proof sharing pipeline at some point, that will be used for ALL proof sharing, and you can toggle the options that are needed. As with the offline / openid /dc api / whatever it's hard to keep everything in sync
There was a problem hiding this comment.
How can I test the biometrics flow? None of the funke flows seem to trigger it? Or do I need to be on secure enclave to test that
There was a problem hiding this comment.
Okay i handled it the same way as the other flows, but unable to test because secure env is broken.
Signed-off-by: Timo Glastra <[email protected]>
No description provided.