nfc

Good morning, I hope to find someone who knows better than me regarding reading NFC tags I'll explain what happens: if I read my card [iso 7816 nfc card with fingerprint reader] everything is fine. If I bring another card near it, for example the Italian tax code, it reads OK (so in the UI it says that it has been read) in the usual entitlement error log I honestly would prefer it to show the error: self.nfcSession?.invalidate(errorMessage: Not a WiBioCard Otp Card) while I have precisely in the UI that everything went well.

Dear Apple Developer Support, I hope this email finds you well. I am writing to seek your assistance regarding an advanced NFC functionality we aim to implement in our existing iOS application. Our application provides a mobile access solution for businesses, eliminating the need for traditional key fobs by enabling door access via smartphones. We are currently working on a feature to unlock doors using NFC tags. The NFC tags will contain specific information for each lock, and users will unlock the door by tapping their iPhone to the tag. To enhance the user experience, we aim to: Bypass the NFC prompt that requires user interaction to confirm the NFC read. Unlock the door without needing to open the app. Our goal is to provide a completely touchless and seamless access experience for our users. However, we understand that there are certain security and privacy constraints in place. We are looking for guidance on: Any potential solutions or workarounds that would

Issue: Amtrak's state partner in New Jersey, SEPTA, has requested the incorporation of NFC suppression when an Amtrak mobile ticket is opened on their app. This feature ensures that NFC remains inactive and does not inadvertently bring up Apple Pay, Google Pay, etc., when customers are trying to scan their Amtrak tickets on SEPTA validators. Request: Amtrak is requesting to use the entitlement com.apple.developer.passkit.pass-presentation-suppression in our Amtrak app to suppress the display of Apple Pay passes when the app is in use. This is to prevent interference with the NFC reader during ticket validation, as illustrated in the attached screenshot from SEPTA's app, which shows a similar implementation with the message: Payment cards and passes will not work automatically while NJ TRANSIT is in use. Entitlement Information: Entitlement Key: com.apple.developer.passkit.pass-presentation-suppression Boolean Value: YES Justification: The entitlement will enable the requestAutomatic

