Cannot Reconnect

[michaelpeterlee]

Disconnect then Reconnect fails with connection error; You can only connect to a Device once in an app session.

This is a regression from 7.3.0 with Capacitor 8; We can connect/disconnect many times without connection error.

Steps to reproduce:

1. requestLEScan();
2. disconnect(id);
3. connect(id,..);
4. disconnect(id);
5. connect(id,..);

Plugin version:

• @capacitor-community/bluetooth-le: [8.0.2]

Smartphone (please complete the following information):

• iPhone 13 pro iOS26.2

[steinerjakob]

@michaelpeterlee I think it's the same as mine #799
Cloning the options object before passing it to the requestLEScan function did work for me.

[peitschie]

Please try this again with either version 7.3.2 or 8.0.3. I've fixed the issue that @steinerjakob identified, so hopefully your problem here is resolved as well.

[michaelpeterlee]

Thanks @peitschie, the issue still exists and may be worse. After disconnect(), the host device still acts like it's still connected as no other phones can see the device anymore.

[peitschie]

@michaelpeterlee are you able to capture the logs from Xcode and the browser during one of these cycles?

[michaelpeterlee]

Will do in the next few days when I revisit. XCode To Native -> BluetoothLe logs may reveal a problem with disconnect().

[michaelpeterlee]

XCodeLog.txt

[peitschie]

Hi @michaelpeterlee

Having a look at these logs, it appears that service discovery is timing out on the second connection attempt and leaving the plugin in an inconsistent state:

⚡️  To Native ->  BluetoothLe connect 41473684
⚡️  BluetoothLe - Connecting to peripheral <CBPeripheral: 0x15629eae0, identifier = BEB6F0E3-0EF6-A5DB-E93F-F3E5A715BCE5, name = MyDevice 113211, mtu = 0, state = disconnected>
⚡️  [log] - scan rendering
⚡️  BluetoothLe - Connected to device <CBPeripheral: 0x15629eae0, identifier = BEB6F0E3-0EF6-A5DB-E93F-F3E5A715BCE5, name = MyDevice 113211, mtu = 23, state = connected>
⚡️  BluetoothLe - Resolve connect|BEB6F0E3-0EF6-A5DB-E93F-F3E5A715BCE5 Successfully connected.
⚡️  BluetoothLe - Connected to peripheral. Waiting for service discovery.
⚡️  BluetoothLe - didDiscoverServices
⚡️  BluetoothLe - didDiscoverCharacteristicsFor 1 2
⚡️  BluetoothLe - didDiscoverCharacteristicsFor 2 2
XPC connection invalid
⚡️  BluetoothLe - Reject connect Connection timeout
ERROR MESSAGE:  {"errorMessage":"Connection timeout","message":"Connection timeout"}
⚡️  [error] - {"errorMessage":"Connection timeout","message":"Connection timeout"}

I'll need to dig a bit further, as it's not obvious to me why this might have regressed since 7.3.1.

While I'm looking further, can you see if removing the second call to BleClient.initialize (you seem to be doing this on every loop) makes any change to the behaviour here?

[michaelpeterlee]

async enable() {
        try {
            let isEnabled = await BleClient.isEnabled();
            if (!isEnabled) {
                await BleClient.initialize();
            }
            isEnabled = await BleClient.isEnabled();
            if (!isEnabled) {
                throw new Error("Bluetooth is not enabled, or not supported");
            }
        } catch (e) {
            throw new Error("Bluetooth Unavailable");
        }
}

This implementation is not working; I added isEnable check before initialize().
Note that other phones cannot see the BLE device once it has been disconnected either, which points to disconnect not working properly for some reason. I will have more time tomorrow for this.

[peitschie]

Hi @michaelpeterlee

isEnabled is unrelated to the initialization state. initialize should only be called once after the application is launched, and never needs to be invoked again (assuming the user access the Bluetooth permissions).