Clock Face not connecting back after Companion unloaded/disconnected

[medocity]

We are developing a Clock Face, the socket messing between Clock Face and companion is working as expected when first time installed. After unloading the companion app or disconnecting, the socket gets closed and doesn't open, even connecting the device back, resetting the Bluetooth connection.

The Clock Face we are building requires the watch to be connected to the companion. We want to send the data from Clock Face to the companion app based upon user action, so far we have not found a way to force the companion to reopen from **ahem** Face when it disconnected/unloaded.

The connection is unreliable, no idea how to improve it. I've tried everything I can think of, so any suggestions would be really helpful. 

[Guy_]

Hi @medocity -  what's your package.json setting for run in background?

[syadav]

I am facing the issue with below setting and details:

Below are the settings to run in the background.

"requestedPermissions": [

"access_internet",

"run_background",

"access_heart_rate",

"access_activity",

"access_sleep"

]

I have set the wake-up interval of 20 min to the companion application.

[medocity]

Hi @Guy_ , I have sent the background in packgage.json

requestedPermissions": [

"access_internet",

"run_background",

]

[Guy_]

@medocity- try without the run in background.

At least restarting the clock face will restart the companion.

See also companion starting.