skills/audioaccessorykit/SKILL.md
Support audio accessory features like automatic switching using AudioAccessoryKit. Use when implementing automatic audio routing for paired accessories, registering audio accessory configuration from the container app, updating placement or connected audio source identifiers from an app extension, or handling AccessoryControlDevice capabilities and errors.
npx skillsauth add dpearson2699/swift-ios-skills audioaccessorykitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Automatic audio switching support and intelligent audio routing inputs for third-party audio accessories. Enables companion apps to register audio accessory configuration with the system, and app extensions to report placement and connected source changes that help the system switch audio output. Available iOS 26.4+ / iPadOS 26.4+.
Beta-sensitive. AudioAccessoryKit is new in iOS 26.4. Re-check current Apple documentation before relying on specific API details.
AudioAccessoryKit builds on top of AccessorySetupKit. The accessory must first
be paired via AccessorySetupKit before it can be registered for audio features.
The central type is AccessoryControlDevice, which registers a
Configuration from the container app and applies ongoing configuration updates
from the app extension.
ASAccessory object.import AccessorySetupKit
import AudioAccessoryKit
| Platform | Minimum Version | |---|---| | iOS | 26.4+ | | iPadOS | 26.4+ |
After pairing via AccessorySetupKit, register the accessory from the container
app by passing an AccessoryControlDevice.Configuration that describes the
capabilities and any initial state the accessory supports:
let accessory: ASAccessory // Obtained from AccessorySetupKit pairing
let configuration = AccessoryControlDevice.Configuration(
devicePlacement: .offHead,
deviceCapabilities: [.audioSwitching, .placement]
)
try await AccessoryControlDevice.register(accessory, configuration)
Registration activates the specified capabilities and gives the system the configuration it needs to participate in audio routing decisions.
In the app extension, access the device's current configuration using the
static current(for:) method:
let device = try AccessoryControlDevice.current(for: accessory)
let currentConfig = device.configuration
This returns the AccessoryControlDevice instance associated with the paired
ASAccessory. The device exposes both the accessory reference and the
current configuration. Apple marks current(for:) as app-extension-only.
In the app extension, push configuration changes to the system with
update(_:). Only update fields for capabilities that were declared during
registration:
let device = try AccessoryControlDevice.current(for: accessory)
var config = device.configuration
config.devicePlacement = .onHead
try await device.update(config)
The update call is async and can throw AccessoryControlDevice.Error on
failure. Apple marks update(_:) as app-extension-only.
Automatic audio switching lets the system intelligently route audio output to the correct device based on placement and connected sources.
Declare the .audioSwitching capability in the registration configuration:
let configuration = AccessoryControlDevice.Configuration(
deviceCapabilities: [.audioSwitching]
)
try await AccessoryControlDevice.register(accessory, configuration)
For Apple's automatic switching workflow, include both .audioSwitching and
.placement when the accessory can report placement:
let configuration = AccessoryControlDevice.Configuration(
devicePlacement: .offHead,
deviceCapabilities: [.audioSwitching, .placement]
)
try await AccessoryControlDevice.register(accessory, configuration)
AccessoryControlDevice.Capabilities is an option set with two members:
| Capability | Purpose |
|---|---|
| .audioSwitching | Device supports automatic audio switching |
| .placement | Device can report its physical placement |
Both capabilities can be combined. Do not declare .placement unless the
accessory can keep the system updated with real placement state.
Report the physical position of the accessory from the app extension to help the system make routing decisions. Update placement whenever the accessory detects a position change.
AccessoryControlDevice.Placement defines four cases:
| Placement | Meaning |
|---|---|
| .inEar | Accessory is seated in the ear (e.g., earbuds) |
| .onHead | Accessory is on the head (e.g., headband headphones) |
| .overTheEar | Accessory is over the ear (e.g., over-ear headphones) |
| .offHead | Accessory is not being worn |
let device = try AccessoryControlDevice.current(for: accessory)
var config = device.configuration
config.devicePlacement = .inEar
try await device.update(config)
Common transitions:
.offHead to .onHead or .inEar when the user puts on the accessory.onHead or .inEar to .offHead when removedFor accessories that connect to multiple Bluetooth devices simultaneously, inform the system from the app extension which devices are connected. This lets the system route audio from the appropriate source.
Provide the Bluetooth address of connected devices as Data:
let device = try AccessoryControlDevice.current(for: accessory)
var config = device.configuration
let primaryBTAddress = Data([0x12, 0x34, 0x56, 0x78, 0x9A, 0xBC])
config.primaryAudioSourceDeviceIdentifier = primaryBTAddress
let secondaryBTAddress = Data([0xAB, 0xCD, 0xEF, 0x01, 0x23, 0x45])
config.secondaryAudioSourceDeviceIdentifier = secondaryBTAddress
try await device.update(config)
Update these identifiers when the Bluetooth connection state changes (new device connects, existing device disconnects).
AccessoryControlDevice.Configuration contains all configurable state:
| Property | Type | Purpose |
|---|---|---|
| deviceCapabilities | Capabilities | Declared device capabilities |
| devicePlacement | Placement? | Current physical placement |
| primaryAudioSourceDeviceIdentifier | Data? | Primary connected Bluetooth device address |
| secondaryAudioSourceDeviceIdentifier | Data? | Secondary connected Bluetooth device address |
In the app extension, inspect the device's declared capabilities through its configuration:
let device = try AccessoryControlDevice.current(for: accessory)
let caps = device.configuration.deviceCapabilities
if caps.contains(.audioSwitching) {
// Device supports automatic audio switching
}
if caps.contains(.placement) {
// Device reports physical placement
}
Read the current placement to determine if the accessory is being worn:
let device = try AccessoryControlDevice.current(for: accessory)
if let placement = device.configuration.devicePlacement {
switch placement {
case .inEar, .onHead, .overTheEar:
// Accessory is being worn
break
case .offHead:
// Accessory is not being worn
break
@unknown default:
break
}
}
AccessoryControlDevice.Error covers failure cases during registration and
updates:
| Error | Cause |
|---|---|
| .accessoryNotCapable | Accessory does not support the requested capability |
| .invalidRequest | Request parameters are invalid |
| .invalidated | Device registration has been invalidated |
| .unknown | An unspecified error occurred |
Handle errors from registration and update calls:
let configuration = AccessoryControlDevice.Configuration(
devicePlacement: .offHead,
deviceCapabilities: [.audioSwitching, .placement]
)
do {
try await AccessoryControlDevice.register(accessory, configuration)
} catch let error as AccessoryControlDevice.Error {
switch error {
case .accessoryNotCapable:
// Accessory hardware does not support requested capabilities
break
case .invalidRequest:
// Check registration parameters
break
case .invalidated:
// Coordinate container-app registration again
break
case .unknown:
// Log and retry
break
@unknown default:
break
}
}
// WRONG -- no ASAccessory from a completed AccessorySetupKit pairing
try await AccessoryControlDevice.register(unknownAccessory, configuration)
// CORRECT -- use the ASAccessory from a completed pairing session
session.activate(on: .main) { event in
if event.eventType == .accessoryAdded, let accessory = event.accessory {
Task {
let configuration = AccessoryControlDevice.Configuration(
deviceCapabilities: [.audioSwitching]
)
try await AccessoryControlDevice.register(accessory, configuration)
}
}
}
// WRONG -- registers placement but never updates it
let registration = AccessoryControlDevice.Configuration(
deviceCapabilities: [.audioSwitching, .placement]
)
try await AccessoryControlDevice.register(accessory, registration)
// System never receives placement data, reducing switching accuracy
// CORRECT -- extension updates placement when state changes
let device = try AccessoryControlDevice.current(for: accessory)
var config = device.configuration
config.devicePlacement = .offHead
try await device.update(config)
// WRONG -- set audio source identifiers once and never update
config.primaryAudioSourceDeviceIdentifier = someAddress
try await device.update(config)
// Device disconnects, but system still thinks it's the primary source
// CORRECT -- update identifiers when connections change
func onDeviceDisconnected() {
var config = device.configuration
config.primaryAudioSourceDeviceIdentifier = nil
Task { try await device.update(config) }
}
// WRONG -- ignores invalidation, keeps using stale device reference
try await device.update(config) // Throws .invalidated, unhandled
// CORRECT -- catch invalidation and ask the container app to re-register
do {
try await device.update(config)
} catch AccessoryControlDevice.Error.invalidated {
await notifyContainerAppToRegisterAgain(accessory)
}
AccessorySetupKit and AudioAccessoryKit importedregister(_: _:) with AccessoryControlDevice.Configurationcurrent(for:) and update(_:).placement capability accompanied by ongoing placement updatesAccessoryControlDevice.Error cases handled, including @unknown defaultupdate(_:) calls use try await and handle errorsdevelopment
Implement, review, or improve data visualizations using Swift Charts. Use when building bar, line, area, point, pie, donut, or iOS 26 3D charts; when adding chart selection, scrolling, annotations, axes, scales, legends, or foregroundStyle grouping; when plotting functions with BarPlot, LinePlot, AreaPlot, PointPlot, Chart3D, or SurfacePlot; or when creating heat maps, Gantt charts, grouped bars, sparklines, threshold lines, or spatial visualizations.
data-ai
Select, implement, or migrate between app architecture patterns for Apple platform apps. Use when choosing between MV (Model-View with @Observable), MVVM, MVI, TCA (The Composable Architecture), Clean Architecture, VIPER, or Coordinator patterns; when evaluating architecture fit for a feature's complexity; when migrating from one pattern to another; or when reviewing whether an app's current architecture is appropriate. Scoped to Apple-platform patterns using Swift 6.3, SwiftUI, and UIKit.
development
Apply Swift API Design Guidelines to name, label, and document Swift APIs. Covers argument label rules (prepositional phrase rule, grammatical phrase rule, first-label omission), mutating/nonmutating pair naming (-ed/-ing participle pattern, form- prefix, sort/sorted, formUnion/union), side-effect naming (noun for pure, verb for mutating), documentation comment structure (summary by declaration kind, O(1) complexity rule), clarity at call site, role-based naming, protocol naming (-able/-ible/-ing), default arguments over method families, casing conventions, and terminology. Use when designing new Swift APIs, reviewing naming and argument labels, writing documentation comments, or refactoring for call site clarity.
development
Implement, review, or improve in-app purchases and subscriptions using StoreKit 2. Use when building paywalls with SubscriptionStoreView or ProductView, processing transactions with Product and Transaction APIs, verifying entitlements, handling purchase flows (consumable, non-consumable, auto-renewable), implementing offer codes or promotional/win-back/introductory offers, managing subscription status and renewal state, setting up StoreKit testing with configuration files, or integrating Family Sharing, Ask to Buy, refund handling, and billing retry logic.