We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The use case is simple, there should be a way to test biometric interaction.
An android command to trigger the fingerprint reader in the emulator You can see the button available in the settings
Command might be structured like this
- simulateFinger: <finger name>
Or to simulate a bad read
- simulateFinger: name: <finger name> failed: true
On android the adb command is adb -e emu finger touch [finger id]
adb -e emu finger touch [finger id]
An iOS command to trigger the faceID reader in the simulator You can see the trigger options in the simulator toolbar
A simple default success command might be like
- simulateFaceID
And a failed might be
- simulateFaceID: failed: true
The xcrun command on how to trigger faceIDs is here https://stackoverflow.com/a/56271446/1621031
No response
The text was updated successfully, but these errors were encountered:
MAE-91 add a "simulateFinger" and "simulateFace" command
Sorry, something went wrong.
No branches or pull requests
Use case
The use case is simple, there should be a way to test biometric interaction.
Proposal
An android command to trigger the fingerprint reader in the emulator

You can see the button available in the settings
Command might be structured like this
Or to simulate a bad read
On android the adb command is
adb -e emu finger touch [finger id]
An iOS command to trigger the faceID reader in the simulator

You can see the trigger options in the simulator toolbar
A simple default success command might be like
- simulateFaceID
And a failed might be
The xcrun command on how to trigger faceIDs is here https://stackoverflow.com/a/56271446/1621031
Anything else?
No response
The text was updated successfully, but these errors were encountered: