-
Notifications
You must be signed in to change notification settings - Fork 317
New issue
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
Enabling Multiple Uses of NFC requestTechnology Instead of One-time #704
Comments
const nfcTagLogin = async () => {
}; const nfcClean = () => { const nfcRefresh =() => { |
I think the problem comes from trying to start the scanning immediatly after the cancellation. I had a similar problem and solved it by adding a small delay, which in your case will look like this
There might be a better solution, but this it the one that i managed to come up with, hope it helps you. Note that I haven't tested that on android |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
Hello. I am an IT developer working for a small company in Korea.
What I want to achieve is a functionality where, regardless of whether NFC is tapped once or not, pressing a 'Refresh' button turns off NFC reading and then turns it back on when pressed again.
However, I encountered an error after implementing this.
Could you please let me know if there is anything unusual in my source code?
The text was updated successfully, but these errors were encountered: