-
Notifications
You must be signed in to change notification settings - Fork 3
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
RC card reading issue - “Tag connection lost” #1
Comments
Thanks for the report. We often encounter "Tag connection lost", but we don't know the best solution for this problem. As for the cause of "Tag connection lost", we know the following:
If you want to read only residence cards, try changing <key>com.apple.developer.nfc.readersession.iso7816.select-identifiers</key>
<array>
- <string>A00000023101</string>
- <string>A00000023102</string>
- <string>D392F000260100000001</string>
- <string>D3921000310001010401</string>
- <string>D3921000310001010402</string>
- <string>D3921000310001010408</string>
<string>D392F0004F0200000000000000000000</string>
<string>D392F0004F0300000000000000000000</string>
<string>D392F0004F0400000000000000000000</string> After making the above changes, the AIDs for the driver's license (A00000023101, A00000023102) and the AIDs for individual number card (D392F000260100000001, D3921000310001010401, D3921000310001010402, D3921000310001010408) will be removed, so please note that these two cards will no longer be readable. For reference, I would appreciate it if you could tell me the model and OS of your iPhone. |
Thank you for the detailed update. |
Thanks for the information. |
When connecting and reading data from RC card, most of the time an error is returning saying “Tag connection lost”.
It seems due to the connection timeout issue in Tag reader session.
https://developer.apple.com/forums/thread/118922
I have tried by running the
libjeid-ios-app
app and also my project integrated with the RC card reading codes.In both the application, timeout error is occurring frequently.
The text was updated successfully, but these errors were encountered: