Dear Apple Support Team, I am writing to bring to your attention an issue we have encountered with NFC (Near Field Communication) functionality on Apple devices, specifically related to the initiation of new NFC sessions after tapping the 'Cancel' button during a previous session. This issue seems to occur predominantly when the device is in Aeroplane mode. The problem we are facing is that the NFC pop-up fails to initiate when a user tries to start a new NFC session after cancelling a previous one. This limitation has caused inconvenience for both our team and our users, as we rely heavily on NFC technology for various applications. We kindly request your support and expertise in investigating and resolving this issue. We understand the complexities involved in addressing such matters and greatly appreciate your dedication to improving the functionality of Apple products. By addressing this problem, you would contribute to enhancing the reliability and user experi
Search results for
nfc
1,176 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
If NFC is now essential, you need to create a new app. It would normally be better to make NFC optional, by continuing to provide the old behaviour on devices that don’t have NFC, and not adding it to the required capabilities. What devices don’t have NFC now? With some of these capabilities you can require them by requiring a sufficiently new iOS version which only runs on hardware that has the feature. One example of that was OpenGL ES 2. Apple do allow to to require a newer iOS version that excludes some existing users.
Topic:
Code Signing
SubTopic:
Entitlements
Tags:
I've added NFC support for my app. So, my UIRequiredDeviceCapabilities were extended from armv7 to armv7 nfc. This means I've prevented this application from running on devices supported by previous versions. Now I've received a message from Apple: ITMS-90109: This bundle is invalid - The key UIRequiredDeviceCapabilities in the Info.plist may not contain values that would prevent this application from running on devices that were supported by previous versions. What is the right way to add new functions?
App Store Review Guidelines said: 3.1.4 Hardware-Specific Content: In limited circumstances, such as when features are dependent upon specific hardware to function, the app may unlock that functionality without using in-app purchase (e.g. an astronomy app that adds features when synced with a telescope). My app has the feature to read NFC tags and write information to normal NFC tags. My app must have that NFC tags features. My app offers auto-renewable subscription with free trials without unlocking that NFC tags features. I think telescopes and normal NFC tags are different. Normal NFC tag is very cheap general-purpose product. Will Apple reject my app?
Hi vastmine1029! If you are looking to decrypt the payload of another organization's NFC-enabled pass this is not possible. The NFC-payloads are encrypted with merchant-specific key pairs (this is a heavy simplification of the security) and cannot be read even with Apple VAS compatible readers without one of one of these keys. If you are referring to NFC-enabled passes that were created by your organization you'd need to reach out to your IT admin or terminal integrator/manufacturer for the organization-specific public key as well as any necessary decryption info.
Topic:
App & System Services
SubTopic:
Apple Pay
Tags:
• I have an NFC read-write app in Flutter and I have been testing it on iPhone se 2020 in developer mode using both Xcode and test flight • It was reading and writing NFC tags fine until the last 10 days or so . Now NFC tag read works but write and erase fails • In Xcode debug mode sometimes the app works. It clears NFC tags and writes into tags correctly, the rest of the time it says it can not. And it gives platform exception tag is not connected, 401 error on tag write and 104 on tag erase. • Other NFC apps on my phone still read-write correctly so nfc hardware on my phone is not faulty • and nfc tags are also not faulty as they work fine with other apps • My app's old builds on the test flight were working fine but even they are not working now, so it's not a change in my code that broke the app • Can a software update on iPhone se 2020 break it, but why does another app still work with the phone but not mine • Xocde uses an automatic provisio
Hi, There are certain NFC tags not compatible with the iphone, for example a vcard, text, location, etc. Does anybody what data tags is compatible with iphone?
Hi, i have a application that has textfields on UI. I can share this textfield's texts with using NFC on RFID card. I want to share this without using rfid cards, is it possible to share this texts with only using two iphone? For example, 1 iphone will be a reader, and other one will be a writer. Both phones are using same application. Read and Write nfc buttons are stay in application.
I have researched this extensively as well. iOS has a HCE (Host Card Emulation) feature. The proof is in the HCE function in Wallet to realize a virtual transportation The proof is in the fact that Wallet uses HCE to realize a virtual transportation IC card. However, Apple keeps this HCE feature secret so that other developers cannot use it. I think Apple is afraid that the HCE function will be abused. Especially since the HCE feature is related to money and keys. Android, on the other hand, is designed to be highly flexible, so the HCE feature can be used as shown in the video. If you want to create a system or app that uses HCE, you need to create an app for Android or wait until Apple changes its mind. One exception is a system that uses the iPhone as a car key. That is a world-class company like BMW, so they got permission from Apple to make it happen. Developers working for ordinary companies have to give up. As a backdoor technique, it may be possible to have the user register a credit card or transport
Topic:
App & System Services
SubTopic:
General
Tags:
1 year later and it hasn’t been fixed? I’ve just updated to the latest iPhone update and still can’t read them I have to nfc readers on my phone and information on cards show on both but my own phone cannot read them
Topic:
App & System Services
SubTopic:
General
Tags:
I dusted off my YubiKey and tried this out today. Here’s what I did: On macOS 13.2.1 with YubiKey Manager 1.2.4 installed… In Terminal, I found my Apple Development signing identity: % security find-identity … Valid identities only … 4) 4E587951B705280CBB8086325CD134D4CDA04977 Apple Development: Quinn Quinn (7XFU7D52S4) … I ran Keychain Access and exported that to a .p12 file. I then used Keychain Access to delete both the private key and the certificate. Back in Terminal, I repeated step 2 and confirmed that the identity was gone. I attached my YubiKey 5 NFC via USB. I elected not to pair it with my account. I use YubiKey Manager to clear out all the PIV slots. And then import the .p12 from step 3 into the Digital Signature slot (9c). (I don’t think the exact slot matters but that seems like the right choice.) I disconnected and reconnected the YubiKey, continuing to opt out of pairing. In Terminal, I ran sc_auth to confirm that my identity is online: % sc_auth identities … SmartCard: com.apple.pivt
Topic:
Code Signing
SubTopic:
General
Tags:
Please Apple company add NFC tag reading functionality to the Apple Watch, just like all the previous commentators asked for. I'm sure we would even pay extra for it. Please do it before the Apple Watch becomes obsolete, like every technical gadget eventually has to. Do it for humanity now. Or, at least tell us that it won't happen or that we have to wait until the augmented reality glasses are proven a flop.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
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?
Hi, In order to use Passkeys and Security Keys during authentication we create two requests (ASAuthorizationPlatformPublicKeyCredentialAssertionRequest and ASAuthorizationSecurityKeyPublicKeyCredentialAssertionRequest) and passing them to ASAuthorizationController. Then after performRequests call we got the Passkey UI with option to use Security Key as well as desired for devices before iOS 16.4. But the same code in iOS 16.4 device does not show Passkey as option at all. Only Security Key and passkey on other device via QR code options are available in the UI. If we don’t pass Security Key request, then Passkey is asked and authentication works. If we pass Security Key request but don’t include any allowedCredentials then Passkey is asked and authentication works. But if I select Security Key option then it is not working (system UI not reacting on NFC security key at all). We assume something was broken in 16.4. is any option to make behavior same as before?
When i write text record on nfc tag, sometimes success but sometimes gives me error below. Error: Error Domain=NFCError Code=401 Stack Error UserInfo={NSLocalizedDescription=Stack Error, NSUnderlyingError=0x2822f9a10 {Error Domain=nfcd Code=21 writeNdefData:toTag:error::360 UserInfo={Line=360, NSLocalizedDescription=Connection Closed, NSDebugDescription=writeNdefData:toTag:error::360, Method=writeNdefData:toTag:error:}}} I don't know why this error sometimes occur. What is the meaning of Connection Closed? And how can I solve the issue?