use NFC api has some error: 2024-07-15 15:42:59.633782+0800 TestNFC[16022:1038141] tagReaderSessionDidBecomeActive 2024-07-15 15:43:03.608427+0800 TestNFC[16022:1038141] [xpc.exceptions] connection to service with pid 58 named com.apple.nfcd.service.corenfc: Exception caught during decoding of received selector didDetectExternalReaderWithNotification:, dropping incoming message. Exception: Exception while decoding argument 0 (#2 of invocation): Exception: decodeObjectForKey: class NFFieldNotification not loaded or does not exist how can I fix it ? thanks

I am using NFC when the phone is near the NFC reader times below the error： 2024-07-15 15:43:03.608427+0800 TestNFC[16022:1038141] [xpc.exceptions] connection to service with pid 58 named com.apple.nfcd.service.corenfc: Exception caught during decoding of received selector didDetectExternalReaderWithNotification:, dropping incoming message. Exception: Exception while decoding argument 0 (#2 of invocation): Exception: decodeObjectForKey: class NFFieldNotification not loaded or does not exist my code: #import @interface ViewController () @property (strong, nonatomic) NFCTagReaderSession *session; @end @implementation ViewController - (void)viewDidLoad { [super viewDidLoad]; // Do any additional setup after loading the view. self.view.backgroundColor = [UIColor whiteColor]; if (@available(iOS 13.0, *)) { // 初始化 NFC 设置代理 NFCTagReaderSessionDelegate if (NFCNDEFReaderSession.readingAvailable) { self.session = [[NFCTagReaderSession alloc] initWithPollingOption:NFCPollingISO14443 delegate

I used NFC in my app, but When I iphone near the NFC device times the following error： 2024-07-15 14:10:24.882616+0800 TestNFC[1239:40733] [xpc.exceptions] connection to service with pid 58 named com.apple.nfcd.service.corenfc: Exception caught during decoding of received selector didDetectExternalReaderWithNotification:, dropping incoming message. Exception: Exception while decoding argument 0 (#2 of invocation): Exception: decodeObjectForKey: class NFFieldNotification not loaded or does not exist my code is : @interface ViewController () @property (strong, nonatomic) NFCTagReaderSession *session; @end @implementation ViewController - (void)viewDidLoad { [super viewDidLoad]; // Do any additional setup after loading the view. self.view.backgroundColor = [UIColor whiteColor]; if (@available(iOS 13.0, *)) { // 初始化 NFC 设置代理 NFCTagReaderSessionDelegate if (NFCNDEFReaderSession.readingAvailable) { self.session = [[NFCTagReaderSession alloc] initWithPollingOption:NFCPollingISO14443 deleg

Hi: I saw the post WWDC WebKit release notes said Safari will support largeblob extension from version 17. But when I create a credential with largeblob extension, different action takes according what authenticator used. The credential options is: credCreateOptions: { rp: { name: WebAuthn demo, id: webauthn.turinggear.com }, user: { name: Jonathon.Runte97@gmail.com, displayName: Jonathon.Runte97@gmail.com, id: bqShD9YGRicjM-1foXiBqrdCzTHTuG1bkmKaxzn7oEM }, challenge: 9BP4y2epk2b3MhRCRRS5tt4bdWYLPJcKBLMMiB_7p7E, pubKeyCredParams: [ { alg: -7, type: public-key }, { alg: -257, type: public-key } ], excludeCredentials: [], authenticatorSelection: { requireResidentKey: true, residentKey: required, userVerification: discouraged }, attestation: none, extensions: { credProps: true, largeBlob: { support: preferred } } } When i choose use iPhone be my authenticator, it seems that largeblob act as it should be: credential : { id: ZRxBdH4LKE4eiVxbwcA4Kmn9VZk, rawId: ZRxBdH4LKE4eiVxbwcA4Kmn9VZk, response: { attestationOb

We want to use HCE or Wallet to use the iPhone on NFC readers that start EV chargers. They use the same tech as transit systems (MiFare and ISO 14443-4), but the backend systems only use the NFC UID for verification. Is it possible to use HCE (CardSession) or Wallet (Transit card) to transmit a static UID? If so, could our use-case go under either In-store purchase, loyalty programme, or transit? Or are those categories very rigid as to their use case? The new EEU regulation seems to open up this a bit.

I am developing an APP, scan and read NFC Tag information. I can only get the message in the NFC tag, but I cannot get the chip information. Or rather, the information obtained is incomplete. Look at the code: NFCNDEFReaderSession *session; - (void)readerSession:(NFCNDEFReaderSession *)session didDetectTags:(NSArray<__kindof id> *)tags API_AVAILABLE(ios(13.0)) API_UNAVAILABLE(watchos, macos, tvos) { NSLog(@call back ios13); if (tags.count > 1) { session.alertMessage = LocalizedString(@ErrorTips4); [session restartPolling]; return; } id firstTag = tags.firstObject; HBNFCNDEFTag *ndefTag = firstTag; NSLog(@ndefTag == %@, [ndefTag valueForKey:@_tag]); dispatch_async(dispatch_get_main_queue(), ^{ [self invalidateSession]; }); } Obtain datas: ndefTag == -BA5A89060AA01FAB { Tech=Unknown Type=Unknown ID=(null), NDEF=4, capacity=137, messageSize=45 } An Other: NFCTagReaderSession *tagSession; - (void)tagReaderSession:(NFCTagReaderSession *)session didDetectTags:(NSArray<__kindof id> *

I have followed the SoupChef example in migrating Custom Intents from SiriKit to AppIntents. However, we only require one iOS release back, so we can require iOS 17. Thus, I eliminated everything that was strictly for backwards compatibility, most notably the SiriKit Extension that required enormous amounts of code to try to coordinate with the real app which worked poorly anyway. I tested for example that an NFC tag Automation created in Shortcuts works to execute an AppIntent while the app is backgrounded. I am now receiving a beta report that indicates someone trying to execute one of our migrated AppIntents from their HomePod is not working, and they say it used to work sometimes (not all the time). I'm sure most such cases used to require the SiriKit Extension in the old SiriKit world. I am terrified that I may need to rebuild that monster once again when the new (to me) AppIntent API seemed so beautiful without it and seemed to work without it. The AppIntent API documentation seems to indicate

I have a client who asked me to create an app that reads nfc data, but this data needs to come from a built in iPhone nfc tag, so the app will read through nfc the SECOND device info. my question is, does the iPhone has a built in nfc tag? if so, can it share any device info?

We are developing an app for the online identification function of the German National ID Card. https://github.com/Governikus/AusweisApp https://apps.apple.com/de/app/ausweisapp-bund/id948660805 Currently there are two NFC timeouts we are not able to influence because there is no API. A NFC Session has a maximum lifetime of 60 seconds, independent from any card communication. When a card was detected the connection will only last for 20 seconds. Combined there is also something like a worst case: The user presents the card 55 seconds after the session was started: The connection will only last for the remaining 5 seconds of the session. The identifications works as follow: The user clicks on a link on a website and our app will appear. After selecting access rights the NFC session is started. Sometimes the user start to search for their ID card now and this takes some time. When the 60 seconds are over we start a new session until there is a card or the user aborts. After establishi