Search results for

nfc

1,175 results found

Post

Replies

Boosts

Views

Activity

Reply to NFC support in iOS application in India
First, please check the document NFC & SE Platform for secure contactless transactions for the requirements and regional availability of NFC support with Secure Element. NFCTagReaderSession cannot be used for payment cards. You will need to use alternate CoreNFC APIs, which are only available via special entitlements and agreements. The document above will also explain the requirements for getting access to those APIs. Eventually, you will need to enter into an agreement with Apple and request the NFC & SE Platform Entitlement, if you satisfy the requirements as listed in the document above. If you are not able to use those APIs, PassKit framework will be your only remaining option, if appropriate. If you have already requested the relevant entitlements, if approved, you will receive further guidance on how to proceed with your development.
3d
NFC support in iOS application in India
We are developing an iOS application that requires NFC-based communication using ISO 7816 / ISO 14443 standards for secure element interaction as part of a card provisioning workflow. We would like clarification on the following points: Is it possible to provision a payment card or securely add a card to an NFC-enabled device using direct ISO 7816 APDU communication via NFCTagReaderSession? If not, is Apple Pay In-App Provisioning (PassKit framework) the only supported approach for enabling contactless payment functionality on iPhone? What specific entitlements are required if the use case involves secure element communication for token provisioning (not bypassing Apple Pay)? We have already requested the relevant NFC entitlements through our Apple Developer account and are awaiting a response. Any guidance on the correct architecture and approval requirements would be greatly appreciated. Thank you in advance for your support.
1
0
43
4d
Reply to Invoking app clip, that was installed from TestFlight, from a different app.
No, you don't need an HTML page with the app-clip-bundle-id meta tag to fix URL invocation (Notes app or UIApplication.shared.open(url)) for TestFlight App Clips. This meta element is for production web/Safari invocations to trigger the card preview; TestFlight restricts dynamic URL taps/open calls despite green Domain Status and approved swcutil (Site/Fmwk Approval: approved). QR/Local Experience works because it bypasses these limits via explicit developer override. TestFlight Limitations Apple docs confirm TestFlight prioritizes controlled testing: Direct launch from TestFlight app (no card, loads clip). QR/NFC with Local Experience (full card flow). Arbitrary URLs (Notes, other apps) intentionally unsupported to mimic beta safety. Your AASA is perfect appclips entry + /numverify/appclip/* components match, CDN-propagated, swcutil validated. Your Options Method Works for Card+Launch? Setup TestFlight Invocations Partial (testers launch via TF UI) App Store Connect > TestFlight > Build > A
3w
How to hide the NFC reading pop-up prompt?
Dear Apple Engineers, I am using NFCNDEFReaderSession to read information from NFC tags. When calling the begin method of the session, a system dialog/popover appears at the bottom of the screen. Is it possible to suppress or disable this dialog? Thank you for your assistance. Here is my demo code: @IBAction func beginScanning(_ sender: Any) { guard NFCNDEFReaderSession.readingAvailable else { let alertController = UIAlertController( title: Scanning Not Supported, message: This device doesn't support tag scanning., preferredStyle: .alert ) alertController.addAction(UIAlertAction(title: OK, style: .default, handler: nil)) self.present(alertController, animated: true, completion: nil) return } session = NFCNDEFReaderSession(delegate: self, queue: nil, invalidateAfterFirstRead: true) session?.alertMessage = Hold your iPhone near the item to learn more about it. session?.begin() }
1
0
91
3w
Can I hide the NFC App Clip card?
Dear Apple Engineers: My app utilizes the App Clip experience. I would like to prevent the App Clip card from appearing when the host app is running in the foreground. How can this be achieved? I have observed that Alipay (in China) does not display an App Clip card when the device is tapped against a tag while the app is in the foreground, which indicates that this behavior is possible. Thank you for your assistance.
0
0
58
3w
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:
4w
Reply to NFC Secure Element / ISO7816 Entitlement Availability by Region (Indonesia)
Yes, this entitlement is restricted by region, along with other eligibility requirements. These are explained in NFC & SE Platform for secure contactless transactions under the Requirements and availability section. The list of regions which it is available in is also in that section. If this list changes, the updated list will be reflected in this section. Without a special entitlement, apps would be limited to interacting with tags that do not require secure element access. there are no workarounds for such apps based or distributed in regions where special entitlements are not available. There are no supported workarounds of this limitation, if such entitlements are not available for you, whether it is due to a region or other requirements.
Topic: Privacy & Security SubTopic: General Tags:
Jan ’26
NFC Secure Element / ISO7816 Entitlement Availability by Region (Indonesia)
Hello, I would like to seek clarification regarding the availability of the NFC Secure Element (SE) / ISO7816 entitlement by region, specifically for Indonesia. I recently contacted Apple Developer Support regarding the use of NFC for reading ISO7816-compatible cards. I was informed that, at this time, the NFC & Secure Element entitlement is not available in Indonesia. For technical planning and compliance purposes, I would like to confirm the following: Is the NFC Secure Element / ISO7816 entitlement currently restricted by region, and is Indonesia officially unsupported at this time? For apps distributed on the App Store in Indonesia, is Core NFC limited to NDEF and non–Secure Element tag reading only? Are there any publicly supported alternatives or recommended architectural approaches for NFC-based workflows in regions where the Secure Element entitlement is unavailable? Is there any public documentation or guidance that outlines regional availabil
1
0
312
Jan ’26
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
2
0
207
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