Search results for

“nfc”

1,224 results found

Post

Replies

Boosts

Views

Activity

Reply to Can an iPhone be used as an NFC terminal to read Apple Wallet passes from another iPhone?
Follow up question to this. I am trying to do something similar -- create an iOS app that train conductors will use, and they would need to scan people's transit cards in the app to check how much credit they have left on their transit card. Most people have set their transit cards on express mode (no need for biometric authentication). My question is, using the NFC & SE Platform entitlement, can developers read transit cards without it requiring user authentication? Or does the user need to unlock their phone before scanning, even if it is set to express mode?
Topic: App & System Services SubTopic: Wallet Tags:
Apr ’25
Reply to Can an iPhone be used as an NFC terminal to read Apple Wallet passes from another iPhone?
It is technically possible. But like you surmised it is restricted due to Secure Element isolation. Basic CoreNFC APIs do not support identity or payment related AIDs. But there is a new NFC & SE Platform for secure contactless transactions Information here: NFC & SE Platform for secure contactless transactions Before investing time and resources, first you should examine the Requirements and availability section to make sure these are available for use in your or your client's region, and your use case and company specifics are suitable. If it is, then you can follow the instructions at that document to apply for access to the API. Any information not clarified/present at this link will be provided once you request access and sign a confidentiality agreement. Details are in the Requesting access to the NFC & SE Platform section. Technically, you will be using the CredentialSession APIs We cannot answer whether this API would be suitable for your specific use case. You w
Topic: App & System Services SubTopic: Wallet Tags:
Apr ’25
Can an iPhone be used as an NFC terminal to read Apple Wallet passes from another iPhone?
Hi all, I'm working on a use case where a customer checks in at a point of service (e.g., a cafeteria or restaurant) using their Apple Wallet pass (e.g., a digital employee badge). In this scenario, we would like to use an iPhone (with a custom iOS app) as the NFC terminal to read the pass directly from the customer's iPhone over NFC. I’m aware that Tap to Pay on iPhone allows NFC-based payment acceptance, but it’s unclear if similar functionality is available or permitted for reading access-type passes from another iPhone via NFC. Key questions: Is it technically possible for an iPhone to act as an NFC reader for a Wallet pass on another iPhone? If not, is this restricted due to Secure Element isolation or protocol limitations? Is there any Apple-supported path for building such a solution — or is certified external hardware (e.g., HID, Wavelynx) the only option? I’ve reviewed the Core NFC and PassKit documentation but couldn't find a definitive answer. T
3
0
911
Apr ’25
Reply to Why my app clips is Unavailable
In the Diagnostics section of the Settings app, the NFC domain shows a warning: “The URL does not match the associated domains for this App Clip.” However, I have verified that my AASA configuration is correct, and the cached AASA file on https://app-site-association.cdn-apple.com/ is also correct.
Topic: UI Frameworks SubTopic: General Tags:
Mar ’25
Get NFC Data Identity card
Hello, I have to create an app in Swift that it scan NFC Identity card. It extract data and convert it to human readable data. I do it with below code import CoreNFC class NFCIdentityCardReader: NSObject , NFCTagReaderSessionDelegate { func tagReaderSessionDidBecomeActive(_ session: NFCTagReaderSession) { print((session.description)) } func tagReaderSession(_ session: NFCTagReaderSession, didInvalidateWithError error: any Error) { print(NFC Error: (error.localizedDescription)) } var session: NFCTagReaderSession? func beginScanning() { guard NFCTagReaderSession.readingAvailable else { print(NFC is not supported on this device) return } session = NFCTagReaderSession(pollingOption: .iso14443, delegate: self, queue: nil) session?.alertMessage = Hold your NFC identity card near the device. session?.begin() } func tagReaderSession(_ session: NFCTagReaderSession, didDetect tags: [NFCTag]) { guard let tag = tags.first else { session.invalidate(errorMessage: No tag detected) return
0
0
370
Mar ’25
JPEG2000 (JP2) Decoding Works on iOS 16 but Fails on iOS 18
I am extracting a JPEG2000 (JP2) facial image from an NFC passport chip (ISO/IEC 19794-5) and attempting to create a UIImage from it. On iOS 16, the following code works fine: import ImageIO import UIKit func getUIImage(from imageData: [UInt8]) -> UIImage? { let data = Data(imageData) guard let imageSource = CGImageSourceCreateWithData(data as CFData, nil), let cgImage = CGImageSourceCreateImageAtIndex(imageSource, 0, nil) else { print(Failed to decode JP2 image!) return nil } return UIImage(cgImage: cgImage) } However, on iOS 18, this fails with errors like: initialize:1415: *** invalid JPEG2000 file *** makeImagePlus:3752: *** ERROR: 'JP2 ' - failed to create image [-50] CGImageSourceCreateImageAtIndex: *** ERROR: failed to create image [-59] Questions: Did Apple remove or modify JPEG2000 support in iOS 18? Is there an official workaround for decoding JPEG2000 on iOS 18? Should I use Vision/Metal/Core Image instead? Is there a recommended way to convert JPEG2000 to JPEG/PNG before creating a UII
3
0
617
Mar ’25
Reply to HCE AID application coupling
At this time there isn't a facility to launch specific apps for specific AIDs. It's an all or none situation. But I am sure the NFC team would love to hear your thoughts in detail about this for a possible future enhancement. The typical way to make such enhancement requests would be via the Feedback Assistant.
Topic: App & System Services SubTopic: Core OS Tags:
Mar ’25
Reply to HCE AID application coupling
Thank you for your swift answer. FYI: Our app is for attendance registration, not payment. I do expect our app to be launched automatically when the phone emulating a card (HCE) has received an AID that is registered to that app. (I need to register it when compiling the app in xcode) I understand that the choice of the default contactless app is the users. But that directs all nfc transactions to this default app, right? So how can multiple apps (or wallets) for different purposes be installed on a iPhone, and still work together? If I ask the user to make our app the default one, how can the others still work? It means that doing attendance registration with our app, would make the phone not unusable for other functions, like payments. Is there a way to coexist?
Topic: App & System Services SubTopic: Core OS Tags:
Mar ’25
Reply to HCE AID application coupling
Are you expecting your app to be launched automatically when near a reader? Then your app will need to become the default payment app. There is no API to set the default payment app. This can only done by the user through the Settings app. Once you have successfully built and installed your app, properly configured with the necessary entitlements, the users should be seeing the option to make that app the default app in Settings->General->Contactless & NFC For this setting option to show up (or for any any of the EEA based features to work) Your app must be correctly configured and built with the correct entitlements and the necessary APIs Your testing device must physically be located in the EEA and is a supported type (iPhone only). The signed-in Apple ID on the device must be registered in an EEA country or region. You will need to contact the entitlements team and ask for the HCE Default App entitlement. Keep in mind that this functionality can only be tested within the EEA. As for the
Topic: App & System Services SubTopic: Core OS Tags:
Mar ’25
Does iPhone Xr and up support ISO 14443 Type B Tags
I am unable to get an iPhone Xr (iOS 18) or iPhone 15 to interact with Texas Instruments RF430CL330H NFC tag. This is an ISO 14443B-compliant tag supporting NDEF. It is NFC Tag Type 4. A Samsung S23 with Android 14 and NFC Tools v8.11 reads and writes NDEF data with this tag as expected. The iPhones with NFC Tools v2.31 do not. For the following comparison the NDEF memory is written with a pre-loaded text data record. NFC Tools on Android reports the following: Tag Type: ISO 14443-4 Technologies Available: IsoDep, NfcB, Ndef Serial Number: Format: NFC Forum Type 4 Text Record 1: UTF-8 (en) Hello World! NFC Tools on iOS (iPhones) reports the following: Tag Type: ISO 7816 Technologies Available: Unknown Serial Number: Format: Text Record 1: Error response: This nfc tag is not supported Attempting to write a text message with NFC Tools on the iPhones returns An error occurred during writing process Other NDEF records (URL and Sear
2
0
589
Mar ’25
Reply to Error "The operation couldn't be completed. (CPSErrorDomain error 2.)" in AppClip sheet
Adding +1 that our App Clip has seen CPSErrorDomain error 2 reported by customers on and off during the last week when invoked by an NFC tag scan. (We haven't released an app update in months.) I haven't been able to reproduce this locally on one of our test phones, so no sysdiagnose to submit, but I will keep trying. For most customers, the App Clip is working. But we're inconsistently seeing these other two behaviors: The customer is taken to our website in Safari instead of displaying the App Clip. The App Clip appears, broken, as seen in the attached photo with CPSErrorDomain error 2.
Topic: UI Frameworks SubTopic: General Tags:
Mar ’25
Error "The operation couldn't be completed. (CPSErrorDomain error 2.)" in AppClip sheet
A few days ago scanning NFC tags or QR codes for AppClips with advanced experiences started showing the error The operation couldn't be completed. (CPSErrorDomain error 2.) in the AppClip sheet as seen here: We are providing AppClips to our customers and they trust AppClips to always work, since it is a big part of their business. Since this is happening at our customers phones and on the phones of their customers, I don't have a sysdiagnose. I already created a feedback entry about this FB16601674. We checked everything, our AASA file, the Appstore Experiences.
8
0
866
Feb ’25
Reply to NFC Communication Issues on iPhone 12–15 with NXP NTAG 5 (ISO15693 Pass-Through Mode)
As you are observing different behaviors on different iPhone models, this is best looked at by our NFC team. Filing a Feedback report with some logging will be the best way for us to investigate the issue further. First, please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Wallet for iOS to install a logging profile on your device. Once that is installed, then reproduce the issue. Once reproduced, then follow the instructions at the above link to create a sysdiagnose Then use the Feedback Assistant. to create a report and include a detailed description of the issue, details of the tags/devices you are using, and the sysdiagnose from the above step. Also include the following info: What is the setup on the device. Including apple wallet settings Please provide sample app if you have one, or can create one Video capture of the failure scenario so we can confirm the positioning of the NFC antenna the Bundle ID of the app you have tested this
Topic: App & System Services SubTopic: Drivers Tags:
Feb ’25
Reply to Can an iPhone be used as an NFC terminal to read Apple Wallet passes from another iPhone?
Follow up question to this. I am trying to do something similar -- create an iOS app that train conductors will use, and they would need to scan people's transit cards in the app to check how much credit they have left on their transit card. Most people have set their transit cards on express mode (no need for biometric authentication). My question is, using the NFC & SE Platform entitlement, can developers read transit cards without it requiring user authentication? Or does the user need to unlock their phone before scanning, even if it is set to express mode?
Topic: App & System Services SubTopic: Wallet Tags:
Replies
Boosts
Views
Activity
Apr ’25
Reply to Can an iPhone be used as an NFC terminal to read Apple Wallet passes from another iPhone?
It is technically possible. But like you surmised it is restricted due to Secure Element isolation. Basic CoreNFC APIs do not support identity or payment related AIDs. But there is a new NFC & SE Platform for secure contactless transactions Information here: NFC & SE Platform for secure contactless transactions Before investing time and resources, first you should examine the Requirements and availability section to make sure these are available for use in your or your client's region, and your use case and company specifics are suitable. If it is, then you can follow the instructions at that document to apply for access to the API. Any information not clarified/present at this link will be provided once you request access and sign a confidentiality agreement. Details are in the Requesting access to the NFC & SE Platform section. Technically, you will be using the CredentialSession APIs We cannot answer whether this API would be suitable for your specific use case. You w
Topic: App & System Services SubTopic: Wallet Tags:
Replies
Boosts
Views
Activity
Apr ’25
Can an iPhone be used as an NFC terminal to read Apple Wallet passes from another iPhone?
Hi all, I'm working on a use case where a customer checks in at a point of service (e.g., a cafeteria or restaurant) using their Apple Wallet pass (e.g., a digital employee badge). In this scenario, we would like to use an iPhone (with a custom iOS app) as the NFC terminal to read the pass directly from the customer's iPhone over NFC. I’m aware that Tap to Pay on iPhone allows NFC-based payment acceptance, but it’s unclear if similar functionality is available or permitted for reading access-type passes from another iPhone via NFC. Key questions: Is it technically possible for an iPhone to act as an NFC reader for a Wallet pass on another iPhone? If not, is this restricted due to Secure Element isolation or protocol limitations? Is there any Apple-supported path for building such a solution — or is certified external hardware (e.g., HID, Wavelynx) the only option? I’ve reviewed the Core NFC and PassKit documentation but couldn't find a definitive answer. T
Replies
3
Boosts
0
Views
911
Activity
Apr ’25
我的app应用上传到testflight之后,无法通过NFC方式唤醒App Clips
为什么App 上传testFlight之后。无法通过NFC的方式唤醒 APP Clips。是必须要上架商店之后才能支持么?
Replies
0
Boosts
0
Views
205
Activity
Mar ’25
Reply to Why my app clips is Unavailable
In the Diagnostics section of the Settings app, the NFC domain shows a warning: “The URL does not match the associated domains for this App Clip.” However, I have verified that my AASA configuration is correct, and the cached AASA file on https://app-site-association.cdn-apple.com/ is also correct.
Topic: UI Frameworks SubTopic: General Tags:
Replies
Boosts
Views
Activity
Mar ’25
Reply to Passkeys authenticatorAttachment and transports in macOS 14.4 and iOS 17.4
As of Safari 18.3 (macOS, iOS, iPadOS), authenticatorAttachment still set to platform instead of cross-platform when registering a credential using a security key (usb/nfc transport) or mobile phone (hybrid transport).
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Mar ’25
Get NFC Data Identity card
Hello, I have to create an app in Swift that it scan NFC Identity card. It extract data and convert it to human readable data. I do it with below code import CoreNFC class NFCIdentityCardReader: NSObject , NFCTagReaderSessionDelegate { func tagReaderSessionDidBecomeActive(_ session: NFCTagReaderSession) { print((session.description)) } func tagReaderSession(_ session: NFCTagReaderSession, didInvalidateWithError error: any Error) { print(NFC Error: (error.localizedDescription)) } var session: NFCTagReaderSession? func beginScanning() { guard NFCTagReaderSession.readingAvailable else { print(NFC is not supported on this device) return } session = NFCTagReaderSession(pollingOption: .iso14443, delegate: self, queue: nil) session?.alertMessage = Hold your NFC identity card near the device. session?.begin() } func tagReaderSession(_ session: NFCTagReaderSession, didDetect tags: [NFCTag]) { guard let tag = tags.first else { session.invalidate(errorMessage: No tag detected) return
Replies
0
Boosts
0
Views
370
Activity
Mar ’25
JPEG2000 (JP2) Decoding Works on iOS 16 but Fails on iOS 18
I am extracting a JPEG2000 (JP2) facial image from an NFC passport chip (ISO/IEC 19794-5) and attempting to create a UIImage from it. On iOS 16, the following code works fine: import ImageIO import UIKit func getUIImage(from imageData: [UInt8]) -> UIImage? { let data = Data(imageData) guard let imageSource = CGImageSourceCreateWithData(data as CFData, nil), let cgImage = CGImageSourceCreateImageAtIndex(imageSource, 0, nil) else { print(Failed to decode JP2 image!) return nil } return UIImage(cgImage: cgImage) } However, on iOS 18, this fails with errors like: initialize:1415: *** invalid JPEG2000 file *** makeImagePlus:3752: *** ERROR: 'JP2 ' - failed to create image [-50] CGImageSourceCreateImageAtIndex: *** ERROR: failed to create image [-59] Questions: Did Apple remove or modify JPEG2000 support in iOS 18? Is there an official workaround for decoding JPEG2000 on iOS 18? Should I use Vision/Metal/Core Image instead? Is there a recommended way to convert JPEG2000 to JPEG/PNG before creating a UII
Replies
3
Boosts
0
Views
617
Activity
Mar ’25
Reply to HCE AID application coupling
At this time there isn't a facility to launch specific apps for specific AIDs. It's an all or none situation. But I am sure the NFC team would love to hear your thoughts in detail about this for a possible future enhancement. The typical way to make such enhancement requests would be via the Feedback Assistant.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Mar ’25
Reply to HCE AID application coupling
Thank you for your swift answer. FYI: Our app is for attendance registration, not payment. I do expect our app to be launched automatically when the phone emulating a card (HCE) has received an AID that is registered to that app. (I need to register it when compiling the app in xcode) I understand that the choice of the default contactless app is the users. But that directs all nfc transactions to this default app, right? So how can multiple apps (or wallets) for different purposes be installed on a iPhone, and still work together? If I ask the user to make our app the default one, how can the others still work? It means that doing attendance registration with our app, would make the phone not unusable for other functions, like payments. Is there a way to coexist?
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Mar ’25
Reply to HCE AID application coupling
Are you expecting your app to be launched automatically when near a reader? Then your app will need to become the default payment app. There is no API to set the default payment app. This can only done by the user through the Settings app. Once you have successfully built and installed your app, properly configured with the necessary entitlements, the users should be seeing the option to make that app the default app in Settings->General->Contactless & NFC For this setting option to show up (or for any any of the EEA based features to work) Your app must be correctly configured and built with the correct entitlements and the necessary APIs Your testing device must physically be located in the EEA and is a supported type (iPhone only). The signed-in Apple ID on the device must be registered in an EEA country or region. You will need to contact the entitlements team and ask for the HCE Default App entitlement. Keep in mind that this functionality can only be tested within the EEA. As for the
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Mar ’25
Does iPhone Xr and up support ISO 14443 Type B Tags
I am unable to get an iPhone Xr (iOS 18) or iPhone 15 to interact with Texas Instruments RF430CL330H NFC tag. This is an ISO 14443B-compliant tag supporting NDEF. It is NFC Tag Type 4. A Samsung S23 with Android 14 and NFC Tools v8.11 reads and writes NDEF data with this tag as expected. The iPhones with NFC Tools v2.31 do not. For the following comparison the NDEF memory is written with a pre-loaded text data record. NFC Tools on Android reports the following: Tag Type: ISO 14443-4 Technologies Available: IsoDep, NfcB, Ndef Serial Number: Format: NFC Forum Type 4 Text Record 1: UTF-8 (en) Hello World! NFC Tools on iOS (iPhones) reports the following: Tag Type: ISO 7816 Technologies Available: Unknown Serial Number: Format: Text Record 1: Error response: This nfc tag is not supported Attempting to write a text message with NFC Tools on the iPhones returns An error occurred during writing process Other NDEF records (URL and Sear
Replies
2
Boosts
0
Views
589
Activity
Mar ’25
Reply to Error "The operation couldn't be completed. (CPSErrorDomain error 2.)" in AppClip sheet
Adding +1 that our App Clip has seen CPSErrorDomain error 2 reported by customers on and off during the last week when invoked by an NFC tag scan. (We haven't released an app update in months.) I haven't been able to reproduce this locally on one of our test phones, so no sysdiagnose to submit, but I will keep trying. For most customers, the App Clip is working. But we're inconsistently seeing these other two behaviors: The customer is taken to our website in Safari instead of displaying the App Clip. The App Clip appears, broken, as seen in the attached photo with CPSErrorDomain error 2.
Topic: UI Frameworks SubTopic: General Tags:
Replies
Boosts
Views
Activity
Mar ’25
Error "The operation couldn't be completed. (CPSErrorDomain error 2.)" in AppClip sheet
A few days ago scanning NFC tags or QR codes for AppClips with advanced experiences started showing the error The operation couldn't be completed. (CPSErrorDomain error 2.) in the AppClip sheet as seen here: We are providing AppClips to our customers and they trust AppClips to always work, since it is a big part of their business. Since this is happening at our customers phones and on the phones of their customers, I don't have a sysdiagnose. I already created a feedback entry about this FB16601674. We checked everything, our AASA file, the Appstore Experiences.
Replies
8
Boosts
0
Views
866
Activity
Feb ’25
Reply to NFC Communication Issues on iPhone 12–15 with NXP NTAG 5 (ISO15693 Pass-Through Mode)
As you are observing different behaviors on different iPhone models, this is best looked at by our NFC team. Filing a Feedback report with some logging will be the best way for us to investigate the issue further. First, please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Wallet for iOS to install a logging profile on your device. Once that is installed, then reproduce the issue. Once reproduced, then follow the instructions at the above link to create a sysdiagnose Then use the Feedback Assistant. to create a report and include a detailed description of the issue, details of the tags/devices you are using, and the sysdiagnose from the above step. Also include the following info: What is the setup on the device. Including apple wallet settings Please provide sample app if you have one, or can create one Video capture of the failure scenario so we can confirm the positioning of the NFC antenna the Bundle ID of the app you have tested this
Topic: App & System Services SubTopic: Drivers Tags:
Replies
Boosts
Views
Activity
Feb ’25