Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
dpearson2699 avatar

Core Nfc

  • 2.6k installs
  • 944 repo stars
  • Updated July 15, 2026
  • dpearson2699/swift-ios-skills

core-nfc is an iOS skill for CoreNFC NDEF and native tag reader sessions with entitlements and write patterns.

About

The core-nfc skill documents read and write NFC tag workflows on iPhone using Apple's CoreNFC framework for Swift 6.3 and iOS 26 plus. Setup requires the Near Field Communication Tag Reading capability, NFCReaderUsageDescription in Info.plist, and com.apple.developer.nfc.readersession.formats entitlements with current TAG values rather than legacy NDEF. NFCNDEFReaderSession covers standard NDEF URLs, text, and MIME records, while NFCTagReaderSession exposes ISO7816, ISO15693, FeliCa, and MIFARE protocols with protocol-specific polling options. Examples walk delegate lifecycle methods, connect-to-tag flows, queryNDEFStatus for readOnly versus readWrite tags, wellKnownTypeURIPayload writes, and invalidate error handling. Device support starts at iPhone 7 with readingAvailable guards before showing NFC UI. Additional guidance covers ISO7816 application identifiers, FeliCa system codes without wildcards, background tag reading, common mistakes, and a review checklist. Apple documents NFCPaymentTagReaderSession for eligible EU payment AIDs instead of generic tag sessions.

  • NFCNDEFReaderSession scans NDEF tags; NFCTagReaderSession handles ISO7816, FeliCa, and MIFARE.
  • Entitlements use com.apple.developer.nfc.readersession.formats TAG values, not legacy NDEF.
  • queryNDEFStatus distinguishes readOnly, readWrite, and notSupported before reads or writes.
  • readingAvailable must be checked before creating sessions on supported iPhone hardware.
  • Payment AIDs belong on NFCPaymentTagReaderSession per Apple EU payment guidance.

Core Nfc by the numbers

  • 2,569 all-time installs (skills.sh)
  • +110 installs in the week ending Jul 29, 2026 (Skillselion tracking)
  • Ranked #81 of 1,039 Mobile Development skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
At a glance

core-nfc capabilities & compatibility

Capabilities
nfcndefreadersession delegate lifecycle and tag · nfctagreadersession multi protocol polling and t · ndef message construction and wellknowntypeuripa · entitlement and info.plist setup for nfcreaderus · background tag reading and review checklist guid
Use cases
frontend · api development
Platforms
macOS
From the docs

What core-nfc says it does

Read and write NFC tags on iPhone using the CoreNFC framework.
SKILL.md
npx skills add https://github.com/dpearson2699/swift-ios-skills --skill core-nfc

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs2.6k
repo stars944
Security audit2 / 3 scanners passed
Last updatedJuly 15, 2026
Repositorydpearson2699/swift-ios-skills

How do I read and write NFC tags with CoreNFC in a Swift iOS app?

Implement CoreNFC NDEF and tag reader sessions, write NDEF payloads, configure entitlements, and handle background tag reading in Swift iOS apps.

Who is it for?

iOS apps scanning NDEF tags, writing URLs, or accessing ISO7816, FeliCa, and MIFARE tags.

Skip if: Skip for Android NFC or server-only tag provisioning without on-device CoreNFC.

When should I use this skill?

User mentions CoreNFC, NDEF reader session, NFC entitlements, or background tag reading.

What you get

Configured NFC sessions, entitlements, and delegate code for NDEF or protocol-specific tag access.

  • entitlement review
  • nfc reader session plan
  • aid configuration checklist

Files

SKILL.mdMarkdownGitHub ↗

CoreNFC

Read and write NFC tags on iPhone using the CoreNFC framework. Covers NDEF reader sessions, tag reader sessions, NDEF message construction, entitlements, and background tag reading. Targets Swift 6.3 / iOS 26+.

Contents

Setup

Project Configuration

1. Add the Near Field Communication Tag Reading capability in Xcode 2. Add NFCReaderUsageDescription to Info.plist with a user-facing reason string 3. Add the com.apple.developer.nfc.readersession.formats entitlement with the current TAG value; do not add legacy NDEF 4. For ISO 7816 tags, add supported application identifiers to com.apple.developer.nfc.readersession.iso7816.select-identifiers in Info.plist 5. For FeliCa tags, add supported system codes to com.apple.developer.nfc.readersession.felica.systemcodes; do not use wildcard system codes

Device Requirements

NFC reading requires iPhone 7 or later. Always check for reader session availability before creating NFC UI or sessions. Use the concrete reader session type you are about to create.

import CoreNFC

guard NFCNDEFReaderSession.readingAvailable else {
    // Device does not support NFC or feature is restricted
    showUnsupportedMessage()
    return
}

Key Types

TypeRole
NFCNDEFReaderSessionScans for NDEF-formatted tags
NFCTagReaderSessionScans for ISO7816, ISO15693, FeliCa, MIFARE tags
NFCNDEFMessageCollection of NDEF payload records
NFCNDEFPayloadSingle record within an NDEF message
NFCNDEFTagProtocol for interacting with an NDEF-capable tag

NDEF Reader Session

Use NFCNDEFReaderSession to read NDEF-formatted data from tags. This is the simplest path for reading standard tag content like URLs, text, and MIME data.

import CoreNFC

final class NDEFReader: NSObject, NFCNDEFReaderSessionDelegate {
    private var session: NFCNDEFReaderSession?

    func beginScanning() {
        guard NFCNDEFReaderSession.readingAvailable else { return }

        session = NFCNDEFReaderSession(
            delegate: self,
            queue: nil,
            invalidateAfterFirstRead: false
        )
        session?.alertMessage = "Hold your iPhone near an NFC tag."
        session?.begin()
    }

    // MARK: - NFCNDEFReaderSessionDelegate

    func readerSessionDidBecomeActive(_ session: NFCNDEFReaderSession) {
        // Session is scanning
    }

    func readerSession(
        _ session: NFCNDEFReaderSession,
        didDetectNDEFs messages: [NFCNDEFMessage]
    ) {
        for message in messages {
            for record in message.records {
                processRecord(record)
            }
        }
    }

    func readerSession(
        _ session: NFCNDEFReaderSession,
        didInvalidateWithError error: Error
    ) {
        let nfcError = error as? NFCReaderError
        if nfcError?.code != .readerSessionInvalidationErrorFirstNDEFTagRead,
           nfcError?.code != .readerSessionInvalidationErrorUserCanceled {
            print("Session invalidated: \(error.localizedDescription)")
        }
        self.session = nil
    }
}

Reading with Tag Connection

For read-write operations, use the tag-detection delegate method to connect to individual tags:

func readerSession(
    _ session: NFCNDEFReaderSession,
    didDetect tags: [any NFCNDEFTag]
) {
    guard let tag = tags.first else {
        session.restartPolling()
        return
    }

    session.connect(to: tag) { error in
        if let error {
            session.invalidate(errorMessage: "Connection failed: \(error)")
            return
        }

        tag.queryNDEFStatus { status, capacity, error in
            guard error == nil else {
                session.invalidate(errorMessage: "Query failed.")
                return
            }

            switch status {
            case .notSupported:
                session.invalidate(errorMessage: "Tag is not NDEF compliant.")
            case .readOnly:
                tag.readNDEF { message, error in
                    if let message {
                        self.processMessage(message)
                    }
                    session.invalidate()
                }
            case .readWrite:
                tag.readNDEF { message, error in
                    if let message {
                        self.processMessage(message)
                    }
                    session.alertMessage = "Tag read successfully."
                    session.invalidate()
                }
            @unknown default:
                session.invalidate()
            }
        }
    }
}

Tag Reader Session

Use NFCTagReaderSession when you need direct access to the native tag protocol (ISO 7816, ISO 15693, FeliCa, or MIFARE).

Polling options are protocol-specific: .iso14443 detects ISO 7816-compatible and MIFARE tags, .iso15693 detects ISO 15693 tags, and .iso18092 detects FeliCa tags. Do not use NFCTagReaderSession for payment-related AIDs; Apple documents NFCPaymentTagReaderSession for eligible EU payment use cases.

final class TagReader: NSObject, NFCTagReaderSessionDelegate {
    private var session: NFCTagReaderSession?

    func beginScanning() {
        guard NFCTagReaderSession.readingAvailable else { return }

        session = NFCTagReaderSession(
            pollingOption: [.iso14443, .iso15693, .iso18092],
            delegate: self,
            queue: nil
        )
        session?.alertMessage = "Hold your iPhone near a tag."
        session?.begin()
    }

    func tagReaderSessionDidBecomeActive(
        _ session: NFCTagReaderSession
    ) { }

    func tagReaderSession(
        _ session: NFCTagReaderSession,
        didDetect tags: [NFCTag]
    ) {
        guard let tag = tags.first else { return }

        session.connect(to: tag) { error in
            guard error == nil else {
                session.invalidate(
                    errorMessage: "Connection failed."
                )
                return
            }

            switch tag {
            case .iso7816(let iso7816Tag):
                self.readISO7816(tag: iso7816Tag, session: session)
            case .miFare(let miFareTag):
                self.readMiFare(tag: miFareTag, session: session)
            case .iso15693(let iso15693Tag):
                self.readISO15693(tag: iso15693Tag, session: session)
            case .feliCa(let feliCaTag):
                self.readFeliCa(tag: feliCaTag, session: session)
            @unknown default:
                session.invalidate(errorMessage: "Unsupported tag type.")
            }
        }
    }

    func tagReaderSession(
        _ session: NFCTagReaderSession,
        didInvalidateWithError error: Error
    ) {
        self.session = nil
    }
}

Writing NDEF Messages

Write NDEF data to a connected tag. Always check readWrite status first.

func writeToTag(
    tag: any NFCNDEFTag,
    session: NFCNDEFReaderSession,
    url: URL
) {
    tag.queryNDEFStatus { status, capacity, error in
        guard status == .readWrite else {
            session.invalidate(errorMessage: "Tag is read-only.")
            return
        }

        guard let payload = NFCNDEFPayload.wellKnownTypeURIPayload(
            url: url
        ) else {
            session.invalidate(errorMessage: "Invalid URL.")
            return
        }

        let message = NFCNDEFMessage(records: [payload])

        tag.writeNDEF(message) { error in
            if let error {
                session.invalidate(
                    errorMessage: "Write failed: \(error.localizedDescription)"
                )
            } else {
                session.alertMessage = "Tag written successfully."
                session.invalidate()
            }
        }
    }
}

NDEF Payload Types

Creating Common Payloads

// URL payload
let urlPayload = NFCNDEFPayload.wellKnownTypeURIPayload(
    url: URL(string: "https://example.com")!
)

// Text payload
let textPayload = NFCNDEFPayload.wellKnownTypeTextPayload(
    string: "Hello NFC",
    locale: Locale(identifier: "en")
)

// Custom payload
let customPayload = NFCNDEFPayload(
    format: .nfcExternal,
    type: "com.example:mytype".data(using: .utf8)!,
    identifier: Data(),
    payload: "custom-data".data(using: .utf8)!
)

Parsing Payload Content

func processRecord(_ record: NFCNDEFPayload) {
    switch record.typeNameFormat {
    case .nfcWellKnown:
        if let url = record.wellKnownTypeURIPayload() {
            print("URL: \(url)")
        } else if let (text, locale) = record.wellKnownTypeTextPayload() {
            print("Text (\(locale)): \(text)")
        }
    case .absoluteURI:
        if let uri = String(data: record.payload, encoding: .utf8) {
            print("Absolute URI: \(uri)")
        }
    case .media:
        let mimeType = String(data: record.type, encoding: .utf8) ?? ""
        print("MIME type: \(mimeType), size: \(record.payload.count)")
    case .nfcExternal:
        let type = String(data: record.type, encoding: .utf8) ?? ""
        print("External type: \(type)")
    case .empty, .unknown, .unchanged:
        break
    @unknown default:
        break
    }
}

Background Tag Reading

On iPhone XS and later, iOS can read NFC tags in the background without opening your app. The NDEF message must contain a URI record (typeNameFormat == .nfcWellKnown, type U). If there are multiple URI records, the system uses the first one.

For app-specific routing, write a universal link to the tag and configure the Associated Domains capability for that domain. Background tag reading also supports specific system URL schemes such as web, email, SMS, telephone, FaceTime, Maps, and HomeKit setup. It does not support custom URL schemes, and the system does not route by bundle ID or arbitrary NDEF content type.

When a user taps a compatible tag, iOS displays a notification that opens your app. Handle the tag data via NSUserActivity:

