Issue: I cannot permanently close the connection to a Socket S550 (BLE device)

[jimc-jpgreze]

Your Socket Mobile Developer ID

94ad3dd4-8474-ea11-a811-000d3a3786fc

Environment

OS Version: iOS 26.4
CaptureSDK version: react-native-capture: 2.0.24
Device: iPad 9th generation

Description

I am upgrading to version 2.x of the React Native CaptureSDK, and while I can connect to the S550 using the new CaptureHelper, I cannot permanently disconnect from it. To disconnect, I'm calling the setDisconnect() method on the CaptureHelperDevice, and I hear the S550 say "disconnected", and I get the onDeviceRemoval event, but then the S550 immediately reconnects and I get a new onDeviceArrival event. I have not figured out a way to permanently disconnect from the device. When I used version 1.x of the SDK, I would clear the favorite, but this is no longer supported. Please advise.

Steps to Reproduce

1. Create an instance of CaptureHelper.
2. Discover the S550 using captureHelper.addBluetoothDevice(BluetoothDiscoveryMode.BluetoothLowEnergy);
3. Upon invocation of onDiscoveredDevice(discoveredDevice), connect using captureHelper.connectDiscoveredDevice(discoveredDevice);
4. The app will receive a onDeviceArrival(s550Device) event indicating the S550 is connected.
5. Now attempt to disconnect using s550Device.setDisconnect()
6. The S550 will briefly disconnect, the app will receive an onDeviceRemoval event, and the S550 will immediately reconnect and the app will receive a onDeviceArrival event again.

Expected Behavior

The expected behavior is for the S550 to remain disconnected after calling the setDisconnect() method, so it can be connected to another host.

Actual Behavior

The actual behavior is that the S550 does not remain disconnected after the setDisconnect() call, it immediately reconnects.

Additional Context

No response

[cyrille-socket]

Hello @jimc-jpgreze

thanks for submitting this issue. We'll try to reproduce it and fix it in the next release.

Tell me what you expect after the device has been disconnected. Do you want to reconnect automatically at the next app launch? Why are you doing this disconnect device so I can understand exactly how to address your issue? Or another scenario that you'd like to share?

Best regards
Cyrille

[jimc-jpgreze]

Hello Cyrille,

The main issue is less with iOS and more with Android. With iOS, the CaptureSDK will disconnect and reconnect the scanner for you when the app is put into the background and then returned to the foreground. Android doesn't do this. And I've found that if I put the app into the background long enough, when it is finally returned to the foreground, it no longer receives scan events. So the only solution I can think of is to disconnect the scanner when the app is put into the background, and reconnect when its back in the foreground. If there is something I am missing, let me know.

Thanks,
Jim

[cyrille-socket]

Hello @jimc-jpgreze,

I need more info like a code snippet of what you're doing to handle the events and open the CaptureSDK.

Then, each native CaptureSDK (iOS and Android) handles the lifecycle of the connection. But normally you don't have to disconnect by yourself. The CaptureSDK handles the connection by disconnecting and reconnecting when transitioning background/foreground.

[cyrille-socket]

Hello @jimc-jpgreze

also, can you provide me the version of Companion that you're using please? Since we have released CaptureSDK 2.0 on iOS and Android, you need Companion 4.0.

If you want more info, please check our newsletter here: http://links.socketmobile.com/m/1/71527447/02-b26071-2c4c21341cde4a0c97e6202517a0b803/2/738/e081840f-5762-45b7-8fdb-b9a8d7ce56f7.