SDK IOS

John

Hello,
Im using the FBeacon iOS SDK (v2.1.2.4) and need clarification on background reconnection.
Our use case: the app scans once in the foreground via FBBluetoothBrowser and obtains an FBPeripheralItem. Later, after the app has been suspended or terminated by iOS, it is relaunched in the background (via significant location change / region monitoring). At that point we need to connect directly to the previously known Feasycom device without scanning, since reliable BLE scanning is not possible while the app is killed.
Our questions:

Does the SDK support connecting to a previously discovered device using a saved CoreBluetooth identifier (i.e. the equivalent of CBCentralManager.retrievePeripherals(withIdentifiers + connect()), without a new scan? If so, which API?
Does the internal CBCentralManager used by FBBluetoothBrowser support CoreBluetooth State Restoration (CBCentralManagerOptionRestoreIdentifierKey / willRestoreState? Can we configure a restoration identifier so iOS relaunches the app on a connection event?

FAE_Gavin

John Regarding the background reconnection feature, the current FBeacon iOS SDK v2.1.2.4 does not support direct reconnection to a previously discovered device in the background without scanning.

In addition, the SDK currently does not support CoreBluetooth State Restoration, including:

CBCentralManagerOptionRestoreIdentifierKey
centralManager(willRestoreState)

Therefore, the workflow you described (foreground scanning → app suspended/terminated → background wake-up → direct reconnection using the previously saved peripheral identifier) is not supported by the current SDK.

For applications requiring advanced background BLE management, you may need to implement the related BLE connection logic using Apple's native CoreBluetooth framework directly.

John

Thank you for your quick and detailed response regarding the SDK's background reconnection limitations.
Based on your recommendation to use Apple's native CoreBluetooth framework for advanced background BLE management I observed the following behavior:
When I write the PIN "000000" the write succeeds but the device disconnects shortly after (CBError Code=7 — "The specified device has disconnected from us") and the connection drops.

// In peripheral(_:didDiscoverCharacteristicsFor:error:)
// after discovering FFF0 service characteristics:

let pinData = "000000".data(using: .utf8)!
peripheral.writeValue(pinData, for: fff2Characteristic, type: .withoutResponse)

Could you clarify what the recommended approach is for connecting to the beacon using CoreBluetooth while maintaining a stable connection?
Additionally, is there a recommended hybrid approach(CoreBluetooth and SDK) to achieve our workflow (app suspended/terminated → background wake-up → direct reconnection)?
If you have any sample code or reference implementations demonstrating the recommended connection lifecycle and background reconnection strategy, I would greatly appreciate it.

FAE_Gavin

John Regarding the connection stability issue after writing the PIN, this behavior is related to the BLE connection management implemented with Apple's CoreBluetooth framework.

As mentioned previously, the current FBeacon iOS SDK does not support background reconnection, CoreBluetooth State Restoration, or customized BLE connection lifecycle management. Therefore, we are unable to provide a recommended implementation or sample code for this specific workflow.

For advanced background BLE connection scenarios, please refer to Apple's CoreBluetooth framework documentation and implement the connection logic based on your application requirements.