Search results for

“nfc”

1,201 results found

Post

Replies

Boosts

Views

Activity

Reply to Crash on CardSession
Pretty sure CardSession.isEligible() is not doing anything to crash your app. You will get this crashing error when you already have an active NFC session in your app. I would suggest to check that your code checks for previous sessions that may have not been closed, or perhaps a lingering variable holding the previous session that hasn't been released yet, etc. In other words, this is a bug in your code you need to resolve. Not an issue caused by CardSession.isEligible()
Topic: App & System Services SubTopic: Core OS Tags:
6d
Reply to HCE not working in Testflight Builds
Hi Team, Could you clarify whether the Apple reference document addresses NFC HCE support across multiple regions? The document mentions that support will expand beyond the European Economic Area (EEA). We need to confirm: - Will HCE support be limited to EEA countries only, or - Will it also extend to the other countries listed in the document? Please advise. Apple reference document link: https://developer.apple.com/support/nfc-se-platform/ We tested the app in Basingstoke, United Kingdom, and we still have not seen successful operation with HCE. Could you please clarify whether HCE is supported in the specified region? Note: We tested in Basingstoke, United Kingdom, and received an “HCE not eligible” error. Please confirm whether this region is included in the list of HCE-supported countries.
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
1w
VAS entitlement
Hi, I have the NFC &SE entitlement but still not able to read a pass from the apple wallet on another iphone. The logs show that the NFCVASReader session is initialised and the readerSessionDidBecomeActive — session is live, waiting for pass tap, but nothing is read. The pass is nfc enabled with correct encryption key. It feels like I am still missing some kind of entitlement to read VAS from passes - could anyone advise please?
Topic: Developer Tools & Services SubTopic: Apple Developer Program Tags:
0
0
66
2w
Reply to My app has been waiting for review for almost three weeks now
@App Review Yes, the review has been completed with the status “Rejected” and the reason provided was: “The app contains hidden features. Specifically, this app contains hidden financial services.” I do not understand what this conclusion was based on. The app does not contain any payment functionality whatsoever. The app is intended for reading and writing NFC tag data. This is also not the first version of the app. In this version, the only significant addition was the ability to attach a photo image to a tag card, and nothing more. Please forgive me, but I am starting to feel as though I am simply being mocked. I strongly request that a phone call with an Apple representative be arranged.
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
3w
UI layout overlaps in bottom sheet upon screen rotation during NFC Reader session
Hello I am experiencing a layout issue where UI components overlap in a bottom sheet during screen rotation while an NFC Reader session is active. The NFC Reader session initializes and displays the bottom sheet properly. However, if the device is rotated while this sheet is on screen, the layout breaks, and elements appear overlapped. I have attached a sample image demonstrating this rendering issue. Is there a known workaround to fix this layout distortion or force a proper layout update during an active NFC session?Any insights or suggestions would be greatly appreciated. Thanks!
Topic: App & System Services SubTopic: Core OS Tags:
1
0
254
3w
Bottom sheet does not adapt to screen rotation after presenting NFC Reader session
Hello I am implementing an NFC Reader session in my app, and presenting the bottom sheet works completely fine. However, I am facing an issue with screen rotation. If I rotate the device while the NFC bottom sheet is active, the sheet does not adapt or resize according to the new screen orientation. Is there a way to force the NFC bottom sheet to update its layout or fix this rotation issue?Any help or workarounds would be greatly appreciated. Thanks!
Topic: App & System Services SubTopic: Core OS Tags:
1
0
254
3w
App category for non-custodial crypto wallet using NFCTagReaderSession only for identity credential exchange with POS device — Guideline 3.1.5 scope?
We are developing a non-custodial cryptocurrency wallet app with the following characteristics: Architecture: Users hold their own private keys at all times (we never custody any assets). The app includes identity credential verification: KYC-verified identity data (Verifiable Credentials / DID-based) is exchanged between the payer's iPhone and a counterparty device for identity verification purposes. NFCTagReaderSession is used only to exchange identity credential data via our proprietary, non-payment ISO 7816 AID with the counterparty device. Cryptocurrency transactions are submitted entirely over the internet (blockchain RPC), completely independent of the NFC session. NFC is NOT used to: Transmit cryptocurrency or payment instructions. Interact with any EMV payment AID or Secure Element. Replace or emulate Apple Pay or any payment card. Jurisdiction & licensing context: The app is being developed by a Japanese company for initial launch in Japan. While this question is posted from an
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
0
0
131
May ’26
Core NFC on iPhone returns “Sandbox restriction” when starting NFCNDEFReaderSession with Personal Team / free account
Hi, I am trying to build a very simple iOS app in Xcode that starts an NFCNDEFReaderSession when I press a button. My goal right now is only to verify that the NFC reading process starts correctly on a real iPhone. I am not trying to publish the app on the App Store. When I try to start the session, I get this error in the console: -[NFCHardwareManager areFeaturesSupported:outError:]:435 XPC Error: Error Domain=NSCocoaErrorDomain Code=4099 The connection to service named com.apple.nfcd.service.corenfc was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction. UserInfo={NSDebugDescription=The connection to service named com.apple.nfcd.service.corenfc was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction.} and then my app reports that NFC is not available on this device. Important details: I added Near Field Communication Tag Reading in Signing & Capabilities. I added the NFC privacy usage description in the target sett
Topic: App & System Services SubTopic: Hardware Tags:
0
0
319
Apr ’26
Reply to The right way to extend UIRequiredDeviceCapabilities
[quote='885705022, Frankois944, /thread/729371?answerId=885705022#885705022, /profile/Frankois944'] is it possible to force the UIRequiredDeviceCapabilities? [/quote] I believe that App Review has a way to allow this. However, before you reach out to them you should carefully think about this choice. By narrowing the set of supported devices, you’re prevent existing users of your app from updating to your latest version. You should carefully consider whether that’s worth it, especially when dealing with a very old app. It might be better to simply ship a new app. Or do what endecotp’s recommended above, that is, not make NFC a requirement. Or you could do both, that is, publish a new app that requires NFC and also update your old app such that the existing functionality, the stuff that you’re users have been using for years, continues to work on devices with NFC. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: General Tags:
Apr ’26
Reply to HCE not working in Testflight Builds
TestFlight distribution and testers have the same requirements as your end users who would be downloading your app from the App Store. This means the testers will have to be: physically be in the EEA logged on to their phones with an iCloud account based in the EEA As explained in the documentation HCE-based contactless NFC transactions for apps in the European Economic Area (EEA), if you have testers outside the EEA, you cannot use TestFlight builds. Testing requirements Apple has developed a solution which allows HCE Developers to develop and test HCE Payment Apps outside the EEA. The new solution allows development and testing on a device through known and well-used means such as Xcode and provisioning of profiles used for testing on devices within a developer’s organization. Developers will be able to have up to 100 test devices outside the EEA. To test HCE-based contactless transactions, you’ll need to test with an iPhone and NFC hardware. CardSession requires the presence of an NFC
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
Apr ’26
Reply to AID A000000308000010000100 seems mandatory to communicate with any smart card through TKSmartCardSlotNFCSession
I’m not entirely sure who allocates AID values, but some rummaging around on the ’net confirms that AID A000000308000010000100 is definitely associated with PIV. As to your current issue, the doc comments in for the -[TKSmartCardSlotManager createNFCSlotWithMessage:completion:] method says: Warning Caller requires com.apple.developer.nfc.readersession.iso7816.select-identifiers Info.plist record which specifies application identifiers of the NFC cards link which suggests that your solution is the right one. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Privacy & Security SubTopic: General Tags:
Apr ’26
Reply to Provisioning profiles marked "Ineligible" for Contactless Pass Provisioning even though entitlement is present in profile
Dear Team, We request your urgent support to proceed with uploading our application to the Apple App Store. Currently, several of our customers are awaiting NFC credentials provisioning via Apple Wallet, and the delay due too thi issues and is directly impacting their onboarding and usage. This situation is significantly affecting our business operations and customer experience. We kindly ask you to prioritize this request(102864920121.) and let us know if any additional information, changes, or compliance items are required from our side to expedite the process. Your prompt assistance will be greatly appreciated, as many customers are actively waiting for access. Thank you for your support.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Apr ’26
AID A000000308000010000100 seems mandatory to communicate with any smart card through TKSmartCardSlotNFCSession
I am using the CryptoTokenKit API in order to communicate with smart cards through NFC, with TKSmartCardSlotNFCSession. I call the createNFCSlotWithMessage method from TKSmartCardSlotManager, which displays successfuly the NFC dialog. However, when I put any smart card next to the phone, the NFC dialog shuts down instantly. I notice the following log in the system console: -[_NFReaderSession(Entitlement) validateAID:allowsPrefixMatch:]:317 Non-permissible identifier: A000000308000010000100 When I add the A000000308000010000100 AID mentioned in the error message to the Info.plist of my application, the NFC dialog does not shut down anymore and I am able to communicate with the smart card (using TKSmartCard). This behavior has been reproduced on an iPhone 16e, iOS 26.4. This AID does not correspond to anything in the smart card. It seems to be related to PIV, but this behavior also occurs with cards that are not PIV (PKCS#15...). Also, with an implementation using CoreNFC API
Topic: Privacy & Security SubTopic: General Tags:
3
0
262
Apr ’26
Can third-party transit apps receive the NFC HCE entitlement in the EEA?
Hi everyone, I'm looking for clarity on the NFC HCE entitlement process for third-party apps in the EEA. I've built an alternative client for Milan's public transport app (ATM Milano) on Android by reverse engineering the original app. It offers the same core functionality(users still need a valid transit subscription) just with a different UI and better UX. I'd now like to port it to iOS. According to Apple's documentation, NFC HCE was opened to third parties in the EEA starting with iOS 17.4. However, the API requires an entitlement from Apple. I have a few questions: Is the entitlement required regardless of distribution method? Even if I distribute through a third-party marketplace like AltStore PAL rather than the App Store, do I still need Apple to grant the HCE entitlement? Are third-party/alternative clients eligible for the entitlement? My app isn't a competing transit provider, it's an alternative frontend for an existing service. Users must hold a valid subscription with the offic
Topic: App & System Services SubTopic: Core OS Tags:
1
0
199
Apr ’26
Reply to Crash on CardSession
Pretty sure CardSession.isEligible() is not doing anything to crash your app. You will get this crashing error when you already have an active NFC session in your app. I would suggest to check that your code checks for previous sessions that may have not been closed, or perhaps a lingering variable holding the previous session that hasn't been released yet, etc. In other words, this is a bug in your code you need to resolve. Not an issue caused by CardSession.isEligible()
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
6d
Reply to HCE not working in Testflight Builds
Hi Team, Could you clarify whether the Apple reference document addresses NFC HCE support across multiple regions? The document mentions that support will expand beyond the European Economic Area (EEA). We need to confirm: - Will HCE support be limited to EEA countries only, or - Will it also extend to the other countries listed in the document? Please advise. Apple reference document link: https://developer.apple.com/support/nfc-se-platform/ We tested the app in Basingstoke, United Kingdom, and we still have not seen successful operation with HCE. Could you please clarify whether HCE is supported in the specified region? Note: We tested in Basingstoke, United Kingdom, and received an “HCE not eligible” error. Please confirm whether this region is included in the list of HCE-supported countries.
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
Replies
Boosts
Views
Activity
1w
VAS entitlement
Hi, I have the NFC &SE entitlement but still not able to read a pass from the apple wallet on another iphone. The logs show that the NFCVASReader session is initialised and the readerSessionDidBecomeActive — session is live, waiting for pass tap, but nothing is read. The pass is nfc enabled with correct encryption key. It feels like I am still missing some kind of entitlement to read VAS from passes - could anyone advise please?
Topic: Developer Tools & Services SubTopic: Apple Developer Program Tags:
Replies
0
Boosts
0
Views
66
Activity
2w
Reply to My app has been waiting for review for almost three weeks now
@App Review Yes, the review has been completed with the status “Rejected” and the reason provided was: “The app contains hidden features. Specifically, this app contains hidden financial services.” I do not understand what this conclusion was based on. The app does not contain any payment functionality whatsoever. The app is intended for reading and writing NFC tag data. This is also not the first version of the app. In this version, the only significant addition was the ability to attach a photo image to a tag card, and nothing more. Please forgive me, but I am starting to feel as though I am simply being mocked. I strongly request that a phone call with an Apple representative be arranged.
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Replies
Boosts
Views
Activity
3w
UI layout overlaps in bottom sheet upon screen rotation during NFC Reader session
Hello I am experiencing a layout issue where UI components overlap in a bottom sheet during screen rotation while an NFC Reader session is active. The NFC Reader session initializes and displays the bottom sheet properly. However, if the device is rotated while this sheet is on screen, the layout breaks, and elements appear overlapped. I have attached a sample image demonstrating this rendering issue. Is there a known workaround to fix this layout distortion or force a proper layout update during an active NFC session?Any insights or suggestions would be greatly appreciated. Thanks!
Topic: App & System Services SubTopic: Core OS Tags:
Replies
1
Boosts
0
Views
254
Activity
3w
Bottom sheet does not adapt to screen rotation after presenting NFC Reader session
Hello I am implementing an NFC Reader session in my app, and presenting the bottom sheet works completely fine. However, I am facing an issue with screen rotation. If I rotate the device while the NFC bottom sheet is active, the sheet does not adapt or resize according to the new screen orientation. Is there a way to force the NFC bottom sheet to update its layout or fix this rotation issue?Any help or workarounds would be greatly appreciated. Thanks!
Topic: App & System Services SubTopic: Core OS Tags:
Replies
1
Boosts
0
Views
254
Activity
3w
App category for non-custodial crypto wallet using NFCTagReaderSession only for identity credential exchange with POS device — Guideline 3.1.5 scope?
We are developing a non-custodial cryptocurrency wallet app with the following characteristics: Architecture: Users hold their own private keys at all times (we never custody any assets). The app includes identity credential verification: KYC-verified identity data (Verifiable Credentials / DID-based) is exchanged between the payer's iPhone and a counterparty device for identity verification purposes. NFCTagReaderSession is used only to exchange identity credential data via our proprietary, non-payment ISO 7816 AID with the counterparty device. Cryptocurrency transactions are submitted entirely over the internet (blockchain RPC), completely independent of the NFC session. NFC is NOT used to: Transmit cryptocurrency or payment instructions. Interact with any EMV payment AID or Secure Element. Replace or emulate Apple Pay or any payment card. Jurisdiction & licensing context: The app is being developed by a Japanese company for initial launch in Japan. While this question is posted from an
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Replies
0
Boosts
0
Views
131
Activity
May ’26
Core NFC on iPhone returns “Sandbox restriction” when starting NFCNDEFReaderSession with Personal Team / free account
Hi, I am trying to build a very simple iOS app in Xcode that starts an NFCNDEFReaderSession when I press a button. My goal right now is only to verify that the NFC reading process starts correctly on a real iPhone. I am not trying to publish the app on the App Store. When I try to start the session, I get this error in the console: -[NFCHardwareManager areFeaturesSupported:outError:]:435 XPC Error: Error Domain=NSCocoaErrorDomain Code=4099 The connection to service named com.apple.nfcd.service.corenfc was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction. UserInfo={NSDebugDescription=The connection to service named com.apple.nfcd.service.corenfc was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction.} and then my app reports that NFC is not available on this device. Important details: I added Near Field Communication Tag Reading in Signing & Capabilities. I added the NFC privacy usage description in the target sett
Topic: App & System Services SubTopic: Hardware Tags:
Replies
0
Boosts
0
Views
319
Activity
Apr ’26
Reply to The right way to extend UIRequiredDeviceCapabilities
[quote='885705022, Frankois944, /thread/729371?answerId=885705022#885705022, /profile/Frankois944'] is it possible to force the UIRequiredDeviceCapabilities? [/quote] I believe that App Review has a way to allow this. However, before you reach out to them you should carefully think about this choice. By narrowing the set of supported devices, you’re prevent existing users of your app from updating to your latest version. You should carefully consider whether that’s worth it, especially when dealing with a very old app. It might be better to simply ship a new app. Or do what endecotp’s recommended above, that is, not make NFC a requirement. Or you could do both, that is, publish a new app that requires NFC and also update your old app such that the existing functionality, the stuff that you’re users have been using for years, continues to work on devices with NFC. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’26
Reply to The right way to extend UIRequiredDeviceCapabilities
Hello, We're reviving of a very old app, we need to use the same app-id. The new one requires NFC and, so, it can now only run on iPhone. is it possible to force the UIRequiredDeviceCapabilities ?
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’26
Reply to HCE not working in Testflight Builds
TestFlight distribution and testers have the same requirements as your end users who would be downloading your app from the App Store. This means the testers will have to be: physically be in the EEA logged on to their phones with an iCloud account based in the EEA As explained in the documentation HCE-based contactless NFC transactions for apps in the European Economic Area (EEA), if you have testers outside the EEA, you cannot use TestFlight builds. Testing requirements Apple has developed a solution which allows HCE Developers to develop and test HCE Payment Apps outside the EEA. The new solution allows development and testing on a device through known and well-used means such as Xcode and provisioning of profiles used for testing on devices within a developer’s organization. Developers will be able to have up to 100 test devices outside the EEA. To test HCE-based contactless transactions, you’ll need to test with an iPhone and NFC hardware. CardSession requires the presence of an NFC
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
Replies
Boosts
Views
Activity
Apr ’26
Reply to AID A000000308000010000100 seems mandatory to communicate with any smart card through TKSmartCardSlotNFCSession
I’m not entirely sure who allocates AID values, but some rummaging around on the ’net confirms that AID A000000308000010000100 is definitely associated with PIV. As to your current issue, the doc comments in for the -[TKSmartCardSlotManager createNFCSlotWithMessage:completion:] method says: Warning Caller requires com.apple.developer.nfc.readersession.iso7816.select-identifiers Info.plist record which specifies application identifiers of the NFC cards link which suggests that your solution is the right one. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’26
Reply to Provisioning profiles marked "Ineligible" for Contactless Pass Provisioning even though entitlement is present in profile
Dear Team, We request your urgent support to proceed with uploading our application to the Apple App Store. Currently, several of our customers are awaiting NFC credentials provisioning via Apple Wallet, and the delay due too thi issues and is directly impacting their onboarding and usage. This situation is significantly affecting our business operations and customer experience. We kindly ask you to prioritize this request(102864920121.) and let us know if any additional information, changes, or compliance items are required from our side to expedite the process. Your prompt assistance will be greatly appreciated, as many customers are actively waiting for access. Thank you for your support.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Apr ’26
AID A000000308000010000100 seems mandatory to communicate with any smart card through TKSmartCardSlotNFCSession
I am using the CryptoTokenKit API in order to communicate with smart cards through NFC, with TKSmartCardSlotNFCSession. I call the createNFCSlotWithMessage method from TKSmartCardSlotManager, which displays successfuly the NFC dialog. However, when I put any smart card next to the phone, the NFC dialog shuts down instantly. I notice the following log in the system console: -[_NFReaderSession(Entitlement) validateAID:allowsPrefixMatch:]:317 Non-permissible identifier: A000000308000010000100 When I add the A000000308000010000100 AID mentioned in the error message to the Info.plist of my application, the NFC dialog does not shut down anymore and I am able to communicate with the smart card (using TKSmartCard). This behavior has been reproduced on an iPhone 16e, iOS 26.4. This AID does not correspond to anything in the smart card. It seems to be related to PIV, but this behavior also occurs with cards that are not PIV (PKCS#15...). Also, with an implementation using CoreNFC API
Topic: Privacy & Security SubTopic: General Tags:
Replies
3
Boosts
0
Views
262
Activity
Apr ’26
Can third-party transit apps receive the NFC HCE entitlement in the EEA?
Hi everyone, I'm looking for clarity on the NFC HCE entitlement process for third-party apps in the EEA. I've built an alternative client for Milan's public transport app (ATM Milano) on Android by reverse engineering the original app. It offers the same core functionality(users still need a valid transit subscription) just with a different UI and better UX. I'd now like to port it to iOS. According to Apple's documentation, NFC HCE was opened to third parties in the EEA starting with iOS 17.4. However, the API requires an entitlement from Apple. I have a few questions: Is the entitlement required regardless of distribution method? Even if I distribute through a third-party marketplace like AltStore PAL rather than the App Store, do I still need Apple to grant the HCE entitlement? Are third-party/alternative clients eligible for the entitlement? My app isn't a competing transit provider, it's an alternative frontend for an existing service. Users must hold a valid subscription with the offic
Topic: App & System Services SubTopic: Core OS Tags:
Replies
1
Boosts
0
Views
199
Activity
Apr ’26