core-bluetooth

To scan and connect to BLE peripherals, initialize CBCentralManager, filter discovered devices by service UUIDs, and invoke connect. You then discover services and characteristics to read, write, or subscribe to notifications.

Core Bluetooth state restoration preserves central and peripheral connections across app relaunches by assigning restoration identifiers to managers. The system reinitializes managers and replays pending events, allowing seamless recovery of BLE sessions.

Yes, Core Bluetooth supports background BLE scanning and advertising when you add the Bluetooth and central/peripheral background modes keys to Info.plist. Background operations are limited to service-filtered scanning and persistent connections.

To implement a peripheral role, configure CBPeripheralManager with your custom service and characteristic UUIDs. You can then advertise these services, publish characteristics, and respond to incoming read, write, and subscription requests.

Characteristic read or write operations fail when properties are mismatched. You must check characteristic properties to verify if they support read, write, notify, or indicate actions before attempting data exchange.

The best way to manage BLE reconnection is to utilize state restoration identifiers alongside central manager state monitoring. This handles disconnected peripherals and automatically triggers reconnection when target devices become available.