Post not yet marked as solved
Adding the bluetooth-central UIBackgroundMode solved this issue for us in debug mode. The problem is that we fail to upload the app since there because of missing com.apple.developer.bluetooth-central-background entitlement.
The problem is that we didn't find a way to add this entitlement in the portal or in Xcode.
I opened a DTS and waiting for a reply.
Post not yet marked as solved
What OS and device do you use? Multiple CBCentralManagers works for me on iOS, watchOS and macOS.
Post not yet marked as solved
You can even use multiple CBCentralManager instaces in order to communicate with the same peripheral
Post not yet marked as solved
The relevant frameworks are:ExternalAccessory for MFI accessorties.CoreBluetooth for BLE devices and for BR/EDR devices that supports GATT.Check if the HID bluetooth profile can fit your need. In that case. If I am not mistaken you will not need to use any framework
Post not yet marked as solved
You can add your own UUID in the "manufacturer data"
Post not yet marked as solved
Try State Preservation and Restorationhttps://developer.apple.com/library/archive/qa/qa1962/_index.html
Post not yet marked as solved
The picker views only unpaired MFi devices.The EAAcessory framework does not provide an API to connect to a device.The MFi device can initiate connection to the iPhone - so if your device can supports GATT you can use CoreBluetooth to connect to the device and ask it to connect over iAP.Another options is the "bridging" feature mentioned in the last WWDC session about CoreBluetooth - with this feature the iPhone connects to the classic bluetooth device when it discover this device over BLE.
Post not yet marked as solved
I think that the CBCharacteristic object is no longer valid after the disconnection. Check what is value after step 4. I believe that the value would still be isNotifying == YES.
Post not yet marked as solved
Only the main queue is guarenteed to run on a specific thread (and therefore a specific runloop). You need to create an NSThread, start it and use its runloop.
Post not yet marked as solved
Maybe the "Database Hash" and "Service Changed" characteristics can prevent this data from being cached by the OS
Post not yet marked as solved
The peripheral can specify that it has no I/O capabilities. In this case the Apple device will not request any pairing key
Post not yet marked as solved
maybe Settings > General > Reset > Reset Network Configurations will help.
Post not yet marked as solved
The key is there but there is no documentation yethttps://developer.apple.com/documentation/corebluetooth/cbconnectperipheraloptionenabletransportbridgingkey?language=objc
Post not yet marked as solved
CoreBluetooth doesn't scan for classic bluetooth devices. It only allows your app to be notified when a classic bluetooth connects to the iPhone.
Post not yet marked as solved
This feature (waking up the app when something happen over BLE) is not supported in watchOS.Communicating over BLE when the app is in the background and not suspended works even without this background mode
