Post not yet marked as solved
I have implemented NFC card reading functionality using NFCTagReaderSession. After starting the NFC reader session in landscape mode at least once, if I switch back to portrait mode and attempt to start the NFC reader session again, the scanning sheet does not respond to any touch interactions. Regardless of whether the screen is rotated, I expect the user to be able to close the reading screen, but it remains open. Is there any workaround for this issue? Code: class ViewController: UIViewController, NFCTagReaderSessionDelegate { func tagReaderSessionDidBecomeActive(_ session: NFCTagReaderSession) { } func tagReaderSession(_ session: NFCTagReaderSession, didInvalidateWithError error: any Error) { } func tagReaderSession(_ session: NFCTagReaderSession, didDetect tags: [NFCTag]) { } override func viewWillTransition(to size: CGSize, with coordinator: any UIViewControllerTransitionCoordinator) { super.viewWillTransition(to: size, with: coordinator) let session = NFCTagReaderSession(poll
Post not yet marked as solved
It's all very well to open up the HCE for banks, but what about other ways of using the HCE. There are companies in the Americas and Asia leveraging Apple's NFC HCE for access control, integrating access badges/cards into Apple Wallet. Is this functionality available in Europe? If not, what's the reason? Can this be accomplished using Apple's Secure Element? I haven't come across any information addressing this.
Post not yet marked as solved
Hello iPhone xs for testing XCode 15.3 I've successfully managed to select the AID and send other commands to a SmartCard using the following code: class NFCReader: NSObject, ObservableObject, NFCTagReaderSessionDelegate { func startNFCSession() { session = NFCTagReaderSession(pollingOption: [.iso14443], delegate: self, queue: nil) session?.alertMessage = Hold your iPhone near the NFC tag. session?.begin() // Start the session } func tagReaderSession(_ session: NFCTagReaderSession, didDetect tags: [NFCTag]) { guard let tag = tags.first else { // Safely unwrap the first tag session.invalidate(errorMessage: No SmartCard detected.) return } session.connect(to: tag, completionHandler: { (error: Error?) in if let error = error { session.invalidate(errorMessage: Unable to connect to SmartCard: (error.localizedDescription)) return } switch tag { case let .iso7816(iso7816Tag): self.sendAPDUCommandSelect(to: iso7816Tag) self.sendAPDUCommand_2(to: iso7816Tag) default: print(Not iso7816 type) // Update the Swif
Post not yet marked as solved
No, Core NFC is not available in the watchOS SDK.
Post not yet marked as solved
Once you have successfully built and installed your app, properly configured with the necessary entitlements, you 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.
Post not yet marked as solved
Is there a way to access the Core NFC Framework from within a watchOS app?
Post not yet marked as solved
I am following this code https://developer.apple.com/documentation/corenfc/building_an_nfc_tag-reader_app to implement a simple scanner for NFC. Now whenever I scan I am always getting connection to service with pid 60 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 NFFieldNotificationECP1_0 not loaded or does not exist>. this error. It always calls this function func readerSession(_ session: NFCNDEFReaderSession, didInvalidateWithError error: Error)
Post not yet marked as solved
Hello everyone Together with a team of students, we have developed an application for android, a pass system that works using NFC, tell me if it will be possible to release a similar system on iOS. It's just that payment using NFC does not work in Russia. In our case, payment is not necessary, the NFC chip is used to transmit the signal to the reader. I would be very grateful if you could tell me if it will be possible to release our application in the App Store
Post not yet marked as solved
Hello All, I am new to iOS development and would like to detect the smart card readers connected to USB-C port on iOS (16+) devices. The smart card reader is a custom hardware and not MFi certified. So as per my understanding, I cannot use ExternalAccessory.framework without MFi certification. Correct? How else can I achieve this? Does TKSmartCardSlotManager works for this purpose (or is it only for NFC devices?)? Is there any example for how to use this interface? I couldn't find any example for this as a starting point... Thanks in advance.
Post not yet marked as solved
Hello all! I have an app (Scriptio Medication Management) that uses NFC on iPhone, and that works really well. However, I need a larger screen to satisfy customer requests (reports, etc). Because we use NFC tags to authenticate & authorize I need to stick with this tech. I cannot assume that all my customers have iPhone (we also deploy to Android) so pairing an iPad with an iPhone doesn't work for us. I was looking at an external device such as FlowJack, but since iPad no longer has an audio port, this won't work for me. Has anyone been able to solve this type of issue? Ideally I can find a solution that non-technical folks can attach/pair with an iPad to read NFC devices (NOT payment processing). Thanks in advance
Post not yet marked as solved
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
Post not yet marked as solved
REYAX Technology, an IOT solution provider based in Taiwan luanched a new NFC/RFID modules that features Industrial NFC/RFID Engine and Apple Wallwt VAS & Google Smart Tap pass - RYRR30D, I believe this could fullfill your inquiries:)
Post not yet marked as solved
hi im tryng for some time to get the certification for NFC-enabled pass to use with Apple Wallet. but not response from apple team they just send a email with some question we reply but them we have not response.. can some one help me?
I have a required item for NFC in the Info.plist, was copy pasted from a flutter plugin for NFC github.
I have published the app on the App Store along with its corresponding app clip, my app clip is configured with some advanced experiences for each one of my clients, but whenever some users try to scan an NFC or QR Code they see the card rendering correctly with their configured banner image, but with the message App Clip Unavailable. The weird thing is that both iMessage and the website to which the associated domain is set and the apple-app-site-association is stored, renders the banner or card correctly, and when the users tap the banner or card they open the advanced app clip experience correctly without any issue. I have attempted to troubleshoot the issue by checking the following: if the app clip is below 15MB if we are using a second level domain in my associated domain both for my app clip and app (excluding the www subdomain). checking if the AASA is correctly stored inside .well-known directory checking the configuration for the advanced experience I opened a case: 102233443873, and added
