Post

Replies

Boosts

Views

Activity

Reply to Inability to Communicate via APDU on iOS Despite NFC Tag Detection
Good Morning Hi I have Just added NFC Permission in Info.plist and formats in Entitlement.plist will that wont be sufficient to launch NFC reader If No, can you share me a Sample .plist and Entitlements with corrections you have suggested. Meanwhile I will try from my end also to check on the suggestion you have provided. But sample would be really helpful to solve my issue. Thanks in Advance
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’25
Reply to ISO 14443-4 Reading issue
attempting to switch to NFCTagReaderSession to communicate at the ISO-DEP / APDU level fails silently. The tagReaderSession(_:didDetect:) delegate is never called, even though the same physical tag is clearly present and readable via the NDEF session. From my observation, it appears that on iOS, once a tag is handled as an NDEF Type 4 tag, Core NFC does not reliably expose it again through NFCTagReaderSession for raw ISO-DEP / APDU communication—especially for NFC-B tags. The session starts successfully but does not surface the tag for APDU exchange. This raises an important question: Is there any supported way on iOS to reliably issue custom APDU commands to ISO 14443-4 (NFC-B) tags like the TI RF430, or is APDU access effectively restricted/filtered by Core NFC when the tag is NDEF-formatted? If this is a platform limitation, it would be helpful to have clarity on whether iOS intentionally blocks APDU-level access for such tags.
Jan ’26
Reply to Inability to Communicate via APDU on iOS Despite NFC Tag Detection
attempting to switch to NFCTagReaderSession to communicate at the ISO-DEP / APDU level fails silently. The tagReaderSession(_:didDetect:) delegate is never called, even though the same physical tag is clearly present and readable via the NDEF session. From my observation, it appears that on iOS, once a tag is handled as an NDEF Type 4 tag, Core NFC does not reliably expose it again through NFCTagReaderSession for raw ISO-DEP / APDU communication—especially for NFC-B tags. The session starts successfully but does not surface the tag for APDU exchange. This raises an important question: Is there any supported way on iOS to reliably issue custom APDU commands to ISO 14443-4 (NFC-B) tags like the TI RF430, or is APDU access effectively restricted/filtered by Core NFC when the tag is NDEF-formatted? If this is a platform limitation, it would be helpful to have clarity on whether iOS intentionally blocks APDU-level access for such tags. we are stuck here but in Android As it is inbuilt ISO dep layer the communication is happening as expected but for us we are facing issue in IOS Tagreadersession as it fails Silently. attaching the Tag details in the next comment
Topic: App & System Services SubTopic: Core OS Tags:
Jan ’26
Reply to Inability to Communicate via APDU on iOS Despite NFC Tag Detection
No I am using TagReaderSession only but its failing silently Did detect is not getting called for the tag mentioned above in screenshot this is how i am intiating the NFC Session is this correct way or anything is Missed public class NfcServiceIos : INfcServiceIos { private SessionDelegate _currentDelegate; private bool _sessionActive = false; private NFCTagReaderSession _currentSession; public async Task SendAsync(byte[] bytes) { var isNfcAvailable = UIDevice.CurrentDevice.CheckSystemVersion(11, 0); if (isNfcAvailable && NFCTagReaderSession.ReadingAvailable) { if (_sessionActive) { await Application.Current.MainPage.DisplayAlert("Error", "NFC session is still active. Please wait.", "Ok"); return; } _sessionActive = true; _currentDelegate = new SessionDelegate(bytes, OnSessionInvalidated); // All CoreNFC session code must be on the main thread! await Microsoft.Maui.ApplicationModel.MainThread.InvokeOnMainThreadAsync(() => { // create NFCTagReaderSession instead of NFCNdefReaderSession _currentSession = new NFCTagReaderSession(NFCPollingOption.Iso14443,_currentDelegate, null); _currentSession.AlertMessage = "Please hold your device near the NFC tag"; _currentSession.BeginSession(); }); var status = await _currentDelegate.WasDataTransmitted.Task; _currentSession = null; _currentDelegate = null; if (status != NfcTransmissionStatus.Success) { await Application.Current.MainPage.DisplayAlert("Error", "Suitable error message", "Ok"); } } else { await Application.Current.MainPage.DisplayAlert("Error", "Read is not supported by this tag", "Ok"); } } private void OnSessionInvalidated() { Application.Current.MainPage.DisplayAlert("Error", "Read Sesssion Invalidated Silently ", "Ok"); _sessionActive = false; }
Topic: App & System Services SubTopic: Core OS Tags:
Jan ’26
Reply to Inability to Communicate via APDU on iOS Despite NFC Tag Detection
I have checked the Console could not really find something there and I have created the sample application just to make contact with my NFC Tag from Texas Instrumentation where the NFC Tagreader session is failing Silently, Thats where our development is blocked and we are unable to progress forward, Is there any way to solve this issue or can we have working session with apple for the same issue ?
Topic: App & System Services SubTopic: Core OS Tags:
Jan ’26
Reply to Unable to Invoke NFC In IOS App
Hi I was able to fix issue but I am facing an different I want to send APDU commands using NfcNDefReadersession as my hardware device is not detected by the NFCTagReader session Is there any approach we can follow to achieve this. Thanks in Advance
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jul ’25
Reply to Inability to Communicate via APDU on iOS Despite NFC Tag Detection
Good Morning Hi I have Just added NFC Permission in Info.plist and formats in Entitlement.plist will that wont be sufficient to launch NFC reader If No, can you share me a Sample .plist and Entitlements with corrections you have suggested. Meanwhile I will try from my end also to check on the suggestion you have provided. But sample would be really helpful to solve my issue. Thanks in Advance
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jul ’25
Reply to Inability to Communicate via APDU on iOS Despite NFC Tag Detection
How do i get the AID of the NFC Hardware Device? Even though in get that its says we need to get apple approval for adding such an identifier in the Info.plist and Entitlements. How to get those Approvals ?
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jul ’25
Reply to Inability to Communicate via APDU on iOS Despite NFC Tag Detection
My question is: If I add the AID entries in both Info.plist and Entitlements.plist within the project, is that sufficient to enable and launch the NFC session, or do I also need to explicitly configure this AID in the Apple Developer portal (under App ID capabilities) and regenerate the provisioning profile with this change?
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jul ’25
Reply to ISO 14443-4 Reading issue
attempting to switch to NFCTagReaderSession to communicate at the ISO-DEP / APDU level fails silently. The tagReaderSession(_:didDetect:) delegate is never called, even though the same physical tag is clearly present and readable via the NDEF session. From my observation, it appears that on iOS, once a tag is handled as an NDEF Type 4 tag, Core NFC does not reliably expose it again through NFCTagReaderSession for raw ISO-DEP / APDU communication—especially for NFC-B tags. The session starts successfully but does not surface the tag for APDU exchange. This raises an important question: Is there any supported way on iOS to reliably issue custom APDU commands to ISO 14443-4 (NFC-B) tags like the TI RF430, or is APDU access effectively restricted/filtered by Core NFC when the tag is NDEF-formatted? If this is a platform limitation, it would be helpful to have clarity on whether iOS intentionally blocks APDU-level access for such tags.
Replies
Boosts
Views
Activity
Jan ’26
Reply to Inability to Communicate via APDU on iOS Despite NFC Tag Detection
attempting to switch to NFCTagReaderSession to communicate at the ISO-DEP / APDU level fails silently. The tagReaderSession(_:didDetect:) delegate is never called, even though the same physical tag is clearly present and readable via the NDEF session. From my observation, it appears that on iOS, once a tag is handled as an NDEF Type 4 tag, Core NFC does not reliably expose it again through NFCTagReaderSession for raw ISO-DEP / APDU communication—especially for NFC-B tags. The session starts successfully but does not surface the tag for APDU exchange. This raises an important question: Is there any supported way on iOS to reliably issue custom APDU commands to ISO 14443-4 (NFC-B) tags like the TI RF430, or is APDU access effectively restricted/filtered by Core NFC when the tag is NDEF-formatted? If this is a platform limitation, it would be helpful to have clarity on whether iOS intentionally blocks APDU-level access for such tags. we are stuck here but in Android As it is inbuilt ISO dep layer the communication is happening as expected but for us we are facing issue in IOS Tagreadersession as it fails Silently. attaching the Tag details in the next comment
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jan ’26
Reply to Inability to Communicate via APDU on iOS Despite NFC Tag Detection
This is Tag I am trying to establish the connection with
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jan ’26
Reply to Inability to Communicate via APDU on iOS Despite NFC Tag Detection
No I am using TagReaderSession only but its failing silently Did detect is not getting called for the tag mentioned above in screenshot this is how i am intiating the NFC Session is this correct way or anything is Missed public class NfcServiceIos : INfcServiceIos { private SessionDelegate _currentDelegate; private bool _sessionActive = false; private NFCTagReaderSession _currentSession; public async Task SendAsync(byte[] bytes) { var isNfcAvailable = UIDevice.CurrentDevice.CheckSystemVersion(11, 0); if (isNfcAvailable && NFCTagReaderSession.ReadingAvailable) { if (_sessionActive) { await Application.Current.MainPage.DisplayAlert("Error", "NFC session is still active. Please wait.", "Ok"); return; } _sessionActive = true; _currentDelegate = new SessionDelegate(bytes, OnSessionInvalidated); // All CoreNFC session code must be on the main thread! await Microsoft.Maui.ApplicationModel.MainThread.InvokeOnMainThreadAsync(() => { // create NFCTagReaderSession instead of NFCNdefReaderSession _currentSession = new NFCTagReaderSession(NFCPollingOption.Iso14443,_currentDelegate, null); _currentSession.AlertMessage = "Please hold your device near the NFC tag"; _currentSession.BeginSession(); }); var status = await _currentDelegate.WasDataTransmitted.Task; _currentSession = null; _currentDelegate = null; if (status != NfcTransmissionStatus.Success) { await Application.Current.MainPage.DisplayAlert("Error", "Suitable error message", "Ok"); } } else { await Application.Current.MainPage.DisplayAlert("Error", "Read is not supported by this tag", "Ok"); } } private void OnSessionInvalidated() { Application.Current.MainPage.DisplayAlert("Error", "Read Sesssion Invalidated Silently ", "Ok"); _sessionActive = false; }
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jan ’26
Reply to Inability to Communicate via APDU on iOS Despite NFC Tag Detection
I have checked the Console could not really find something there and I have created the sample application just to make contact with my NFC Tag from Texas Instrumentation where the NFC Tagreader session is failing Silently, Thats where our development is blocked and we are unable to progress forward, Is there any way to solve this issue or can we have working session with apple for the same issue ?
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jan ’26