nfc

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

I'm working on an app (actually in Test Flight) that has camera and NFC support. So in iPhone is obviously working as expected, but when testers want to try the camera aspect of the app on iPads they can't even download the app it says No compatible hardware in Test Flight. What I need to do in this case, I already have a UI/UX solution when theres no NFC support or it's disabled (Android can detect this) but here I have no clue if I'm missing something. Thanks in advance

Hi there. I am using flutter_nfc_kit (https://pub.dev/packages/flutter_nfc_kit) to make application that sends bytes to NFC module using tranceive commands, but really often system respond with error 500 or 103... Is there anything in this package that I can change for my commands to work fine? Cause now when I try to scan data it takes minimum like 30 seconds whereas on Android it takes like 7-10 seconds every time Thanks for any feedback

Both the codesign tool and Xcode allow you to sign code with a hardware-based code-signing identity. However, setting that up can be a bit of a challenge. Recently a developer open a DTS tech support incident requesting help with this, and so I thought I’d post my instructions here for the benefit of all. If you have any questions or comments about this, please start a new thread, tagging it with Code Signing so that I see it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com Signing code with a hardware-based code-signing identity Both the codesign tool and Xcode allow you to sign code with a hardware-based code-signing identity. This post explains how to set that up. I used macOS 14.2.1 with Xcode 15.2. For my hardware-based key I used a YubiKey 5 NFC that I reset to its defaults. I installed YubiKey Manager 1.2.5. IMPORTANT While I used a YubiKey, the code signing parts of this process should work with any token that has a function

Hello I am developing an iOS app and would like to read an EMV card that is issued by me and want my customers to tap to activate simply to validate the possession of the card at the time of activation. Any suggestions welcome on how can i achieve this using either NFC Framework or secure elements