11-05-2018 19:33
11-05-2018 19:33
Hi, sometimes after the app starts I get the sessionClosed exception from the messaging API. This usually happens when I go from clock face to start another app, terminate the app and come back to watch face. Because of this I am not able to communicate with watch from phone.
I can see that before sessionClosed, the onopen callback was called. How can I handle this situation? I am using iOS on my phone.
Best Answer11-06-2018 00:02
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
11-06-2018 00:02
Just try initiating a message from the device, it should try to establish a connection.
Best Answer11-06-2018 07:08
11-06-2018 07:08
Thanks for suggestion, I tried moving some initial messages on device, but messaging api is definitely buggy
So from logs I can see the following is being executed from device
messaging.peerSocket.send({
command: 'settings'
});But the companion never receives any message and I see no error on device. Note: This only happens some times, but it does happen
Best Answer