nfc

I am trying to launch Nfc session but its failing with the below error ** CoreNFC CRASHING_DUE_TO_PRIVACY_VIOLATION NSLocalizedFailureReason = This app cannot be installed because its integrity could not be verified. Failed to verify code signature ... (A valid provisioning profile for this executable was not found.)** But We have declared NFC in capabilities both in code base and provisioning profile. Tools Used VS Code , MAUI IOS Development Please let me know how to resolve this issue

I stumbled across the Apple NFC & SE Platform while searching for the cause to a persistent missing entitlement error. I am curious if not having this entitlement could be the root cause to my issues? Specifically, I am trying to perform an HMAC-SHA1 challenge-response via NFC on a YubiKey. Part of this entails low level APDU Send commands via NFC. The missing entitlement occurs right after the APDU Send. Per my separate post, I believe I have exhausted all other possible causes to no avail. For reference and details, this is the other post: [https://developer.apple.com/forums/thread/791995)

The root issues is a missing entitlement error. I've jumped through countless hoops of checking/rechecking .entitlement file/plist file, creating new credentials, creating new projects, creating new provisioning profiles with no luck, manual signing, automatic signing. Any suggestions appreciated. Looking at the Provisioning Profile Info shows NFC Tag capabilities is included and NFC Entitlements are included. I'm at a loss... I am including the following: Pertinent output from console Current Info.Plist Current .entitlement file Here are the pertinent sectsis the Console Log for reference: ... NFCConnectionManager[0x074d6e40].tagReaderSessionDidBecomeActive(:): NFCTagReaderSessionDelegate: Session did become active NFCConnectionManager[0x074d6e40].tagReaderSession(:didDetect:): NFCTagReaderSessionDelegate: Session didDetectTags – 1 tags NFCConnectionManager[0x074d6e40].connected(session:tag:): Manager.connected(session:tag:) - tag: 7 bytes NFCConnection.Type.connection(): NFCConnection.conn

Hi everyone, I’m working on an iOS project where an iPhone needs to connect to external scanners (dedicated hardware devices) over Wi-Fi. The goal is to: Discover available Wi-Fi networks from the scanner devices (broadcasting their own networks). Allow the user to seamlessly connect to the chosen scanner network. Network Discovery: Is there a way to programmatically list available Wi-Fi networks (SSIDs) on iOS without private APIs? If not, are there workarounds (e.g., Bonjour/mDNS)? Seamless Connection: As I see, we can use NEHotspotConfigurationManager to connect to and disconnect from specified networks and there will always be a system alert asking about do we really want to join this network Hardware/Firmware/Software Alternatives: If iOS restrictions prevent this, what alternatives exist? For example: Hardware: Scanners supporting Bluetooth LE for initial pairing, then Wi-Fi provisioning. Firmware: Scanners acting as clients on the same network as the iPhone (e.g., via user’s home/office Wi-Fi). Softwar

I'm in the process of exploring using Passkit to host and distribute our University Digital ID card. I understand that Apple has worked with a few Universities in this Vertical and that there is a means to apply for this program. The only issue is that we don't have a one card solution, and our cards aren't distributed through Blackboard. We would like to handle this ourselves though with NFC readers deployed at strategic locations throughout campus (i.e. the Library, shared printers (Where students are required to swipe their ID's to release print jobs) as well as Dining locations, where they use their ID cards for a declining balance.Is there a way to work with Apple to get an NFC certificate for this using the system I described (barring having to work with Blackboard)?

Hello Apple Developer Community and Apple Team, I want to raise awareness and gather support for an important feature request regarding NFC support on iPhone devices in Argentina. Millions of Argentinians use the official public transit card, SUBE, daily to pay for buses, subways, and trains. On Android devices, the SUBE app allows users to: • Check balance via NFC • Reload credit instantly • Confirm top-ups by holding the card near the phone • Use a digital version of the card (in some cases) However, iPhone users cannot use these NFC features because iOS currently does not allow third-party apps like SUBE to access the NFC chip fully. This limitation negatively impacts iPhone users, many of whom rely heavily on SUBE. I have submitted detailed feedback to Apple requesting the enablement of controlled NFC access for third-party transit apps in Argentina, starting with SUBE. I encourage fellow developers, users, and community members to support this request. Enablin

