Search results for

“nfc”

1,224 results found

Post

Replies

Boosts

Views

Activity

Reply to whitelisting of the NFC Tag Reading and Writing (NDEF) entitlement
There is no whitelisting or other kinds of permissions or entitlements required to simply read and write to a writeable tag. You can configure your entitlements and Info.plist entries yourself for these functions. The sample code here: https://developer.apple.com/documentation/corenfc/creating-nfc-tags-from-your-iphone demonstrates how to implement writing to a writeable tag. As long as what you are reading and writing is not a restricted AID, like payment, identity, etc. there are no permissions required.
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’25
Reply to Inability to Communicate via APDU on iOS Despite NFC Tag Detection
You can check out https://developer.apple.com/documentation/corenfc/building-an-nfc-tag-reader-app for an example of how the entitlements and Info.plist entries are constructed. I can't help you with getting the AID of the NFC device. You may need to contact the manufacturer, if the AIDs are not standard, or documented. Approval depends on what you are trying to do. In order to just read from the tag, or write to the tag, you don't need any approval. If you are trying to emulate a tag (the NFC hardware you are using is a reader), or if the AIDs you are using are of restricted nature (like payment intent, identification, etc.) then you need approval and depending on the region you are operating in, that may or may not be possible, and will require an extensive application process.
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’25
whitelisting of the NFC Tag Reading and Writing (NDEF) entitlement
We have been struggling to get support and answeres regarding this roadblock : Request in whitelisting of the NFC Tag Reading and Writing (NDEF) entitlement for our iOS application Our application utilizes Core NFC to enable reading and writing of NFC tags, simplifying user interactions with NFC-enabled devices and services. The NDEF entitlement is essential for our app to deliver its core functionality effectively. Build Environment: Our app is developed and built using Xcode 16.4 on Codemagic’s cloud-based CI/CD platform, which utilizes a compatible macOS version (e.g., macOS Sonoma 14.4 or later). The app targets iOS 18 and uses Core NFC APIs for NDEF tag reading and writing. so far we cant get it to read or write as ios is restricking us
Topic: App & System Services SubTopic: Core OS Tags:
1
0
300
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:
Jul ’25
NFC Error
During EEPROM reading or writing on some appliance devices, the app encounters an error after 6 steps. This issue occurs only on iPhone 14 Pro Max, 15 Pro Max, and 16 Pro models, while all other iPhone models function correctly. Any one with this problem?
Topic: App & System Services SubTopic: Core OS Tags:
1
0
211
Jul ’25
Inability to Communicate via APDU on iOS Despite NFC Tag Detection
Background: We are developing a cross-platform mobile application that communicates with a custom NFC-enabled hardware device. The hardware expects ISO7816-style APDU commands for data exchange and functions correctly with Android using the IsoDep protocol. Observed Issue on iOS: On iOS, the tag is only detectable via NFCNdefReaderSession, which provides access to INFCNdefTag. Attempting to use NFCTagReaderSession with NFCPollingOption.Iso14443 (which is required for APDU communication) results in no tag detection. As a result, the tag is inaccessible for APDU-based communication on iOS. Since NFCNdefReaderSession does not support APDU, we are unable to establish the required command channel. Constraints: The hardware firmware cannot be changed to support NDEF-based command interpretation. The device expects raw ISO-DEP APDU commands (i.e., Class-Instruction-Param1-Param2-Data-Le). Impact: The lack of ISO7816 tag detection on iOS prevents the app from sending APDU commands, resulting in a platform-sp
Topic: App & System Services SubTopic: Core OS Tags:
12
0
525
Jul ’25
Is "NFC & SE Platform" required for raw ISO7816 APDU send via NFC?
I stumbled across the Apple NFC & SE Platform while searching for the cause to a persistent missing entitlement error. I am curious if not having this entitlement could be the root cause to my issues? Specifically, I am trying to perform an HMAC-SHA1 challenge-response via NFC on a YubiKey. Part of this entails low level APDU Send commands via NFC. The missing entitlement occurs right after the APDU Send. Per my separate post, I believe I have exhausted all other possible causes to no avail. For reference and details, this is the other post: [https://developer.apple.com/forums/thread/791995)
Topic: App & System Services SubTopic: Core OS Tags:
2
0
339
Jul ’25
Reply to Root issue is missing entitlement in NFC App
My initial post was not very clear, adding some supporting information below: Initial NFC session establishes successfully Failure occurs immediately on first APDU transmission Configuration & Verification: Xcode Capabilities: Near Field Communication Tag Reading is enabled in the target's Signing & Capabilities tab. entitlements File: com.apple.developer.nfc.readersession.formats is correctly set to an array containing only TAG. (Confirmed ISO7816 should NOT be directly in this array based on Apple documentation). com.apple.developer.nfc.readersession.formats TAG Info.plist Configuration: Privacy - NFC Scan Usage Description (NFCReaderUsageDescription) is present. com.apple.developer.nfc.readersession.iso7816.select-identifiers is correctly configured with an array of relevant YubiKey AIDs, including the OATH AID (A000000527210101) and others. codesign Output : After building the app, running codesign -d --entitlements :- /path/to/YourAppName.app explicitly confirms that the com.app
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’25
Root issue is missing entitlement in NFC App
The root issues is a missing entitlement error. I've jumped through countless hoops of checking/rechecking .entitlement file/plist file, creating new credentials, creating new projects, creating new provisioning profiles with no luck, manual signing, automatic signing. Any suggestions appreciated. Looking at the Provisioning Profile Info shows NFC Tag capabilities is included and NFC Entitlements are included. I'm at a loss... I am including the following: Pertinent output from console Current Info.Plist Current .entitlement file Here are the pertinent sectsis the Console Log for reference: ... NFCConnectionManager[0x074d6e40].tagReaderSessionDidBecomeActive(:): NFCTagReaderSessionDelegate: Session did become active NFCConnectionManager[0x074d6e40].tagReaderSession(:didDetect:): NFCTagReaderSessionDelegate: Session didDetectTags – 1 tags NFCConnectionManager[0x074d6e40].connected(session:tag:): Manager.connected(session:tag:) - tag: 7 bytes NFCConnection.Type.connection(): NFCConnection.conn
Topic: App & System Services SubTopic: Core OS Tags:
3
0
344
Jul ’25
Reply to ID Card for a University
As it is currently, Apple requires an authorized Credential Manager to deploy Student ID utilizing the NFC chipset with the digital credential located in the Apple Wallet. The Credential Managers are the One Card Providers, such as: Transact/CBORD (formerly Blackboard), ITC, Touchnet and Atrium. They have also added recently Swift Connect, which is not a One Card Provider, as they are more of software integration and development firm that interfaces with the One Card Providers for your declining balance needs and all of the other systems requiring integration, such as: access control systems, parking systems, book store puirchases, network printer access, etc.
Topic: App & System Services SubTopic: Apple Pay Tags:
Jul ’25
iOS App with Wi-Fi Scanner Connectivity – Listing Networks & Seamless Connection
Hi everyone, I’m working on an iOS project where an iPhone needs to connect to external scanners (dedicated hardware devices) over Wi-Fi. The goal is to: Discover available Wi-Fi networks from the scanner devices (broadcasting their own networks). Allow the user to seamlessly connect to the chosen scanner network. Network Discovery: Is there a way to programmatically list available Wi-Fi networks (SSIDs) on iOS without private APIs? If not, are there workarounds (e.g., Bonjour/mDNS)? Seamless Connection: As I see, we can use NEHotspotConfigurationManager to connect to and disconnect from specified networks and there will always be a system alert asking about do we really want to join this network Hardware/Firmware/Software Alternatives: If iOS restrictions prevent this, what alternatives exist? For example: Hardware: Scanners supporting Bluetooth LE for initial pairing, then Wi-Fi provisioning. Firmware: Scanners acting as clients on the same network as the iPhone (e.g., via user’s home/office Wi-Fi). Softwar
Topic: App & System Services SubTopic: Networking Tags:
3
0
298
Jul ’25
Reply to Unable to Invoke NFC In IOS App
A valid provisioning profile for this executable was not found would mean that for some reason the provisioning profile is not found and used when building the app. So, having declared NFC capability in the provisioning profile didn't do anything in this case. Did you download it from the portal? Are you using the correct developer account to build the app? As we can't help with solving build issues using 3rd party development tools, you might want to use the support channels for MAUI to find an answer why the provisioning profile is not available.
Topic: App & System Services SubTopic: Core OS Tags:
Jun ’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 whitelisting of the NFC Tag Reading and Writing (NDEF) entitlement
There is no whitelisting or other kinds of permissions or entitlements required to simply read and write to a writeable tag. You can configure your entitlements and Info.plist entries yourself for these functions. The sample code here: https://developer.apple.com/documentation/corenfc/creating-nfc-tags-from-your-iphone demonstrates how to implement writing to a writeable tag. As long as what you are reading and writing is not a restricted AID, like payment, identity, etc. there are no permissions required.
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
You can check out https://developer.apple.com/documentation/corenfc/building-an-nfc-tag-reader-app for an example of how the entitlements and Info.plist entries are constructed. I can't help you with getting the AID of the NFC device. You may need to contact the manufacturer, if the AIDs are not standard, or documented. Approval depends on what you are trying to do. In order to just read from the tag, or write to the tag, you don't need any approval. If you are trying to emulate a tag (the NFC hardware you are using is a reader), or if the AIDs you are using are of restricted nature (like payment intent, identification, etc.) then you need approval and depending on the region you are operating in, that may or may not be possible, and will require an extensive application process.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jul ’25
whitelisting of the NFC Tag Reading and Writing (NDEF) entitlement
We have been struggling to get support and answeres regarding this roadblock : Request in whitelisting of the NFC Tag Reading and Writing (NDEF) entitlement for our iOS application Our application utilizes Core NFC to enable reading and writing of NFC tags, simplifying user interactions with NFC-enabled devices and services. The NDEF entitlement is essential for our app to deliver its core functionality effectively. Build Environment: Our app is developed and built using Xcode 16.4 on Codemagic’s cloud-based CI/CD platform, which utilizes a compatible macOS version (e.g., macOS Sonoma 14.4 or later). The app targets iOS 18 and uses Core NFC APIs for NDEF tag reading and writing. so far we cant get it to read or write as ios is restricking us
Topic: App & System Services SubTopic: Core OS Tags:
Replies
1
Boosts
0
Views
300
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
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
Do you have the correct AIDs for the NFC device entered in the com.apple.developer.nfc.readersession.iso7816.select-identifiers entry in your Info.plist? Keep in mind that the AIDs have to be an exact match, and you cannot use shortened prefixes
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jul ’25
NFC Error
During EEPROM reading or writing on some appliance devices, the app encounters an error after 6 steps. This issue occurs only on iPhone 14 Pro Max, 15 Pro Max, and 16 Pro models, while all other iPhone models function correctly. Any one with this problem?
Topic: App & System Services SubTopic: Core OS Tags:
Replies
1
Boosts
0
Views
211
Activity
Jul ’25
Inability to Communicate via APDU on iOS Despite NFC Tag Detection
Background: We are developing a cross-platform mobile application that communicates with a custom NFC-enabled hardware device. The hardware expects ISO7816-style APDU commands for data exchange and functions correctly with Android using the IsoDep protocol. Observed Issue on iOS: On iOS, the tag is only detectable via NFCNdefReaderSession, which provides access to INFCNdefTag. Attempting to use NFCTagReaderSession with NFCPollingOption.Iso14443 (which is required for APDU communication) results in no tag detection. As a result, the tag is inaccessible for APDU-based communication on iOS. Since NFCNdefReaderSession does not support APDU, we are unable to establish the required command channel. Constraints: The hardware firmware cannot be changed to support NDEF-based command interpretation. The device expects raw ISO-DEP APDU commands (i.e., Class-Instruction-Param1-Param2-Data-Le). Impact: The lack of ISO7816 tag detection on iOS prevents the app from sending APDU commands, resulting in a platform-sp
Topic: App & System Services SubTopic: Core OS Tags:
Replies
12
Boosts
0
Views
525
Activity
Jul ’25
Is "NFC & SE Platform" required for raw ISO7816 APDU send via NFC?
I stumbled across the Apple NFC & SE Platform while searching for the cause to a persistent missing entitlement error. I am curious if not having this entitlement could be the root cause to my issues? Specifically, I am trying to perform an HMAC-SHA1 challenge-response via NFC on a YubiKey. Part of this entails low level APDU Send commands via NFC. The missing entitlement occurs right after the APDU Send. Per my separate post, I believe I have exhausted all other possible causes to no avail. For reference and details, this is the other post: [https://developer.apple.com/forums/thread/791995)
Topic: App & System Services SubTopic: Core OS Tags:
Replies
2
Boosts
0
Views
339
Activity
Jul ’25
Reply to Root issue is missing entitlement in NFC App
My initial post was not very clear, adding some supporting information below: Initial NFC session establishes successfully Failure occurs immediately on first APDU transmission Configuration & Verification: Xcode Capabilities: Near Field Communication Tag Reading is enabled in the target's Signing & Capabilities tab. entitlements File: com.apple.developer.nfc.readersession.formats is correctly set to an array containing only TAG. (Confirmed ISO7816 should NOT be directly in this array based on Apple documentation). com.apple.developer.nfc.readersession.formats TAG Info.plist Configuration: Privacy - NFC Scan Usage Description (NFCReaderUsageDescription) is present. com.apple.developer.nfc.readersession.iso7816.select-identifiers is correctly configured with an array of relevant YubiKey AIDs, including the OATH AID (A000000527210101) and others. codesign Output : After building the app, running codesign -d --entitlements :- /path/to/YourAppName.app explicitly confirms that the com.app
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jul ’25
Root issue is missing entitlement in NFC App
The root issues is a missing entitlement error. I've jumped through countless hoops of checking/rechecking .entitlement file/plist file, creating new credentials, creating new projects, creating new provisioning profiles with no luck, manual signing, automatic signing. Any suggestions appreciated. Looking at the Provisioning Profile Info shows NFC Tag capabilities is included and NFC Entitlements are included. I'm at a loss... I am including the following: Pertinent output from console Current Info.Plist Current .entitlement file Here are the pertinent sectsis the Console Log for reference: ... NFCConnectionManager[0x074d6e40].tagReaderSessionDidBecomeActive(:): NFCTagReaderSessionDelegate: Session did become active NFCConnectionManager[0x074d6e40].tagReaderSession(:didDetect:): NFCTagReaderSessionDelegate: Session didDetectTags – 1 tags NFCConnectionManager[0x074d6e40].connected(session:tag:): Manager.connected(session:tag:) - tag: 7 bytes NFCConnection.Type.connection(): NFCConnection.conn
Topic: App & System Services SubTopic: Core OS Tags:
Replies
3
Boosts
0
Views
344
Activity
Jul ’25
Reply to ID Card for a University
As it is currently, Apple requires an authorized Credential Manager to deploy Student ID utilizing the NFC chipset with the digital credential located in the Apple Wallet. The Credential Managers are the One Card Providers, such as: Transact/CBORD (formerly Blackboard), ITC, Touchnet and Atrium. They have also added recently Swift Connect, which is not a One Card Provider, as they are more of software integration and development firm that interfaces with the One Card Providers for your declining balance needs and all of the other systems requiring integration, such as: access control systems, parking systems, book store puirchases, network printer access, etc.
Topic: App & System Services SubTopic: Apple Pay Tags:
Replies
Boosts
Views
Activity
Jul ’25
iOS App with Wi-Fi Scanner Connectivity – Listing Networks & Seamless Connection
Hi everyone, I’m working on an iOS project where an iPhone needs to connect to external scanners (dedicated hardware devices) over Wi-Fi. The goal is to: Discover available Wi-Fi networks from the scanner devices (broadcasting their own networks). Allow the user to seamlessly connect to the chosen scanner network. Network Discovery: Is there a way to programmatically list available Wi-Fi networks (SSIDs) on iOS without private APIs? If not, are there workarounds (e.g., Bonjour/mDNS)? Seamless Connection: As I see, we can use NEHotspotConfigurationManager to connect to and disconnect from specified networks and there will always be a system alert asking about do we really want to join this network Hardware/Firmware/Software Alternatives: If iOS restrictions prevent this, what alternatives exist? For example: Hardware: Scanners supporting Bluetooth LE for initial pairing, then Wi-Fi provisioning. Firmware: Scanners acting as clients on the same network as the iPhone (e.g., via user’s home/office Wi-Fi). Softwar
Topic: App & System Services SubTopic: Networking Tags:
Replies
3
Boosts
0
Views
298
Activity
Jul ’25
Reply to Unable to Invoke NFC In IOS App
A valid provisioning profile for this executable was not found would mean that for some reason the provisioning profile is not found and used when building the app. So, having declared NFC capability in the provisioning profile didn't do anything in this case. Did you download it from the portal? Are you using the correct developer account to build the app? As we can't help with solving build issues using 3rd party development tools, you might want to use the support channels for MAUI to find an answer why the provisioning profile is not available.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jun ’25