How does Core NFC support ISO 7816? ISO 7816 is for contact smart cards. Is Apple adding smart card readers to devices? If not, how is it possible for Core NFC to support ISO 7816?
Search results for
nfc
1,175 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Is anyone else no longer able to trigger Shortcuts automations on iOS 13 beta 4? They were working for me before the upgrade and now, although I can create a new automation and the tag scans without a problem, I'm no longer able to trigger them by scanning the tag after they've been created.
Same here. I am furious. I am developing a project where I need the personal automations and the NFC feature. We are now unemployed for how long? I don't know. Thanks Apple. Good job!
Topic:
App & System Services
SubTopic:
Core OS
Tags:
This sample code project is associated with WWDC 2019 session 715: Core NFC Enhancements.but with deprecated warning NFCNDEFPayload.wellKnowTypeTextPayload in iOS 13.0 beta 4CreatingNFCTagsFromYourIPhone/FishTagCreator/MainViewController.swift:90:42: 'wellKnowTypeTextPayload(string:locale:)' was deprecated in iOS 13.0Any idea to fix?
Yes, I just verified. It's in the 2019 Core NFC Enhancements video at time point 9:00.However, for the time being, reading payment cards will not be supported.Presumably they want to encourage Apple Pay as the only kind of payment handling the phone engages in.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Hi d.Knowles,Yes I do have the latest (beta 5 build 17A5547d), and XCode 11.0 beta 3. When do you get the error ? At the start of the session or when you actually call the customcommand function?If you are getting the error before the end of tag connection, you should check again your App profile, capabilities, .plist and .entitlements file and that you ar embedding the corenfc.framework library ... ( see Core NFC Enhancements - WWDC 2019 - Videos - Apple Developer )If the connection goes well but you still get the error on customcommand, the problem should be solved with installing beta 4 or later and I did actually get the confirmation from the 'Feedback Assitant'.I just needed the customcommand function as I am using the NFCISO15693Tag to communicate with and ST25DV Tag. I have not tested the other functions.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
The NXP app for Android can read MiFare DESFire EV1 tags, so I figured there must be a way to do similar in an app on iOS13. However, it appears I must know in advance the ISO7816 AID to populate the select-identifiers property of my app's Info.plist before I will get tags from the reader session. I believe my code is correct to setup the reader session and begin. But I my didDetect callback never fires. Is there some sort of wildcard select-identifier that would present all tags to my callback?
Not able to read data from the NFC tag using SendCommand . the entitlements and info.plist values are in place.I am able to create a session and connect to the tag.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
We have been successfully writing to NFC tags using Beta 13, but have no luck with trying to lock them using the writeLock() function. After execution we get back a result of nil but it is definitely not locking. Any clues or has anyone managed to get this work as yet?Code is extremley straight forward (but might have done something stupid!) - Trying on different variations of a NXP NTAG213 tag:if (self.lockTag) { // locking required also os_log(Tag needs to be locked) tag.writeLock() { (error: Error?) in if error != nil { os_log(LOCK FAILED!!) session.alertMessage = Lock failed try again session.invalidate() } else { session.alertMessage = Write and Lock successful session.invalidate() } } } else { // only writing os_log(Tag is unlocked) session.alertMessage = Write successful! session.invalidate() }
I'm running iOS 13 beta 6 on a newly purchased iPad Pro 11. This device appears to have the same NFC chipset as the iPhone XS. I downloaded the NFC Tag-Reader example (https://developer.apple.com/documentation/corenfc/building_an_nfc_tag-reader_app) to test the NDEF reading capability. The app built but when I went to deploy I got this error message:Unable to install “NFCTagReader”Domain: com.apple.platform.iphoneosCode: -1Recovery Suggestion: “NFCTagReader” requires the “nfc” capability which is not supported by iPadProNot sure if this is an oversight or something that will be changed in the future. Obviously the hardware is there. Can we not use iPad Pros for NFC support? I have a client project where they'd like to use tablets at workstations to read NFC tags.Also would like to use CoreNFC on WatchOS 6 on a series 4 watch. Haven't gotten there yet, but would be good to know the level of support there.-Thanks
Yes! Same issue here (Xcode 11 Beta 5, iOS 13 Beta 7, iPhone XR). It took me forever to figure out it was ObservedObject that was causing the crash. Ended up creaing a virtually blank Xcode project to replicate and sure enough adding any ObservedObject to a SwiftUI view causes a crash every time on a real device. I'm working with NFC, so I need to use an actual device rather than the simulator, but obviously have hit a wall.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
How do you get the dump ?Could you get the dump for Mifare Ultralight and compare ?Did you ask NXP if there is something special in Mifare Plus that could explain ?In particular, here it says:No NDEF data storage present:Is it the same on Ultralight ?I read thish ttps://atadistance.net/2018/11/07/ios-12-apple-pay-wallet-pulled-a-mifare-on-us-and-nobody-noticed/It is not clear if Apple NFC supports all Mifare variationshttps://stackoverflow.com/questions/44429828/it-is-possible-to-read-protected-nfc-tags-in-iosThey note that:Core NFC only works with NFC tag that are NDEF formatted. Thus, you can only interact with NFC tags that adhere to the NDEF (NFC Data Exchange Format) hardware abstraction layer specified by the NFC Forum. Specifically, with NFC Forum tag types 1 to 5.Core NFC overview page:Reading NFC NDEF tags is supported on iPhone 7 and iPhone 7 Plus.Using Core NFC, you can read Near Field Communication (
Topic:
App & System Services
SubTopic:
Drivers
Tags:
nNo NFC support on iPad or watchOS.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Is there any guidance how to customize scan dialog (Ready to Scan) which is launched by NFCTagReaderSession? E.g. size, color, icon or is it limited by operating system?
I keep getting, ⚠ The message contains invalid characters so editing to add one line at a time...FINISHED! It didn't like the word, m a r r i a g e?! What the... ? WOW! 😠- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -I had installed iOS 13 beta a few weeks ago but have since reverted back to 12. I seem to recall asking about this somewhere, but not sure if it was in this forum or not. Since most people use their iPhones to schedule morning alarms, not just notifications, and Homekit knows all about our devices, it seems having more hooks between the iPhone Clock and Homekit would be advantageous.Some of the things I'd like to be able to do with iPhone alarms and Homekit follow:iPhone alarm triggers a Homekit event or sets a Homekit device state:I go to sleep at a different time almost every night, between say, 10pm & 5am. I try to sleep at least 6 hours and set my iPhone alarm when I get into bed, usually by saying, Hey Siri, wake me up in 6 hours. I woul