@mmerterden/multi-agent-pipeline 8.6.1 → 10.0.6

package/pipeline/skills/shared/external/core-motion/evals/evals.json

@@ -0,0 +1,49 @@
+{
+  "skill_name": "core-motion",
+  "evals": [
+    {
+      "id": 0,
+      "prompt": "Build a concise SwiftUI tilt-control service for an iOS game. It should read device motion at a reasonable rate, avoid wasting battery, and clean up correctly when the view disappears.",
+      "expected_output": "A Core Motion implementation outline that uses one CMMotionManager, includes NSMotionUsageDescription, checks availability/reference frames, starts device-motion or accelerometer updates at a suitable interval, handles errors/queues, and stops updates on lifecycle exit.",
+      "files": [],
+      "expectations": [
+        "Adds or calls out NSMotionUsageDescription before accessing motion data.",
+        "Uses a single shared CMMotionManager instead of one manager per view.",
+        "Checks isDeviceMotionAvailable or the relevant sensor availability before starting updates.",
+        "Chooses a modest update interval based on the interaction instead of defaulting to the highest possible rate.",
+        "Stops the matching updates when the view or service is no longer active.",
+        "Checks available attitude reference frames before requesting a north-based frame."
+      ]
+    },
+    {
+      "id": 1,
+      "prompt": "Review this plan for a hiking app: use CMPedometer for daily steps, CMMotionActivityManager to switch walking/driving modes, and CMAltimeter for elevation. The team says absolute altitude is GPS-based, activity flags are mutually exclusive, and only activity recognition needs motion permission.",
+      "expected_output": "A correction-focused review that covers NSMotionUsageDescription and authorization checks for pedometer/activity/altimeter, nonexclusive CMMotionActivity flags with confidence, and absolute altitude as sea-level altitude on supported hardware rather than GPS-based data.",
+      "files": [],
+      "expectations": [
+        "Requires NSMotionUsageDescription for the Core Motion APIs in the plan.",
+        "Checks CMAuthorizationStatus through the relevant pedometer, activity, or altimeter manager APIs before relying on data.",
+        "Explains that CMMotionActivity flags are not mutually exclusive and should be interpreted with confidence.",
+        "Describes absolute altitude as altitude relative to sea level, not GPS-based altitude.",
+        "Mentions that absolute altitude requires supported hardware such as iPhone 12 or later or Apple Watch Series 6/SE or later.",
+        "Keeps the answer in Core Motion scope rather than turning it into a HealthKit workout or SensorKit research guide."
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "I need advanced motion guidance for a watchOS app that analyzes golf swings with batched accelerometer data, tracks AirPods head motion during coaching, and supports shallow dive depth on Apple Watch Series 10/Ultra. What setup and API pitfalls should I avoid?",
+      "expected_output": "An advanced Core Motion guide that uses CMBatchedSensorManager safely without assigning read-only frequency properties, covers CMHeadphoneMotionManager privacy/connection behavior, and sets up CMWaterSubmersionManager with availability checks, motion usage text, Shallow Depth and Pressure or full entitlement, and underwater-depth background mode.",
+      "files": [],
+      "expectations": [
+        "Uses CMBatchedSensorManager only after checking support and authorization.",
+        "Does not assign accelerometerDataFrequency or deviceMotionDataFrequency and instead treats them as reported read-only frequencies.",
+        "Mentions watchOS 10+ async batched update sequences or otherwise gates batched update APIs by availability.",
+        "Includes NSMotionUsageDescription for headphone motion and submersion access.",
+        "Uses CMHeadphoneMotionManager delegate or connection-status updates for connect/disconnect behavior.",
+        "Checks CMWaterSubmersionManager.waterSubmersionAvailable before instantiating the manager.",
+        "Distinguishes Shallow Depth and Pressure capability for 6-meter dives from the full Submerged Depth and Pressure entitlement for 40-meter dives.",
+        "Adds WKBackgroundModes with underwater-depth for dive sessions/autolaunch and does not claim only Apple Watch Ultra can support shallow depth."
+      ]
+    }
+  ]
+}

package/pipeline/skills/shared/external/core-motion/references/motion-patterns.md

@@ -5,14 +5,14 @@ exceed the main skill file's scope.
 
 ## Contents
 
-- [SwiftUI Integration with @Observable](#swiftui-integration-with-observable)
+- [SwiftUI Integration with `@Observable`](#swiftui-integration-with-observable)
 - [CMBatchedSensorManager (High-Frequency)](#cmbatchedsensormanager-high-frequency)
 - [Headphone Motion](#headphone-motion)
 - [Pedometer SwiftUI View](#pedometer-swiftui-view)
 - [Activity-Based Navigation](#activity-based-navigation)
-- [Water Submersion (watchOS Ultra)](#water-submersion-watchos-ultra)
+- [Water Submersion (watchOS)](#water-submersion-watchos)
 
-## SwiftUI Integration with @Observable
+## SwiftUI Integration with `@Observable`
 
 ### Motion Manager Service
 
@@ -64,7 +64,7 @@ struct TiltView: View {
     @State private var motionService = MotionService.shared
 
     var body: some View {
-        VStack(spacing: 20) {
+        VStack {
             Circle()
                 .fill(.blue)
                 .frame(width: 60, height: 60)
@@ -114,8 +114,10 @@ struct LevelIndicator: View {
 
 ## CMBatchedSensorManager (High-Frequency)
 
-`CMBatchedSensorManager` delivers batched data at higher frequencies (up to 800 Hz
-on Apple Watch Ultra). Available on iOS 17+ and watchOS 10+.
+`CMBatchedSensorManager` delivers batches of high-frequency accelerometer and
+device-motion data for workout-style motion analysis, such as golf swings or bat
+swings. The async update sequences are watchOS 10+ APIs; check availability and
+authorization before starting updates.
 
 ### AsyncSequence Pattern
 
@@ -131,7 +133,10 @@ final class BatchedMotionService {
     var latestAcceleration: CMAcceleration?
 
     func startBatchedAccelerometer() {
-        guard CMBatchedSensorManager.isAccelerometerSupported else { return }
+        let authorization = CMBatchedSensorManager.authorizationStatus
+        guard CMBatchedSensorManager.isAccelerometerSupported,
+              authorization != .denied,
+              authorization != .restricted else { return }
 
         updateTask = Task {
             for await batch in batchedManager.accelerometerUpdates() {
@@ -151,23 +156,31 @@ final class BatchedMotionService {
     func stop() {
         updateTask?.cancel()
         updateTask = nil
+        batchedManager.stopAccelerometerUpdates()
     }
 }
 ```
 
-### Configuring Frequency
+### Reading Frequency
 
 ```swift
 let batchedManager = CMBatchedSensorManager()
 
-// Set frequency before starting updates
-batchedManager.accelerometerDataFrequency = 200  // Hz
+// Start updates, then read the frequency the device reports.
 batchedManager.startAccelerometerUpdates()
+let reportedHz = batchedManager.accelerometerDataFrequency
 ```
 
+`accelerometerDataFrequency` and `deviceMotionDataFrequency` are read-only. Do
+not assign them; use the reported values to size buffers, throttle UI updates, or
+downsample processed results.
+
 ## Headphone Motion
 
 Track head motion using AirPods Pro / AirPods Max via `CMHeadphoneMotionManager`.
+On iOS and macOS, include `NSMotionUsageDescription`. Use connection-status
+updates when the app needs connect/disconnect events outside an active motion
+session.
 
 ```swift
 import CoreMotion
@@ -185,6 +198,7 @@ final class HeadphoneMotionService: NSObject {
         guard headphoneManager.isDeviceMotionAvailable else { return }
 
         headphoneManager.delegate = self
+        headphoneManager.startConnectionStatusUpdates()
         headphoneManager.startDeviceMotionUpdates(to: .main) { [weak self] motion, error in
             guard let self, let motion else { return }
             self.headPitch = motion.attitude.pitch
@@ -194,6 +208,7 @@ final class HeadphoneMotionService: NSObject {
 
     func stop() {
         headphoneManager.stopDeviceMotionUpdates()
+        headphoneManager.stopConnectionStatusUpdates()
     }
 }
 
@@ -341,9 +356,22 @@ final class NavigationModeService {
 }
 ```
 
-## Water Submersion (watchOS Ultra)
+## Water Submersion (watchOS)
+
+Track water depth and temperature for dive apps on supported Apple Watch
+hardware. Use `waterSubmersionAvailable` rather than hard-coding model checks:
+Apple Watch Ultra supports submersion data, and Apple Watch Series 10 supports
+the Shallow Depth and Pressure capability.
+
+Setup checklist:
 
-Track water depth and temperature for dive apps on Apple Watch Ultra.
+- Add `NSMotionUsageDescription`.
+- Add the Shallow Depth and Pressure capability for dives up to 6 meters, or
+  apply for the full Submerged Depth and Pressure entitlement for dives up to
+  40 meters.
+- Add `WKBackgroundModes` with `underwater-depth` so the app can remain
+  frontmost and eligible for dive autolaunch.
+- Check availability before instantiating `CMWaterSubmersionManager`.
 
 ```swift
 import CoreMotion
@@ -351,7 +379,7 @@ import CoreMotion
 @Observable
 @MainActor
 final class DiveService: NSObject {
-    private let submersionManager = CMWaterSubmersionManager()
+    private var submersionManager: CMWaterSubmersionManager?
 
     var isSubmerged = false
     var currentDepth: Double?
@@ -359,7 +387,9 @@ final class DiveService: NSObject {
 
     func start() {
         guard CMWaterSubmersionManager.waterSubmersionAvailable else { return }
-        submersionManager.delegate = self
+        let manager = CMWaterSubmersionManager()
+        manager.delegate = self
+        submersionManager = manager
     }
 }
 
@@ -401,5 +431,6 @@ extension DiveService: CMWaterSubmersionManagerDelegate {
 ```
 
 **Important:** `CMWaterSubmersionManager` requires the
-`com.apple.developer.submerged-shallow-depth-and-pressure` entitlement and runs
-only on Apple Watch Ultra hardware.
+Shallow Depth and Pressure capability or the full Submerged Depth and Pressure
+entitlement. If the app lacks the entitlement, the delegate receives
+`CMError.notEntitled` and no submersion data.

package/pipeline/skills/shared/external/core-nfc/SKILL.md

@@ -7,7 +7,7 @@ description: "Read and write NFC tags using CoreNFC. Use when scanning NDEF tags
 
 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.2 / iOS 26+.
+and background tag reading. Targets Swift 6.3 / iOS 26+.
 
 ## Contents
 
@@ -27,13 +27,15 @@ and background tag reading. Targets Swift 6.2 / iOS 26+.
 
 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 tag types your app reads (e.g., `NDEF`, `TAG`)
+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 presenting NFC UI.
+availability before creating NFC UI or sessions. Use the concrete reader
+session type you are about to create.
 
 ```swift
 import CoreNFC
@@ -167,13 +169,21 @@ func readerSession(
 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.
+
 ```swift
 final class TagReader: NSObject, NFCTagReaderSessionDelegate {
     private var session: NFCTagReaderSession?
 
     func beginScanning() {
+        guard NFCTagReaderSession.readingAvailable else { return }
+
         session = NFCTagReaderSession(
-            pollingOption: [.iso14443, .iso15693],
+            pollingOption: [.iso14443, .iso15693, .iso18092],
             delegate: self,
             queue: nil
         )
@@ -319,11 +329,15 @@ func processRecord(_ record: NFCNDEFPayload) {
 ## Background Tag Reading
 
 On iPhone XS and later, iOS can read NFC tags in the background without
-opening your app. To opt in:
+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.
 
-1. Add associated domains or universal links that match the URL on your tags
-2. Register your app for the tag's NDEF content type
-3. Include your app's bundle ID in the tag's NDEF record
+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`:
@@ -336,60 +350,30 @@ func scene(
     guard userActivity.activityType ==
         NSUserActivityTypeBrowsingWeb else { return }
 
-    if let message = userActivity.ndefMessagePayload {
-        for record in message.records {
-            processRecord(record)
-        }
+    let message = userActivity.ndefMessagePayload
+    guard message.records.first?.typeNameFormat != .empty else { return }
+
+    for record in message.records {
+        processRecord(record)
     }
 }
 ```
 
 ## Common Mistakes
 
-### DON'T: Forget the NFC entitlement
+### DON'T: Use stale or missing NFC entitlements
 
 Without the `com.apple.developer.nfc.readersession.formats` entitlement,
-session creation crashes at runtime.
-
-```swift
-// WRONG -- entitlement not added, crashes
-let session = NFCNDEFReaderSession(
-    delegate: self, queue: nil, invalidateAfterFirstRead: true
-)
-
-// CORRECT -- add entitlement in Signing & Capabilities first
-// Then the same code works:
-let session = NFCNDEFReaderSession(
-    delegate: self, queue: nil, invalidateAfterFirstRead: true
-)
-```
+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
 
-Attempting to create an NFC session on an unsupported device (iPad, iPod
-touch, or iPhone 6s and earlier) crashes.
+Creating an NFC session on an unsupported or restricted device fails before
+the scan UI can do useful work.
 
-```swift
-// WRONG
-func scan() {
-    let session = NFCNDEFReaderSession(
-        delegate: self, queue: nil, invalidateAfterFirstRead: true
-    )
-    session.begin()
-}
-
-// CORRECT
-func scan() {
-    guard NFCNDEFReaderSession.readingAvailable else {
-        showUnsupportedAlert()
-        return
-    }
-    let session = NFCNDEFReaderSession(
-        delegate: self, queue: nil, invalidateAfterFirstRead: true
-    )
-    session.begin()
-}
-```
+Check `NFCNDEFReaderSession.readingAvailable` or
+`NFCTagReaderSession.readingAvailable` before creating the matching session.
 
 ### DON'T: Ignore session invalidation errors
 
@@ -468,20 +452,23 @@ tag.queryNDEFStatus { status, capacity, error in
 
 - [ ] NFC capability added in Signing & Capabilities
 - [ ] `NFCReaderUsageDescription` set in Info.plist
-- [ ] `com.apple.developer.nfc.readersession.formats` entitlement configured with correct tag types
-- [ ] `NFCNDEFReaderSession.readingAvailable` checked before creating sessions
+- [ ] `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`
-- [ ] Background tag reading configured with associated domains if needed
+- [ ] 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
 
-- Extended patterns (ISO 7816 commands, multi-tag scanning, NDEF locking): `references/nfc-patterns.md`
+- Extended patterns (ISO 7816 commands, multi-tag scanning, NDEF locking): [references/nfc-patterns.md](references/nfc-patterns.md)
 - [Core NFC framework](https://sosumi.ai/documentation/corenfc)
 - [NFCNDEFReaderSession](https://sosumi.ai/documentation/corenfc/nfcndefreadersession)
 - [NFCTagReaderSession](https://sosumi.ai/documentation/corenfc/nfctagreadersession)
@@ -493,3 +480,5 @@ tag.queryNDEFStatus { status, capacity, error in
 - [Building an NFC Tag-Reader App](https://sosumi.ai/documentation/corenfc/building_an_nfc_tag-reader_app)
 - [Adding Support for Background Tag Reading](https://sosumi.ai/documentation/corenfc/adding-support-for-background-tag-reading)
 - [Near Field Communication Tag Reader Session Formats Entitlement](https://sosumi.ai/documentation/bundleresources/entitlements/com.apple.developer.nfc.readersession.formats)
+- [ISO7816 application identifiers for NFC Tag Reader Session](https://sosumi.ai/documentation/bundleresources/entitlements/com.apple.developer.nfc.readersession.iso7816.select-identifiers)
+- [ISO18092 system codes for NFC Tag Reader Session](https://sosumi.ai/documentation/bundleresources/entitlements/com.apple.developer.nfc.readersession.felica.systemcodes)

package/pipeline/skills/shared/external/core-nfc/evals/evals.json

@@ -0,0 +1,49 @@
+{
+  "skill_name": "core-nfc",
+  "evals": [
+    {
+      "id": 0,
+      "name": "entitlement-setup-review",
+      "prompt": "Review this Core NFC setup before we hand it to the iOS team. The app needs to scan NDEF tags, read ISO 7816 identity cards by AID, and read a FeliCa transit tag. The draft entitlements include com.apple.developer.nfc.readersession.formats = [\"NDEF\", \"TAG\"], NFCReaderUsageDescription, and one ISO7816 AID. What should we change or verify?",
+      "expected_output": "A source-grounded setup review that corrects stale Core NFC entitlements and covers ISO 7816 and FeliCa configuration.",
+      "files": [],
+      "expectations": [
+        "States that the current `com.apple.developer.nfc.readersession.formats` value should use `TAG` and should not include legacy `NDEF`.",
+        "Requires a non-empty `NFCReaderUsageDescription` in Info.plist.",
+        "Requires `com.apple.developer.nfc.readersession.iso7816.select-identifiers` entries for ISO 7816 AIDs.",
+        "Requires `com.apple.developer.nfc.readersession.felica.systemcodes` entries for FeliCa and says wildcard system codes are not allowed.",
+        "Tells the team to check `NFCNDEFReaderSession.readingAvailable` or `NFCTagReaderSession.readingAvailable` before creating sessions."
+      ]
+    },
+    {
+      "id": 1,
+      "name": "native-tag-reader-boundary",
+      "prompt": "Design a concise Swift Core NFC tag scanner that can read ISO 7816, ISO 15693, MIFARE, and FeliCa tags. Also call out any payment-card or multi-tag pitfalls. Keep it as implementation guidance and snippets, not a full app.",
+      "expected_output": "Implementation guidance that uses NFCTagReaderSession correctly, maps polling options to tag families, and preserves payment-card boundaries.",
+      "files": [],
+      "expectations": [
+        "Uses `NFCTagReaderSession` for native ISO 7816, ISO 15693, MIFARE, and FeliCa access.",
+        "Checks `NFCTagReaderSession.readingAvailable` before creating the session.",
+        "Maps `.iso14443` to ISO 7816-compatible and MIFARE tags, `.iso15693` to ISO 15693, and `.iso18092` to FeliCa.",
+        "Connects to the detected tag before sending protocol commands and switches over `NFCTag` cases.",
+        "Handles multiple detected tags by asking the user to remove extras and restarting polling rather than arbitrarily using every tag.",
+        "States that `NFCTagReaderSession` does not support payment-related AIDs and routes eligible EU payment use cases to `NFCPaymentTagReaderSession`."
+      ]
+    },
+    {
+      "id": 2,
+      "name": "background-tag-routing",
+      "prompt": "A product manager wants an NFC tag to wake the app in the background by putting our bundle ID and a custom content type in the NDEF record. They also asked whether a custom myapp:// URL is fine. Write the corrected iOS implementation checklist.",
+      "expected_output": "A background tag reading checklist that corrects bundle-ID/content-type misconceptions and uses URI records and universal links.",
+      "files": [],
+      "expectations": [
+        "Says background tag reading looks for an NDEF URI record with type name format `.nfcWellKnown` and type `U`.",
+        "States that if multiple URI records exist, iOS uses the first URI record.",
+        "Uses universal links with Associated Domains for app-specific routing.",
+        "States that custom URL schemes are not supported for background tag reading.",
+        "Rejects routing by bundle ID or arbitrary NDEF content type.",
+        "Handles delivery through `NSUserActivityTypeBrowsingWeb` and `NSUserActivity.ndefMessagePayload`, including an empty-record guard for non-background activities."
+      ]
+    }
+  ]
+}

package/pipeline/skills/shared/external/core-nfc/references/nfc-patterns.md

@@ -7,6 +7,7 @@ Overflow reference for the `core-nfc` skill. Contains advanced patterns that exc
 - [ISO 7816 APDU Commands](#iso-7816-apdu-commands)
 - [ISO 15693 Tag Reading](#iso-15693-tag-reading)
 - [MIFARE Tag Operations](#mifare-tag-operations)
+- [FeliCa Tag Operations](#felica-tag-operations)
 - [Multi-Record NDEF Messages](#multi-record-ndef-messages)
 - [NDEF Tag Locking](#ndef-tag-locking)
 - [SwiftUI NFC Scanner](#swiftui-nfc-scanner)
@@ -129,7 +130,9 @@ func readMiFare(
     case .ultralight:
         readMiFareUltralight(tag: tag, session: session)
     case .desfire:
-        readMiFareDESFire(tag: tag, session: session)
+        session.invalidate(
+            errorMessage: "Use app-specific DESFire commands for this card."
+        )
     case .plus:
         print("MIFARE Plus tag detected")
         session.invalidate()
@@ -160,6 +163,33 @@ func readMiFareUltralight(
 }
 ```
 
+## FeliCa Tag Operations
+
+FeliCa discovery requires `.iso18092` polling and
+`com.apple.developer.nfc.readersession.felica.systemcodes` entries in
+Info.plist. Each system code must be explicit; wildcard values are not allowed.
+
+```swift
+func readFeliCa(
+    tag: NFCFeliCaTag,
+    session: NFCTagReaderSession
+) {
+    tag.requestSystemCode { systemCodes, error in
+        guard error == nil else {
+            session.invalidate(errorMessage: "System code request failed.")
+            return
+        }
+
+        let codes = systemCodes.map {
+            $0.map { String(format: "%02x", $0) }.joined()
+        }
+        print("FeliCa system codes: \(codes.joined(separator: ", "))")
+        session.alertMessage = "FeliCa tag read successfully."
+        session.invalidate()
+    }
+}
+```
+
 ## Multi-Record NDEF Messages
 
 Build messages with multiple records of different types:
@@ -348,7 +378,7 @@ struct NFCScannerView: View {
     @State private var scanner = NFCScannerModel()
 
     var body: some View {
-        VStack(spacing: 20) {
+        VStack {
             if !scanner.isAvailable {
                 ContentUnavailableView(
                     "NFC Unavailable",