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
In order to detect a keycard reader connection on the client side we're starting the same flow in a loop (every 3 seconds) calling keycardStartFlow.
Since we need to detect a keycard reader removal if the current error (state) is keycard.action.insert-card, we're also using a loop on the client side, by canceling the current flow calling keycardCancelFlow, then wait for 3 seconds, then start the same flow again calling keycardStartFlow.
Use case:
Running the app and plugging in/out a keycard reader, based on above described scenario, appropriate states are displayed:
app asks to plugin the card reader -> user plugs it in
app asks to insert a keycard -> user plugs out a reader
app asks to plugin the card reader -> user plugs it in
app asks to insert a keycard -> user plugs out a reader
.
.
.
and so on in a loop till the card gets inserted
Issue:
In some point while user is plugging in/out a keycard reader the app crashes (doesn't happen often, like once in 15-20 tries) getting the following log from the keycard library:
The text was updated successfully, but these errors were encountered:
Short context:
keycardStartFlow
.keycard.action.insert-card
, we're also using a loop on the client side, by canceling the current flow callingkeycardCancelFlow
, then wait for 3 seconds, then start the same flow again callingkeycardStartFlow
.Use case:
Running the app and plugging in/out a keycard reader, based on above described scenario, appropriate states are displayed:
Issue:
In some point while user is plugging in/out a keycard reader the app crashes (doesn't happen often, like once in 15-20 tries) getting the following log from the keycard library:
The text was updated successfully, but these errors were encountered: