Search results for

nfc

1,175 results found

Post

Replies

Boosts

Views

Activity

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 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
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
1
0
125
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
2
0
305
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
1
0
138
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
Dec ’25
Reply to NFC Bottomsheet customization
The UI cannot be modified in the way you envision. Additionally, if your NFC transfers are taking long enough to require a progress bar, I should remind you of the NFC session timeout duration, which is currently at a maximum of 20 seconds, and that cannot be changed either.
Topic: Design SubTopic: General Tags:
Dec ’25
NFC Bottomsheet customization
Hi all, I wanted to check whether the NFC bottom-sheet UI shown by iOS during an NFC reading session can be customized. We have a Figma design (attached) for how the sheet should look, but we are not sure whether iOS allows modifying the default NFC UI. Is UI customization supported, or is the bottom sheet fully controlled by the system? Thanks in advance.
Topic: Design SubTopic: General Tags:
1
0
503
Dec ’25
Reply to RFID read
Two questions please: I understand silently reading NFC tags using NFC libraries is not possible. Is there perhaps a different library which allows reading other types of RFID tags? Is there a way for a company to request silently reading NFC tags on the condition that the relevant app only be deployed internally, never on the apple store? Thanks
Topic: App & System Services SubTopic: Drivers Tags:
Dec ’25
RFID read
Hi! Following this ticket: https://developer.apple.com/forums/thread/808764?page=1#868010022 Is there any way to use the hardware RFID reading capabilities of an iPhone to read ISO15693 RF tags silently, and without a UI pop-up? Perhaps using other native iOS libraries than the NFC library? If not, is there a way for a business to request this feature be allowed in internally used apps only?
3
0
318
Dec ’25