Search results for

nfc

1,175 results found

Post

Replies

Boosts

Views

Activity

CardSession.Error doubts
Hi, I am dealing with CardSession.Error (https://developer.apple.com/documentation/corenfc/cardsession/error) and I have some doubts to force some of them. radiodisabled --> I do not know how reproduce this error. I thought it happen on flight mode but it is does not. Until I know you cannot disable de NFC on iPhone. How can I reproduce? transmissionerror --> I guess it happens when somethings is wrong during the apdu respond. But I have never got, how can it force? emulationStopped --> I try to force by code with stopemulation(status:) but I have not got this error. How I can get it? Which is the difference between accessnotaccepted and systemeligibilityfailed? I think both of them are happening when the user decline the permissions, right? I hope you can help me to solve these doubts. Thank you in advance. Best regards.
1
0
90
Apr ’25
Any NFC readers with VAS protocol?
Hi all, I am working on a small project with a deadline coming soon, which involves using an NFC digital pass in Apple Wallet. I have recently stumbled upon that in order to read NFC passes, I must use an NFC device that has compatible NFC terminals, [where] Apple uses the Apple Value Added Services (Apple VAS) protocol. I tried to find some NFC terminals online but I couldn't find any that would just read the decrypt and output NFC payload. Are there any NFC terminals anyone can suggest that would be inexpensive and supportd Apple VAS to read NFC passes from Apple Wallet?
4
0
2.7k
Apr ’23
Reply to Can an iPhone be used as an NFC terminal to read Apple Wallet passes from another iPhone?
@kocaatli in old versions of iOS it was possible to negotiate a session with an Apple Wallet pass if it was manually selected: https://youtu.be/FKwzPYBX4aY @swakitaki it is possible to read transit cards without authentication. It depends on the issuer's implementation but here's an example: https://github.com/kormax/apple-device-as-access-card The NFC @ SE Platform entitlement is for creating a credential that would be served by an application different from Apple Wallet, as I understand it. If you want to offer an iOS app for train conductors to scan people's transit cards and managing the issuance of these cards, your best bet is to use an external reader like so: https://youtube.com/shorts/csC_rloFr90
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
461
Apr ’25
NFCTagReaderSession - Missing required entitlement
Hi there, I am using Core NFC and I established the connection with the card, (it means that the info.plist is correct and the entitlement should be correct as well). The app detects the card, but after sending the command 'tag.sendCommand()' I receive this message: [CoreNFC] -[NFCTagReaderSession transceive:tagUpdate:error:]:879 Error Domain=NFCError Code=2 Missing required entitlement UserInfo={NSLocalizedDescription=Missing required entitlement} So, what is missing or what am I doing wrong? Here is the code: func tagReaderSession(_ session: NFCTagReaderSession, didDetect tags: [NFCTag]) { guard !tags.isEmpty else { return } let hexString = //... if case let .iso7816(tag) = tags[0] { session.connect(to: tags[0]) { error in if let error = error { print(Error: (error.localizedDescription)) return } let apdu = hexString.convertToAPDU() tag.sendCommand(apdu: apdu) { (response: Data, sw1: UInt8, sw2: UInt8, error: Error?) in // -> here is when the error appears, in the completion print([UInt8](respon
6
0
2.4k
Jun ’24
Apple Wallet VAS & NFC Entitlement for Approved Product Plan
So we are developing an NFC reader for a client and one of the requirements was Apple ECP. We submitted a product plan and it was approved and we were given access to the specific documentation for ECP. We are looking to only use Loyalty passes via NFC. Not Apple Pay. We wish to develop passes that have NFC capability and apparently you need another approval for NFC Entitlement. Apple just denied our application. No reason given, just denied. How are we suppose to develop a solution when we can only do one side of the development? Also we are seeing VAS mentioned and believe we also need access to this documentation as well, but no idea where to request it. Nothing in our developer portal or wpc portal. Can someone from Apple please steer us in the right direction. As we understand it we need: Approved hardware product plan (which we have) Access to ECP 2.0 documentation (which we have) Access to VAS protocol documentation (we don't have) NFC entitlement to be able
3
0
1k
Feb ’25
Reply to HCE AID application coupling
The current iOS implementation of HCE interoperability (EEA only), with regard to ISO 7816-4 protocol communication, presents significant challenges. When using the CardSession functionality to interact with NFC readers, an application can be configured to listen for a SELECT command using an Application Identifier (AID) as specified by ISO 7816-5. However, the SELECT command is not always honored by the system. Currently, users are required to either switch between default contactless apps to allow the SELECT command to reach the intended application or manually open the app and initiate a presentmentIntent. While the presentmentIntent itself is not a workaround, its use for directing NFC commands in this manner is. This approach prevents the default contactless app from interfering and ensures that the user’s app is selected. However, this is not consistent with the ISO 7816 standard, which specifies that an application must be directly selectable by its AID, if its AID is known. This is a
Topic: App & System Services SubTopic: Core OS Tags:
Apr ’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:
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
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
How to use NFC and suppress Apple Pay?
Hello, I need to use NFC for a project. My problem is that always when im entering with my Phone a RFID field Apple Pay shows up instead of just my NFC application. I know that you can suppress Apple Pay with adding com.apple.developer.passkit.pass-presentation-suppression to the Entitlements File but my Problem is that this Entitlement also suppresses NFC which I need. How can I suppress Apple Pay but use NFC? Thanks for Help!
1
0
871
May ’22
Passkeys authenticatorAttachment and transports in macOS 14.4 and iOS 17.4
In the new macOS and iOS updates (14.4 and 17.4 respectively), something has changed in regards to passkey creation: Any passkey created from Safari doesn't have any transports + the authenticatorAttachment is always set to platform, irrespective of whether a cross-platform authentication method is utilized, such as a hardware security key. All passkeys saved in iCloud Keychain created from any browser have an authenticatorAttachment always set to platform + empty authenticator transports. authenticatorAttachment always set to platform According to the WebAuthn specification (Section 5.4.5), the authenticatorAttachment descriptor plays a crucial role in guiding the client (browser or platform) to create or use an authenticator of a specific type. The options are platform for a built-in authenticator or cross-platform for a roaming authenticator. Some relying parties mandate a cross-platform method for the first passkey or as second authentication factor. This is to ensure users do not find themselves locked o
3
0
1.3k
Apr ’24
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
415
Mar ’25