Search results for

“nfc”

1,224 results found

Post

Replies

Boosts

Views

Activity

Temporarily disable macOS capture of USB RFID reader(s)
Hello. I am attempting to wrap the C library libnfc as a Swift library. This is not for use on macOS - it's mainly for use on Linux (Raspberry Pi). I have a USB reader and my code appears to work so far, however the code/test/debug cycle is suboptimal if I'm running the code on the Pi. As I use a Mac for day-to-day coding, I'd prefer to use Xcode and my Mac for development. MacOS appears to capture the NFC hardware for its own frameworks and attempting to open a connection to the USB device gives a Unable to claim USB interface (Permission denied) error. ioreg shows that the hardware is claimed by an Apple framework: UsbExclusiveOwner = pid 10946, com.apple.ifdbun Is there a way to temporarily over-ride that system and use the hardware myself? I've tried Googling but most of the replies are out of date and Claude's advice launchctl unload /System/Library/LaunchDaemons/com.apple.ifdreader.plist doesn't appear to work... I'm wary of disabling SIP - is there a simple way to have access to the hardware m
Topic: App & System Services SubTopic: Hardware Tags:
2
0
503
Jan ’26
Reply to Inability to Communicate via APDU on iOS Despite NFC Tag Detection
It's probably not failing that silently. You should be checking for any errors returned from CoreNFC functions and see what they say. You could also be checking the Console logs for any errors displayed by the NFC system. You could check if your project configurations are correct by using the sample app and see if that works. For your code, you would want to seek for advice from the support channels for the development tools you are using.
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 _
Topic: App & System Services SubTopic: Core OS 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 i
Topic: App & System Services SubTopic: Core OS Tags:
Jan ’26
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.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Jan ’26
Reply to Cant Create/Update App Clips
Hey @jasonknebel we were able to fix it using the new format. Someone replied at Feedback Assistant to try the new format again and it finally worked! We had to change these two arguments from 'EN' to '${EN}': // Before 'data.relationships.localizations.data.0.id' => 'EN', 'included.0.id' => 'EN', // Now 'data.relationships.localizations.data.0.id' => '${EN}', 'included.0.id' => '${EN}', If that helps, do you mind sharing a URL of one of your app clips or just manually check this thing scanning an NFC card with a URL that uses your app clip host but random path that's not associated with an app clip? https://developer.apple.com/forums/thread/803187
Topic: App Store Distribution & Marketing SubTopic: App Store Connect API Tags:
Jan ’26
Reply to CoreNFC ISO7816: provisioning profile doesn’t match entitlements for readersession.formats / iso7816.select-identifiers + NFCError 104 “Tag is not connected”
ISO7816 application identifiers for NFC Tag Reader Session (ISO7816 application identifiers for NFC Tag Reader Session) while behaving like entitlements, they are not entered in the Entitlements file. This key and the AIDs would be entered in the Info.plist instead, and as such, they do not need any special provisioning on the developer portal. You just need to know what the AIDs are. Issue B could be related to not having the AIDs properly configured. So, once you have them configured properly the problem might go away. If it does not, then we can look into that further.
Topic: App & System Services SubTopic: Core OS Tags:
Jan ’26
CoreNFC ISO7816: provisioning profile doesn’t match entitlements for readersession.formats / iso7816.select-identifiers + NFCError 104 “Tag is not connected”
Hi all, I’m building an iOS app that uses CoreNFC to communicate with a YubiKey 5C NFC over ISO14443 / ISO7816 and send APDUs (e.g. select an applet by AID). Environment • Device: iPhone 13 Pro Max • iOS: 18.6.2 • Xcode: 26.1.1 (17B100) • API: NFCTagReaderSession(pollingOption: .iso14443) using NFCTag.iso7816 What I’m trying to do 1. Start NFCTagReaderSession(.iso14443) 2. Detect tag → connect 3. Send ISO7816 APDUs (SELECT AID, etc.) Issue A — Entitlements / signing If I add ISO7816-related NFC entitlements, Xcode fails signing with an error like: • “Provisioning profile … doesn’t match entitlements file value for com.apple.developer.nfc.readersession.formats” When I inspect the generated .mobileprovision, I only see something like: • com.apple.developer.nfc.readersession.formats = [NDEF, TAG, PACE] …and I do not see an ISO7816 / select-identifiers entitlement (and the Developer portal UI doesn’t appear to let me enable it). Questions: 1. Is ISO7816 access under com.apple.developer.nfc.reade
Topic: App & System Services SubTopic: Core OS Tags:
1
0
290
Dec ’25
NFCTagReaderSession fails with "Missing required entitlement" on iOS 26.2 despite correct configuration
Environment: Device: iPhone 15 iOS Version: 26.2 Xcode Version: (add your version) Signing: Automatic with Apple Developer account Problem: When calling NFCTagReaderSession.begin(), the session immediately fails with error code 2: Missing required entitlement. This happens even though: NFCTagReaderSession.readingAvailable returns true NFCNDEFReaderSession.readingAvailable returns true The session object is created successfully Configuration verified: BonoResidente.entitlements: Info.plist (relevant keys): NFCReaderUsageDescription This app needs NFC permission to read transport cards com.apple.developer.nfc.readersession.iso7816.select-identifiers D2760000850101 Apple Developer Portal: App ID com.acalvoelorri.BonoResidente has NFC Tag Reading capability enabled Provisioning profiles were regenerated after enabling the capability Xcode: Near Field Communication Tag Reading capability added via Signing & Capabilities CODE_SIGN_ENTITLEMENTS correctly points to the entitlements file Automati
Topic: App & System Services SubTopic: General Tags:
2
0
627
Dec ’25
Why my App Clip Card can not be opened?
Hello, I have an AppClip technical issue I'd like to ask about: Our Xiaohongshu App (Version 9.14 & Build 9140845 & appid 741292507) was submitted to the App Store for review on December 18th and approved on December 19th, starting a phased rollout. This version was the first to support AppClip functionality, and as of today the app has been fully rolled out, but I still cannot activate the Xiaohongshu App Clip Card using the NFC tag (built-in URL: https://xhslink.com/n/22UG9jlaOfv?sourceid=911). I checked all the configurations of our project's AppClip target (Associated Domains:appclips:xhslink.com), the default experience in the ASC backend (URL: https://appclip.apple.com/id?p=com.xingin.discover.Clip), and the advanced experience (URL: https://xhslink.com/n/Arxpo4IVY9X), and all showed no abnormalities. Furthermore, the default experience URL, after being written with an NFC tag, can be successfully launched by tapping the NFC tag to open the Xiaohongshu App Clip Card, a
Topic: App & System Services SubTopic: General Tags:
1
0
263
Dec ’25
Reply to P2P NFC BTC
Dear Apple, We have obtained the entitlement for NFC transactions for apps in the European Economic Area. With it it's possible to have a P2P NFC communication? if yes where I can found an example to have the writer part. In the documentation we have see the Device-to-Device transactions: If you have the legal right and the necessary regulatory permissions to provide device-to-device NFC solutions in the EEA, you can request access to iOS APIs to develop, test, or distribute an HCE Application for transmitting data over NFC to another mobile device. but in any place we discover documentation that explain how to do that. thanks
Topic: App & System Services SubTopic: Tap to Pay on iPhone Tags:
Dec ’25
Temporarily disable macOS capture of USB RFID reader(s)
Hello. I am attempting to wrap the C library libnfc as a Swift library. This is not for use on macOS - it's mainly for use on Linux (Raspberry Pi). I have a USB reader and my code appears to work so far, however the code/test/debug cycle is suboptimal if I'm running the code on the Pi. As I use a Mac for day-to-day coding, I'd prefer to use Xcode and my Mac for development. MacOS appears to capture the NFC hardware for its own frameworks and attempting to open a connection to the USB device gives a Unable to claim USB interface (Permission denied) error. ioreg shows that the hardware is claimed by an Apple framework: UsbExclusiveOwner = pid 10946, com.apple.ifdbun Is there a way to temporarily over-ride that system and use the hardware myself? I've tried Googling but most of the replies are out of date and Claude's advice launchctl unload /System/Library/LaunchDaemons/com.apple.ifdreader.plist doesn't appear to work... I'm wary of disabling SIP - is there a simple way to have access to the hardware m
Topic: App & System Services SubTopic: Hardware Tags:
Replies
2
Boosts
0
Views
503
Activity
Jan ’26
Reply to Inability to Communicate via APDU on iOS Despite NFC Tag Detection
It's probably not failing that silently. You should be checking for any errors returned from CoreNFC functions and see what they say. You could also be checking the Console logs for any errors displayed by the NFC system. You could check if your project configurations are correct by using the sample app and see if that works. For your code, you would want to seek for advice from the support channels for the development tools you are using.
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 _
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
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 i
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jan ’26
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.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Jan ’26
Reply to Cant Create/Update App Clips
Hey @jasonknebel we were able to fix it using the new format. Someone replied at Feedback Assistant to try the new format again and it finally worked! We had to change these two arguments from 'EN' to '${EN}': // Before 'data.relationships.localizations.data.0.id' => 'EN', 'included.0.id' => 'EN', // Now 'data.relationships.localizations.data.0.id' => '${EN}', 'included.0.id' => '${EN}', If that helps, do you mind sharing a URL of one of your app clips or just manually check this thing scanning an NFC card with a URL that uses your app clip host but random path that's not associated with an app clip? https://developer.apple.com/forums/thread/803187
Topic: App Store Distribution & Marketing SubTopic: App Store Connect API Tags:
Replies
Boosts
Views
Activity
Jan ’26
Reply to CoreNFC ISO7816: provisioning profile doesn’t match entitlements for readersession.formats / iso7816.select-identifiers + NFCError 104 “Tag is not connected”
ISO7816 application identifiers for NFC Tag Reader Session (ISO7816 application identifiers for NFC Tag Reader Session) while behaving like entitlements, they are not entered in the Entitlements file. This key and the AIDs would be entered in the Info.plist instead, and as such, they do not need any special provisioning on the developer portal. You just need to know what the AIDs are. Issue B could be related to not having the AIDs properly configured. So, once you have them configured properly the problem might go away. If it does not, then we can look into that further.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jan ’26
CoreNFC ISO7816: provisioning profile doesn’t match entitlements for readersession.formats / iso7816.select-identifiers + NFCError 104 “Tag is not connected”
Hi all, I’m building an iOS app that uses CoreNFC to communicate with a YubiKey 5C NFC over ISO14443 / ISO7816 and send APDUs (e.g. select an applet by AID). Environment • Device: iPhone 13 Pro Max • iOS: 18.6.2 • Xcode: 26.1.1 (17B100) • API: NFCTagReaderSession(pollingOption: .iso14443) using NFCTag.iso7816 What I’m trying to do 1. Start NFCTagReaderSession(.iso14443) 2. Detect tag → connect 3. Send ISO7816 APDUs (SELECT AID, etc.) Issue A — Entitlements / signing If I add ISO7816-related NFC entitlements, Xcode fails signing with an error like: • “Provisioning profile … doesn’t match entitlements file value for com.apple.developer.nfc.readersession.formats” When I inspect the generated .mobileprovision, I only see something like: • com.apple.developer.nfc.readersession.formats = [NDEF, TAG, PACE] …and I do not see an ISO7816 / select-identifiers entitlement (and the Developer portal UI doesn’t appear to let me enable it). Questions: 1. Is ISO7816 access under com.apple.developer.nfc.reade
Topic: App & System Services SubTopic: Core OS Tags:
Replies
1
Boosts
0
Views
290
Activity
Dec ’25
NFCTagReaderSession fails with "Missing required entitlement" on iOS 26.2 despite correct configuration
Environment: Device: iPhone 15 iOS Version: 26.2 Xcode Version: (add your version) Signing: Automatic with Apple Developer account Problem: When calling NFCTagReaderSession.begin(), the session immediately fails with error code 2: Missing required entitlement. This happens even though: NFCTagReaderSession.readingAvailable returns true NFCNDEFReaderSession.readingAvailable returns true The session object is created successfully Configuration verified: BonoResidente.entitlements: Info.plist (relevant keys): NFCReaderUsageDescription This app needs NFC permission to read transport cards com.apple.developer.nfc.readersession.iso7816.select-identifiers D2760000850101 Apple Developer Portal: App ID com.acalvoelorri.BonoResidente has NFC Tag Reading capability enabled Provisioning profiles were regenerated after enabling the capability Xcode: Near Field Communication Tag Reading capability added via Signing & Capabilities CODE_SIGN_ENTITLEMENTS correctly points to the entitlements file Automati
Topic: App & System Services SubTopic: General Tags:
Replies
2
Boosts
0
Views
627
Activity
Dec ’25
After configuring the APP Clip, it cannot be displayed
I have configured all the necessary settings for the APP Clip, but it still cannot be activated through NFC or scanning the code. What is the problem?
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Replies
0
Boosts
0
Views
208
Activity
Dec ’25
No response for over 3 weeks from apple entitlement team
I have an open NFC Value-Added Services entitlement case (17370116) with Apple Wallet Entitlements. My request was acknowledged, information provided, but the case appears to have been split into duplicates and stalled. Is there a way to have the case consolidated and routed back to the Wallet Entitlements team?
Topic: Developer Tools & Services SubTopic: Apple Developer Program Tags:
Replies
2
Boosts
0
Views
247
Activity
Dec ’25
App Clip cannot be displayed after creation
I have configured all the necessary settings for the APP Clip, but it still cannot be activated through NFC or scanning the code. What is the problem?
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Replies
0
Boosts
0
Views
129
Activity
Dec ’25
APP Stroe has created an advanced lightweight app experience, where NFC and QR code scanning are not activated
APP Stroe has created an advanced lightweight app experience, but NFC and QR code scanning are not activated. What is the problem?
Topic: App Store Distribution & Marketing SubTopic: App Store Connect
Replies
0
Boosts
0
Views
125
Activity
Dec ’25
Why my App Clip Card can not be opened?
Hello, I have an AppClip technical issue I'd like to ask about: Our Xiaohongshu App (Version 9.14 & Build 9140845 & appid 741292507) was submitted to the App Store for review on December 18th and approved on December 19th, starting a phased rollout. This version was the first to support AppClip functionality, and as of today the app has been fully rolled out, but I still cannot activate the Xiaohongshu App Clip Card using the NFC tag (built-in URL: https://xhslink.com/n/22UG9jlaOfv?sourceid=911). I checked all the configurations of our project's AppClip target (Associated Domains:appclips:xhslink.com), the default experience in the ASC backend (URL: https://appclip.apple.com/id?p=com.xingin.discover.Clip), and the advanced experience (URL: https://xhslink.com/n/Arxpo4IVY9X), and all showed no abnormalities. Furthermore, the default experience URL, after being written with an NFC tag, can be successfully launched by tapping the NFC tag to open the Xiaohongshu App Clip Card, a
Topic: App & System Services SubTopic: General Tags:
Replies
1
Boosts
0
Views
263
Activity
Dec ’25
Reply to P2P NFC BTC
Dear Apple, We have obtained the entitlement for NFC transactions for apps in the European Economic Area. With it it's possible to have a P2P NFC communication? if yes where I can found an example to have the writer part. In the documentation we have see the Device-to-Device transactions: If you have the legal right and the necessary regulatory permissions to provide device-to-device NFC solutions in the EEA, you can request access to iOS APIs to develop, test, or distribute an HCE Application for transmitting data over NFC to another mobile device. but in any place we discover documentation that explain how to do that. thanks
Topic: App & System Services SubTopic: Tap to Pay on iPhone Tags:
Replies
Boosts
Views
Activity
Dec ’25