-
Notifications
You must be signed in to change notification settings - Fork 121
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
Long discovery times for NTAG 424 #180
Comments
Sorry but I do not currently have NTAG424 available. 1.4s polling time does not look normal. Have you tried using another tag (i.e. confirming that it is not the problem w.r.t. one specific tag)? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey there, I'm struggling with improving the discovery times for an NTAG 424. (The tag shouldn't be the culprit most likely as the tag is significantly found faster on NFC Tools App)
This is the code that outputs the logs seen further down below, I also included a comparison with an Ntag 213
`Future<NfcPayloadStruct?> nfcKit(BuildContext context) async {
final startTime = DateTime.now();
print('nfcKit function started: $startTime');
try {
print('Checking NFC availability: ${DateTime.now()}');
var availability = await FlutterNfcKit.nfcAvailability;
print('NFC availability checked: ${DateTime.now()}, Result: $availability');
} catch (e) {
print('Error occurred: ${DateTime.now()}, Error: $e');
await FlutterNfcKit.finish(iosErrorMessage: "Error reading the tag.");
}
print('nfcKit function ended without result: ${DateTime.now()}');
return null;
}
`
The outputs for the print statements:
NTAG 424:
NTAG 213:
About the setup, I placed my iPhone on both tags to have the same conditions that the tags are available to be found from the very first moment.
Also I noticed that the problem is more prominent on iOS - don't have an Android unfortunately atm to provide timestamps as well
If you have any ideas how this could be well improved, let me know☺️
The text was updated successfully, but these errors were encountered: