I'm trying to use iOS 13's new CoreNFC capabilities to readwrite data to an ISO15693 compatible chip. My app includes the NFC Tag Reader Session Formats Entitlements:<key>com.apple.developer.nfc.readersession.formats</key> <array> <string>NDEF</string> <string>TAG</string> </array>The NFCTagReaderSessionDelegate receives an object that conforms the NFCISO15693Tag protocol and I have been successfully called readSingleBlock function to read dtat from the Tag. But whenever I call customCommand to send a proprietary command for reading data from the Tag, I get the following error: Error Domain=NFCError Code=2 Missing required entitlement UserInfo={NSLocalizedDescription=Missing required entitlement}.Does anyone has managed to get this work? What are the missing entitlements needed to use customCommand function?
Search results for
nfc
1,175 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I seem to be seeing the same behaviour. I have both an ePassport and generic transport AID configured in Info.plist. I can successfully detect an ePassport, but the transport card results in nfcd crashing.0x8344 default 14:48:35.662570 +0100 SharingViewService NFCTagReaderViewController: Interrupted0x8344 default 14:48:35.663573 +0100 SharingViewService XPC interrupted0x8344 default 14:48:35.663794 +0100 SharingViewService dismissIfIdle: is idle0xe6e2 default 14:48:35.717530 +0100 nfc-prototype tagReaderSession.didInvalidateWithError Session invalidated unexpectedly0xe861 default 14:48:35.747840 +0100 runningboardd XPC connection invalidated: [daemon<com.apple.nfcd>:563]0xe8a1 default 14:48:35.750553 +0100 ReportCrash cr_update: Parsing corpse data for process nfcd [pid 563]0xe804 default 14:48:35.765041 +0100 runningboardd [daemon<com.apple.nfcd>:563] Death sentinel fired!0xe67f default 14:48:35.780511 +0100 passd 00000001 0371cc50 -[NFHardwareManager didInterruptXPCConnection:]:208 Conn
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Hi,I am trying to use the new `NFCVASReaderSession` API on iOS 13 beta using an iPhone XR.NFCVASReaderSession.readingAvailable is returning false, but when I call session.begin() it launches the scan UI.A couple of questions:Is there additional entitlements needed for NFCVASReaderSession to work?? Or should these work (https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_developer_nfc_readersession_formats).I have NFC enabled Apple Wallet VAS passes and have configured the NFCVASReaderSession to target the correct `passTypeIdentifier` but to no avail. Is this supposed to work with NFC enabled Apple Wallet passes?Thanks,Scott
Issue fixed by updating Apple Program Dev License !!! From now, full NFC Tag Reading capabilities are available into my iOS Dev profile !!!
Topic:
App & System Services
SubTopic:
Core OS
Tags:
We are testing NFC tags to send visitors to a special landing page. The tag (its a card) asks an iPhone XR if it would like to open the subject URL, but on an iPhone 8 it opens Apple Pay (you see your linked card appear)? Does anyone know why the result is different for these two phones and why the 8 thinks you are trying to buy with Apple Pay, instead of taking the user to our landing page URL?
Is the new iPod Touch support the NFC Read/write ? I want to test the NFC read / write in a real device.
In the WWDC 2019 Video on NFC enhancement , he said “iPhone 7 or future phones”. No mention of iPod Touch or iPad devices.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I discovered the answer, my iPhone 8 requires an app to read NFC, otherwise it goes to Apple Wallet. My iPhone XR reads the code without an app and asks if I'd like to open the coded URL:iPhone Xs, iPhone Xs Max and iPhone XR include a new feature for NFC that Apple didn’t mention on stage. The new models will be able to scan NFC tags in the background. With current iPhones, users must first launch an app to enable NFC Reader mode.more on this:There are some constraints to this system. Any NDEF tag is supported that ends with a URL that is registered with Apple’s Universal Link system. Background tag reading happens whilst the iPhone display is on (either on lock screen or home screen).Background tag reading requires the device to have been unlocked at least once since it has been rebooted. It also is disabled if Apple Pay Wallet session is active, if Airplane mode is enabled, or if the camera is on.quotes source: https://9to5mac.com/2018/09/12/iphone-xs-and-iphone-xr-can-r
Topic:
Developer Tools & Services
SubTopic:
Developer Forums
Tags:
My colleague and I ran both Apple's and AndyQ's examples on an iPhone XR but it won't read anything – we tried passports, ID cards and credit cards. We have enabled the NFC entitlement, added it in the app, added all the tags suggested above in the info.plist – but nothing changes, even though `readingAvailable` returns `true`. We are using Xcode 11 beta 2. Any clue what we are missing?
Topic:
App & System Services
SubTopic:
Core OS
Tags:
We're trying to communicate with Tangem cards (https://tangem.com) that contains ISO7816 Tag via NFC.We open session:readerSession = NFCTagReaderSession(pollingOption: [.iso14443], delegate: self, queue: nil)readerSession?.begin()Bring our card to iPhone NFC Reader and connect to a tagsession.connect(to: tags.first!)and start sending APDU commands one by one.But after about 20 seconds CoreNFC session sends us the error:Error Domain=NFCErrorCode=100 Tag connection lostUserInfo={NSLocalizedDescription=Tag connection lost}or, if there was no active command at that moment:Error Domain=NFCErrorCode=201 Session timeoutUserInfo={NSLocalizedDescription=Session timeout}We have to send plenty of commands within one session. It is needed to secure Tangem clients from malefactors that can read data without user's knowledge and approval. Session with the card can last more than 30 seconds. And we can't invalidate session and start another one, because after it we have to start sending commands from the very begin
I know there were screenshots of an NFC option for personal automation, but I don't see it in the public beta. Is it working for anyone else, or did the mention that it's not ready yet?
I talked no many developers who are interested in getting ceritficate. Some are even NFC hardware vendor. They have same trouble getting ceritificate from Apple. I feel Apple should be more transparent about the process for getting the ceritifcate. ex: what's the requirmenet or at least reply to develoeper's request when they are requesting certitifcate. Right now, developer.apple.com/wallet is like a blackhole. I was hoping there are more information released in wwdc 2019, but unfortunately there was nothing.
Topic:
App & System Services
SubTopic:
Apple Pay
Tags:
Just checked the beta 3: same error message!It is indeed very frustrating... NFC has long been held back by Apple not supporting it, but now with iOS 13 and the latest announcements we are eager to see this up and running.I have also reported this error to the feedback center and I am waiting for a response.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I was curious about this too.So far what I've found is that the 2018 iPad Pro 11 models (circa 2018) do have an NXP 100VB27 NFC controller (via iFixit: https://www.ifixit.com/Teardown/iPad+Pro+11-Inch+Teardown/115457).In theory, with IOS 13 they should be able to support CoreNFC's new features.
Topic:
App & System Services
SubTopic:
Apple Pay
Tags:
Does iOS 13 support ISO 14443 considering all of the enhancements to Core NFC? Thank you.Very Respectfully,Michael Ross