Some background: We are developing an app that needs to scan NFC tags We are following this documentation for our app We (assume) we've gotten all the correct entitlements for our app Our app correctly shows the NFC scanning prompt We are using up-to-date iPhones to test We tested scanning using a different NFC app on the app store and were able to successfully scan the tag We're using NFC NDEF tags to test The problem: Nothing is being detected in the scan Nothing in the example application when we downloaded it down and loaded it onto a test device (reminder that the app from the app store was able to read our tag) When connected to the debugger, our delegate function is not firing (tested with breakpoints and print statements). The following is the signature of our delegate function: func readerSession(_ session: NFCNDEFReaderSession, didDetectNDEFs messages: [NFCNDEFMessage]) Is there something that we're missing to get the NFC scanning to work? Perhaps some ki

Hi everyone, I'm working on a library application that uses ISO15693 NFC tags embedded in books to track checkout status. These tags are password-protected and require secure access in order to write the AFI (Application Family Identifier) field, which we use to mark books as checked out. According to the tag spec (ST SL2S2602), the flow for writing to a protected AFI requires: Sending Get Random Number (custom command 0xB2) Sending Present Password (custom command 0xB3) Writing AFI using Write AFI (0x27) We’re using Core NFC's customCommand(requestFlags:customCommandCode:customRequestParameters:) on NFCISO15693Tag. While basic tag operations like getSystemInfo() and readSingleBlock() work fine, any customCommand immediately fails with this error: Error Domain=NFCError Code=100 Tag connection lost This only happens on tags that return ICRef = 0x01 in the system info response. The exact same tags and command sequence work fine on Android (transceive) and in desktop NFC tools. It look

I am working with a Texas Instruments RF430 NFC tag, which is compliant with: ISO/IEC 14443-4 (ISO-DEP) NFC Forum Type 4 Tag NFC-B protocol NDEF-formatted storage I’m using an iPhone 12 running iOS 18, and my app uses the Core NFC framework. Using NFCNDEFReaderSessionDelegate, I am able to successfully read the first NDEF message from the tag. However, the tag stores multiple NDEF messages, and I would like to access the others. Based on the tag’s specification, these messages are accessible via an NDEF file located at file ID 0xE104. To try and access this additional NDEF file, I attempted to use NFCTagReaderSession with the NFCTagReaderSessionDelegate, intending to issue APDU commands. However, the tagReaderSession(_:didDetect:) delegate method is never called, even though the tag is present and detected using NFCNDEFReaderSession. My questions: Does Core NFC on iOS 18 support issuing custom APDU commands to ISO 14443-4 (NFC-B) tags like the TI RF430? Is

Hi, I’m trying to migrate an App Clip from one main app (App A) to another (App B). These two apps are under the same Apple Developer Account (Team ID), and each has its own App Group. I’m wondering: 1. If I change the App Group configured in the App Clip’s entitlements, will this effectively allow the App Clip to be treated as part of App B? 2. Will this change allow me to reuse the existing App Clip Experiences (e.g., NFC/QR code invocation URLs) that were originally associated with App A? 3. Is such a change sufficient for Apple to treat the App Clip as migrated, or are there additional steps (e.g., changing the Bundle ID, resubmitting the App Clip Experience, etc.) required to complete the migration? I want to confirm whether switching the App Group and submitting a new App Clip with the new app is a valid and seamless way to perform the migration. I understand App Groups are typically used for data sharing, not experience binding — but I want to clarify if switching App Groups affects App Clip–m