jariz / jariz/react-native-fingerprint-android
isCancelled should be set to true as a initial value
- Dominant language
- JavaScript
- Stars
- 96
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
Thanks for your share firstly.
Before start authenticate every time, we should check the FingerPrint whether is started, if yes, cancel it. So if do cancel when FingerPrint is not started, we will get an error.
In general, the status of service should always be cleared or closed before service is started.
is it right?
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the authentication entry point and the isCancelled state referenced in the issue, then trace the cancellation path before fingerprint authentication starts. Reproduce the error when cancellation is attempted before the service starts; done means the initial service state is handled consistently without that error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, javascript, react-native
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100