Hello, I have developed an iOS application called DinecTag (be.dinec.DinecTag) with a developer account named Dinec International which is registered in Belgium, I received the NFC entitlement valid for Europe and my App is on the App store since some months (the App is used to open doors by presenting the iPhone in front of a special reader) The App is published only on countries inside Europe (it don’t work outside anyway) I would like my App can be used outside Europe, so I need another entitlement called NFC & SE Platform entitlementn to ask for that, I need an account registered in a country covered by that entitlement Dinec is a company that is member of the Lisam group Lisam has an apple developer account registered to USA, called Lisam Systems So I have asked to the owner of that account to add me as a developer in the USA team So when I connect to my developer account, I can switch between Dinec International SA and Lisam Systems on top right of the screen, I am member of the tw
Search results for
nfc
1,125 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hi everyone — I’m developing an iOS passkey/password manager where the private key material must be stored on a physical device (NFC card / USB token). I’m hitting a hard limitation: CoreNFC is not available for use from app extensions, which prevents an appex (e.g. password/credential provider or other extension) from talking directly to an NFC card during an authentication flow.  My questions: 1. Is there any plan to make CoreNFC (or some limited NFC-API) available to app extensions in a future iOS version? If not, could Apple clarify why (security/entitlements/architecture reasons)? 2. Are there any recommended/approved workarounds for a passkey manager extension that needs to access a physical NFC token during authentication? (For example: background tag reading that launches the containing app, or some entitlement for secure NFC card sessions.) I’ve read about background tag reading, but that seems to be about system/OS handling of tags rather than giving ext
We cannot discuss why CoreNFC is not available from app extensions. It just isn't. We cannot discuss future plans either. If this is important for your use case, we always welcome feature requests via the Feedback Assistant There are no ticks, workaround, or entitlements to make CoreNFC work from an extension. Nor it is possible to launch the main app form an extension. Your option 3 of the main app performing the NFC functions and then sharing the data with the extension is about the only way this would seem to work for your use case if I understand it correctly.
Topic:
App & System Services
SubTopic:
Hardware
Tags:
You should start by checking the error returned when your reader session is invalidated. You say all setup is done, assuming correctly, but that's where mistakes are most commonly made, by not including the correct entitlements, and declaring the AIDs you need to use with the passport. Also, reading passports is not going to be as simple as reading a regular NFC tag by just tapping. They will usually be protected by an access protocol. You will need to determine the protocol used by the passport you are trying to scan. Older passports use BAC (Basic Access Control), where newer ones may be using PACE (Password Authenticated Connection Establishment). In your app, you need to have implemented the correct protocol both in code and in user flow.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Hi, I just having an issue with ePassport NFC. When development all requirement setup already included. After build success when trying to scan the passport, it froze there. Nothing happen , look like it not detecting the passport. I check my device and passport no issue. So can help me since its urgent part of the development. It has been blocker since day 1 of the development
Hello I am developing an iOS app and would like to read an EMV card that is issued by me and want my customers to tap to activate simply to validate the possession of the card at the time of activation. Any suggestions welcome on how can i achieve this using either NFC Framework or secure elements
Is tap to pay still needed? i don't want to read passes from wallet nor accept payments. I want to use nfc card reader on the credit card from the bank i work for in the bank of the app i work for to validate the card and activate it. I don't see how it would be related to tap to pay or wallet. we already have apple pay setup but we still get an error about the entitlements missing. So i'm wondering which one i need and if i need to do a specific request to have them knowing we are a bank and already have com.apple.developer.payment-pass-provisioning
Topic:
App & System Services
SubTopic:
Tap to Pay on iPhone
Tags:
Unexpected behavior encountered when scanning NFC tags. Imagine a link shortener web service where users can create lots of different URLs that are hosted on the same domain eg, https://short.com/unique-path The service has optional App Clip capability -- users can select any of their links and have the service create an App Clip for the selected link(s). Users can encode their URLs into NFC tags and have their customers scan NFC tags. Let's take just two URLs for example: https://short.com/foo https://short.com/bar The /foo link does have an App Clip associated with it while /bar does not have it. Each link has been encoded into appropriate NFC tag. Expected behavior when scanning from an iPhone: /foo -- shows an App Clip popup. /bar -- shows a Open in Safari default notification. What's actually happening /foo -- opens App Clip poput with correct metadata (title, subtitle, image) which is totally expected behavior. /bar (the one that doesn't have app clip associated with
This seems to be related to iOS26, app clips also no longer work over NFC
Topic:
App Store Distribution & Marketing
SubTopic:
General
Tags:
We have the same issue with NFC: app clips stopped working on iOS 26, stating App Clip unavailable
Topic:
UI Frameworks
SubTopic:
General
Tags:
Here's another interesting thing that's happening. I've tried clearing experience cache (Settings -> Developer -> App Clips Testing -> Clear Experience Cache) and immediately after that scanning URLs that don't have app clips as invocation URLs. What sometimes (3 out of 10 attempts) started happening is this: Clear cache Scan NFC tag Shows Open in Safari notification // Expected behavior Scan NFC tag again Shows No app clip available Scan NFC tag again and again and again Shows CPSError Domain error 2 All other attempts it just shows CPSErrorDomain.
Topic:
App & System Services
SubTopic:
General
Tags:
Another interesting thing is when reading an NFC card that has just domain without path, it works as expected: https://short.com -- Shows Open in Safari notification, expected behavior since there's no App Clip with this invocation URL. https://short.com/ -- Shows Open in Safari notification, expected behavior since there's no App Clip with this invocation URL. https://short.com/a -- Shows the CPSErrorDomain error 2 popup. There's no App Clip Invocations registered with this URL. When checking these three URLs at Settings -> Developer -> App Clips Testing -> Diagnostics -- it shows the same information for all three URLs (it just shows the same as in the second Diagnostics screenshot I attached in replies above). *Just a reminder that short.com is just an example domain here.
Topic:
App & System Services
SubTopic:
General
Tags:
Foreword: I filed a feedback a week ago and so far no one replied or at least acknowledged my feedback. That's why I'm writing here now to get some more attention (hopefully, thanks). I recorded a video to show you what exactly is happening. I am not sure where the issue belongs to exactly but it is related to associated domains, the camera (QR codes), the NFC module, App Intents and Control Center controls. https://youtu.be/sT2bZLs_6rA FB20418059 (I added some tags that are somehow related to the associated domain issue)
The 20 second limit is a hard limit, and there is no opportunities to extend it. Furthermore, you may need to plan for a cooldown period between sessions as well. My recommendation would be to reconsider if NFC is the correct tool for what you are trying to do. A typical NFC transaction takes a few seconds, and even reading complex documents take no longer than approximately 10 seconds. The time limits on the sessions have been determined based on common use cases, and as the 20 seconds limit cannot be extended, and you may have to require a hardware imposed cooldown period between sessions, your users may find this process inconvenient. But in the end, it is your business to decide if using NFC despite not satisfying your requirements is something to build upon.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I’m developing an iOS application using CoreNFC and working with ISO7816 tags. My use case involves exchanging APDU commands with a hardware device, but some operations can take more than 20 seconds. From my testing, I see that: The NFC reader session itself lasts about 60 seconds. But once a tag is connected, the connection seems to drop after ~20 seconds, and I receive a “connection lost” / session invalidated error. My questions are: Is this ~20-second connection window a hard limit enforced by iOS? Is there any way to extend this timeout for long-running APDU operations? If not, what’s the recommended design pattern for handling these scenarios? For example, should I split the process into smaller APDU commands and prompt the user to re-tap when the session times out? Any guidance or best practices for handling long NFC exchanges on iOS would be greatly appreciated.