func scene(
    _ scene: UIScene,
    continue userActivity: NSUserActivity
) {
    guard userActivity.activityType ==
        NSUserActivityTypeBrowsingWeb else { return }

    let message = userActivity.ndefMessagePayload
    guard message.records.first?.typeNameFormat != .empty else { return }

    for record in message.records {
        processRecord(record)
    }
}

Common Mistakes

DON'T: Use stale or missing NFC entitlements

Without the com.apple.developer.nfc.readersession.formats entitlement, reader sessions cannot access NFC hardware. Use the current TAG value for Core NFC reader sessions; do not copy older examples that add NDEF.

DON'T: Skip the readingAvailable check

Creating an NFC session on an unsupported or restricted device fails before the scan UI can do useful work.

Check NFCNDEFReaderSession.readingAvailable or NFCTagReaderSession.readingAvailable before creating the matching session.

DON'T: Ignore session invalidation errors

The session invalidates for multiple reasons. Distinguishing user cancellation from real errors prevents false error alerts.

// WRONG -- shows error when user cancels
func readerSession(
    _ session: NFCNDEFReaderSession,
    didInvalidateWithError error: Error
) {
    showAlert("NFC Error: \(error.localizedDescription)")
}

// CORRECT -- filter expected invalidation reasons
func readerSession(
    _ session: NFCNDEFReaderSession,
    didInvalidateWithError error: Error
) {
    let nfcError = error as? NFCReaderError
    switch nfcError?.code {
    case .readerSessionInvalidationErrorUserCanceled,
         .readerSessionInvalidationErrorFirstNDEFTagRead:
        break  // Normal termination
    default:
        showAlert("NFC Error: \(error.localizedDescription)")
    }
    self.session = nil
}

DON'T: Hold a strong reference to a stale session

Once a session is invalidated, it cannot be restarted. Nil out your reference and create a new session for the next scan.

// WRONG -- reusing invalidated session
func scanAgain() {
    session?.begin()  // Does nothing, session is dead
}

// CORRECT -- create a new session
func scanAgain() {
    session = NFCNDEFReaderSession(
        delegate: self, queue: nil, invalidateAfterFirstRead: false
    )
    session?.begin()
}

DON'T: Write without checking tag status

Writing to a read-only tag silently fails or produces confusing errors.

// WRONG -- writes without checking status
tag.writeNDEF(message) { error in
    // May fail on read-only tags
}

// CORRECT -- check status first
tag.queryNDEFStatus { status, capacity, error in
    guard status == .readWrite else {
        session.invalidate(errorMessage: "Tag is read-only.")
        return
    }
    tag.writeNDEF(message) { error in
        // Handle result
    }
}

Review Checklist

  • [ ] NFC capability added in Signing & Capabilities
  • [ ] NFCReaderUsageDescription set in Info.plist
  • [ ] com.apple.developer.nfc.readersession.formats entitlement uses TAG, not legacy NDEF
  • [ ] NFCNDEFReaderSession.readingAvailable or NFCTagReaderSession.readingAvailable checked before creating sessions
  • [ ] Session delegate set before calling begin()
  • [ ] Session reference set to nil after invalidation
  • [ ] didInvalidateWithError distinguishes user cancellation from actual errors
  • [ ] NDEF status queried before write operations
  • [ ] Tag capacity checked before writing large messages
  • [ ] ISO 7816 application identifiers listed in Info.plist if using NFCTagReaderSession
  • [ ] FeliCa system codes listed in Info.plist when polling .iso18092
  • [ ] Background tag reading uses a URI NDEF record and universal links or supported system URL schemes
  • [ ] Custom URL schemes, bundle IDs, or arbitrary NDEF content types are not used for background routing
  • [ ] Payment-related AIDs are routed away from NFCTagReaderSession
  • [ ] Only one reader session active at a time

References

Related skills

How it compares

Use core-nfc for Apple Core NFC entitlement and multi-format reader reviews rather than generic iOS skills without ISO 7816 or FeliCa specifics.

FAQ

Which session type should I use for URL tags?

Use NFCNDEFReaderSession for standard NDEF-formatted tags with URLs, text, or MIME payloads.

What entitlement format value should I add?

Add com.apple.developer.nfc.readersession.formats with the current TAG value; do not add legacy NDEF.

When is NFCTagReaderSession required?

Use it when you need ISO7816, ISO15693, FeliCa, or MIFARE protocol access beyond NDEF.

Is Core Nfc safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Mobile Developmentfrontendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.