React-native-ble-plx: Using BLE in background on Android

[keyz23]

Hi everyone, I use this library on my Android App, but I need to use also BLE in background! It's possible to do on Android Device with this module?
Thank you

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[njdullea]

Hey @keyz23 did you ever get an answer?

[curest0x1021]

I need to get the BLE signals even though the app is in the background on both of iOS and Android devices.
@keyz23 Did you solve the background issue? If you already solved this problem please let me know the solution.

Thanks.

[ezranbayantemur]

Any update?

[dariuszseweryn]

On Android one needs to implement a Foreground Service to keep the Application process running. You can find more info on that using Google.

[ezranbayantemur]

On Android one needs to implement a Foreground Service to keep the Application process running. You can find more info on that using Google.

Thank you for your quick response.
I haven't try but does react-native-background-task package handles foreground service implementation?

[dariuszseweryn]

I haven't try but does react-native-background-task package handles foreground service implementation?

I am not familiar with this library

[jordan-tpz]

On Android one needs to implement a Foreground Service to keep the Application process running. You can find more info on that using Google.

@dariuszseweryn If I want to keep the connection with my BLE device in background on Android, I understood I have to create a specific task (using foreground service).

My question is : do you think I should use the connectToDevice() function in this task when I connect my BLE device with my app ? (and I could remove this task when I would like to disconnect my BLE device)
But, another solution : maybe quite simply I should create the BleManager instance within this task ?

[dariuszseweryn]

It all depends on how you want to architecture your app. This topic is very wide and subjective — personally I tend to have a single object managing the connection.