accessorysetupkit
dpearson2699/swift-ios-skills
Privacy-preserving Bluetooth and Wi-Fi accessory discovery and setup for iOS 18+.
What is accessorysetupkit?
AccessorySetupKit provides a system picker for discovering and configuring Bluetooth and Wi-Fi accessories without requiring broad Bluetooth permissions. Use it when you need to present users with a curated list of compatible accessories, handle pairing events, or migrate from CoreBluetooth's permission-based scanning.
- Present a system picker for Bluetooth and Wi-Fi accessory discovery
- Define discovery descriptors with service UUIDs, names, company identifiers, and SSID matching
- Handle accessory session events (added, changed, removed, pairing, setup failures)
- Support Bluetooth LE pairing, transport bridging, and HID devices
- Allow accessory renaming and authorization confirmation during setup
- Migrate legacy CoreBluetooth-paired accessories to AccessorySetupKit
How to install accessorysetupkit
npx skills add https://github.com/dpearson2699/swift-ios-skills --skill accessorysetupkit- iOS 18 or later
- Xcode with AccessorySetupKit framework available
- Info.plist configured with NSAccessorySetupSupports and relevant Bluetooth/Wi-Fi keys
- Product images (180x120 points) for display items
How to use accessorysetupkit
- 1.Configure Info.plist with NSAccessorySetupSupports (Bluetooth and/or WiFi) and matching service UUIDs, names, or company identifiers
- 2.Create an ASAccessorySession and activate it on the main thread with an event handler
- 3.Define ASDiscoveryDescriptor instances with Bluetooth service UUIDs, names, company identifiers, or Wi-Fi SSID/prefix
- 4.Create ASPickerDisplayItem instances with accessory name, product image, and descriptor
- 5.Call session.showPicker(for:) to present the system picker to the user
- 6.Handle ASAccessoryEvent callbacks (activated, accessoryAdded, accessoryChanged, accessoryRemoved, pickerSetupFailed, etc.)
- 7.After pairing, use CoreBluetooth or NetworkExtension to communicate with the accessory
Use cases
- Setting up a Bluetooth fitness tracker without requesting broad Bluetooth permissions
- Discovering Wi-Fi smart home devices by SSID prefix
- Allowing users to rename accessories during initial pairing
- Handling multiple matching devices in a carousel picker
- Migrating an existing app from CoreBluetooth permission dialogs to privacy-preserving setup
- iOS app developers building accessory pairing flows
- Smart home and IoT app developers
- Fitness and wearable app developers
- Developers migrating from CoreBluetooth to AccessorySetupKit
accessorysetupkit FAQ
No. When you declare NSAccessorySetupSupports with Bluetooth in Info.plist, the app no longer triggers the system Bluetooth permission dialog. CBCentralManager transitions to poweredOn only after at least one accessory is paired via AccessorySetupKit.
The app will crash during AccessorySetupKit discovery. All Bluetooth service UUIDs, names, and company identifiers used in discovery descriptors must be declared in Info.plist.
Yes. Pass an array of ASPickerDisplayItem instances to showPicker(for:). If multiple devices match a single descriptor, the picker displays them in a horizontal carousel.
After AccessorySetupKit pairs the accessory, hand off communication to CoreBluetooth (for Bluetooth) or NetworkExtension (for Wi-Fi) using the accessory information from the session.
The picker displays images in a 180x120 point container. Provide high-resolution images for all screen scales, use transparent backgrounds, and test in both light and dark modes.
Full instructions (SKILL.md)
Source of truth, from dpearson2699/swift-ios-skills.
name: accessorysetupkit description: "Discover and configure Bluetooth and Wi-Fi accessories using AccessorySetupKit. Use when presenting a privacy-preserving accessory picker, defining discovery descriptors for BLE or Wi-Fi devices, handling accessory session events, migrating from CoreBluetooth permission-based scanning, or setting up accessories without requiring broad Bluetooth permissions."
AccessorySetupKit
Use the iOS 18+ system picker for privacy-preserving Bluetooth/Wi-Fi accessory discovery and authorization, then hand off communication to CoreBluetooth or NetworkExtension.
Contents
- Setup and Entitlements
- Discovery Descriptors
- Presenting the Picker
- Event Handling
- Bluetooth Accessories
- Wi-Fi Accessories
- Migration from CoreBluetooth
- Common Mistakes
- Review Checklist
- References
Setup and Entitlements
Info.plist Configuration
Add these keys to the app's Info.plist:
| Key | Type | Purpose |
|---|---|---|
NSAccessorySetupSupports | [String] | Required. Array containing Bluetooth and/or WiFi |
NSAccessorySetupBluetoothServices | [String] | Service UUIDs the app discovers (Bluetooth) |
NSAccessorySetupBluetoothNames | [String] | Bluetooth names or substrings to match |
NSAccessorySetupBluetoothCompanyIdentifiers | [String] | Two-byte Bluetooth company identifiers |
The Bluetooth-specific keys must match the values used in ASDiscoveryDescriptor.
If the app uses identifiers, names, or services not declared in Info.plist, the
app crashes during AccessorySetupKit discovery. For Wi-Fi accessories, include
WiFi in NSAccessorySetupSupports and match the descriptor's SSID rule.
No Bluetooth Permission Required
When an app declares NSAccessorySetupSupports with Bluetooth, creating a
CBCentralManager no longer triggers the system Bluetooth permission dialog.
The central manager's state transitions to poweredOn only when the app has
at least one paired accessory via AccessorySetupKit.
Discovery Descriptors
ASDiscoveryDescriptor defines the matching criteria for finding accessories.
The system matches scanned results against all rules in the descriptor to
filter for the target accessory.
Bluetooth Descriptor
import AccessorySetupKit
import CoreBluetooth
var descriptor = ASDiscoveryDescriptor()
descriptor.bluetoothServiceUUID = CBUUID(string: "12345678-1234-1234-1234-123456789ABC")
descriptor.bluetoothNameSubstring = "MyDevice"
descriptor.bluetoothRange = .immediate // Only nearby devices
A Bluetooth descriptor needs at least one of bluetoothCompanyIdentifier or
bluetoothServiceUUID. Add narrower matchers as needed:
bluetoothNameSubstringwith a company identifier or service UUIDbluetoothManufacturerDataBlobandbluetoothManufacturerDataMaskwith a company identifier; blob and mask must have the same lengthbluetoothServiceDataBlobandbluetoothServiceDataMaskwith a service UUID; blob and mask must have the same length
Wi-Fi Descriptor
var descriptor = ASDiscoveryDescriptor()
descriptor.ssid = "MyAccessory-Network"
// OR use a prefix:
// descriptor.ssidPrefix = "MyAccessory-"
Supply either ssid or ssidPrefix, not both. The app crashes if both are set.
The ssidPrefix must have a non-zero length.
Bluetooth Range
Control the physical proximity required for discovery:
| Value | Behavior |
|---|---|
.default | Standard Bluetooth range |
.immediate | Only accessories in close physical proximity |
Support Options
Set supportedOptions on the descriptor to declare the accessory's capabilities:
descriptor.supportedOptions = [.bluetoothPairingLE, .bluetoothTransportBridging]
| Option | Purpose |
|---|---|
.bluetoothPairingLE | BLE pairing support |
.bluetoothTransportBridging | Bluetooth transport bridging |
.bluetoothHID | Bluetooth HID device |
Presenting the Picker
Creating the Session
Create and activate an ASAccessorySession to manage discovery lifecycle. Wait for .activated before reading session.accessories or presenting the picker:
import AccessorySetupKit
final class AccessoryManager {
private let session = ASAccessorySession()
func start() {
session.activate(on: .main) { [weak self] event in
self?.handleEvent(event)
}
}
private func handleEvent(_ event: ASAccessoryEvent) {
switch event.eventType {
case .activated:
// Session ready. Check session.accessories for previously paired devices.
break
case .accessoryAdded:
guard let accessory = event.accessory else { return }
handleAccessoryAdded(accessory)
case .accessoryChanged:
// Accessory properties changed (e.g., display name updated in Settings)
break
case .accessoryRemoved:
// Accessory removed by user or app
break
case .invalidated:
// Session invalidated, cannot be reused
break
@unknown default:
break
}
}
}
Showing the Picker
Create ASPickerDisplayItem instances with a name, product image, and
discovery descriptor, then pass them to the activated session:
func showAccessoryPicker() {
var descriptor = ASDiscoveryDescriptor()
descriptor.bluetoothServiceUUID = CBUUID(string: "ABCD1234-0000-1000-8000-00805F9B34FB")
guard let image = UIImage(named: "my-accessory") else { return }
let item = ASPickerDisplayItem(
name: "My Bluetooth Accessory",
productImage: image,
descriptor: descriptor
)
session.showPicker(for: [item]) { error in
if let error {
print("Picker failed: \(error.localizedDescription)")
}
}
}
The picker runs in a separate system process. It shows each matching device as a separate item. When multiple devices match a given descriptor, the picker creates a horizontal carousel.
Setup Options
Configure picker behavior per display item:
var item = ASPickerDisplayItem(
name: "My Accessory",
productImage: image,
descriptor: descriptor
)
item.setupOptions = [.rename, .confirmAuthorization]
| Option | Effect |
|---|---|
.rename | Allow renaming the accessory during setup |
.confirmAuthorization | Show authorization confirmation before setup |
.finishInApp | Signal that setup continues in the app after pairing |
Product Images
The picker displays images in a 180x120 point container. Best practices:
- Use high-resolution images for all screen scale factors
- Use transparent backgrounds for correct light/dark mode appearance
- Adjust transparent borders as padding to control apparent accessory size
- Test in both light and dark mode
Event Handling
Event Types
The session delivers ASAccessoryEvent objects through the event handler:
| Event | When |
|---|---|
.activated | Session is active, query session.accessories |
.accessoryAdded | User selected an accessory in the picker |
.accessoryChanged | Accessory properties updated (e.g., renamed) |
.accessoryRemoved | Accessory removed from system |
.invalidated | Session invalidated, create a new one |
.migrationComplete | Migration of legacy accessories completed |
.pickerDidPresent | Picker appeared on screen |
.pickerDidDismiss | Picker dismissed |
.pickerSetupBridging | Transport bridging setup in progress |
.pickerSetupPairing | Bluetooth pairing in progress |
.pickerSetupFailed | Setup failed |
.pickerSetupRename | User is renaming the accessory |
.accessoryDiscovered | New accessory found (custom filtering mode) |
Coordinating Picker Dismissal
When the user selects an accessory, .accessoryAdded fires before
.pickerDidDismiss. To show custom setup UI after the picker closes, store the
accessory on the first event and act on it after dismissal:
private var pendingAccessory: ASAccessory?
private func handleEvent(_ event: ASAccessoryEvent) {
switch event.eventType {
case .accessoryAdded:
pendingAccessory = event.accessory
case .pickerDidDismiss:
if let accessory = pendingAccessory {
pendingAccessory = nil
beginCustomSetup(accessory)
}
@unknown default:
break
}
}
Bluetooth Accessories
After an accessory is added via the picker, use CoreBluetooth to communicate.
The bluetoothIdentifier on the ASAccessory maps to a CBPeripheral.
import CoreBluetooth
func handleAccessoryAdded(_ accessory: ASAccessory) {
guard let btIdentifier = accessory.bluetoothIdentifier else { return }
// Create CBCentralManager — no Bluetooth permission prompt appears
let centralManager = CBCentralManager(delegate: self, queue: nil)
// After poweredOn, retrieve the peripheral
let peripherals = centralManager.retrievePeripherals(
withIdentifiers: [btIdentifier]
)
guard let peripheral = peripherals.first else { return }
centralManager.connect(peripheral, options: nil)
}
Key points:
CBCentralManagerstate reaches.poweredOnonly when the app has paired accessories- Scanning with
scanForPeripherals(withServices:)returns only accessories paired through AccessorySetupKit - No
NSBluetoothAlwaysUsageDescriptionis needed when using AccessorySetupKit exclusively
Wi-Fi Accessories
For Wi-Fi accessories, the ssid on the ASAccessory identifies the network.
Use NEHotspotConfiguration from NetworkExtension to join it:
import NetworkExtension
func handleWiFiAccessoryAdded(_ accessory: ASAccessory) {
guard let ssid = accessory.ssid else { return }
let configuration = NEHotspotConfiguration(ssid: ssid)
NEHotspotConfigurationManager.shared.apply(configuration) { error in
if let error {
print("Wi-Fi join failed: \(error.localizedDescription)")
}
}
}
Because the accessory was discovered through AccessorySetupKit, joining the network does not trigger the standard Wi-Fi access prompt.
Migration from CoreBluetooth
Apps with existing CoreBluetooth-authorized accessories can migrate them to
AccessorySetupKit using ASMigrationDisplayItem. This is a one-time operation
that registers known accessories in the new system.
func migrateExistingAccessories() {
guard let image = UIImage(named: "my-accessory") else { return }
var descriptor = ASDiscoveryDescriptor()
descriptor.bluetoothServiceUUID = CBUUID(string: "ABCD1234-0000-1000-8000-00805F9B34FB")
let migrationItem = ASMigrationDisplayItem(
name: "My Accessory",
productImage: image,
descriptor: descriptor
)
// Set the peripheral identifier from CoreBluetooth
migrationItem.peripheralIdentifier = existingPeripheralUUID
// For Wi-Fi accessories:
// migrationItem.hotspotSSID = "MyAccessory-WiFi"
session.showPicker(for: [migrationItem]) { error in
if let error {
print("Migration failed: \(error.localizedDescription)")
}
}
}
Migration rules:
- If
showPickercontains only migration items, the system shows an informational page instead of a discovery picker - If migration items are mixed with regular display items, migration happens only when a new accessory is discovered and set up
- Do not initialize
CBCentralManagerbefore migration completes — doing so causes an error and the picker fails to appear - The session receives
.migrationCompletewhen migration finishes
Common Mistakes
| Mistake | Fix |
|---|---|
| Descriptor identifiers are absent from Info.plist | Declare every Bluetooth service, name, and company identifier before presenting the picker. |
Both ssid and ssidPrefix are set | Choose exactly one matching strategy. |
| CoreBluetooth starts before migration completes | Wait for .migrationComplete, then create CBCentralManager. |
| Picker appears without explicit user intent | Present it only from a user action. |
| An invalidated session is reused | Create, activate, and retain a new ASAccessorySession. |
Review Checklist
-
NSAccessorySetupSupportsadded to Info.plist withBluetoothand/orWiFi - Session activated before calling
showPicker - Event handler uses
[weak self]to avoid retain cycles - All
ASAccessoryEventTypecases handled, including@unknown default - Product images use transparent backgrounds and appropriate resolution
-
bluetoothIdentifierorssidfromASAccessoryused to connect post-setup - Accessory removal events handled to clean up app state
References
- Extended patterns (custom filtering, batch setup, removal handling, error recovery): references/accessorysetupkit-patterns.md
- AccessorySetupKit framework
- ASAccessorySession
- ASDiscoveryDescriptor
- ASPickerDisplayItem
- ASAccessory
- ASAccessoryEvent
- ASMigrationDisplayItem
- Discovering and configuring accessories
- Setting up and authorizing a Bluetooth accessory
- Meet AccessorySetupKit — WWDC24
Related skills
More from dpearson2699/swift-ios-skills and the wider catalog.

activitykit
Build real-time Lock Screen and Dynamic Island Live Activities for iOS with ActivityKit.

adattributionkit
Privacy-preserving ad attribution for iOS 17.4+ measuring conversions without exposing user data.

alarmkit
Build iOS/iPadOS alarms and countdown timers with Lock Screen, Dynamic Island, and Apple Watch integration.

app-clips
Build lightweight iOS App Clips with invocation routing, experience configuration, and full-app handoff.

app-intents
Expose iOS app actions to Siri, Shortcuts, Spotlight, widgets, Control Center, and Apple Intelligence via App Intents.

app-store-optimization
Optimize App Store listings for search visibility and conversion with keyword strategy, metadata, and page variants.