Device Status has seen as Unavailable from companion

[my8bit]

When I was testing my clockface for some long period (a week or so) I noticed that eventually, companion stops recognizing the clockface. From the Developer Menu -> My clockface I see that:

Status: Unavailable
Settings: Unavailable

And after this happened I can not reach the companion from the device. When I try to connect from CLI to the device I see logs from the device show that I could not send any message because of peerSocketState === 1. I see no logs from the message open even so I can conclude that the open message event never happens for some reason.

I tried to unload clockface, load some another app and go back to the clock face. Still got an error when the device is trying to connect to the companion. From companion, in this case, I see the logs only from the companion side and it's only:

AppLifecyceMessage: terminateApp
AppLifecyceMessage: launchApp
and so on

My assumption is that this might be because of some memory leak or something. But on the other hand, I unload and load an app. Also, I was thinking about the connectivity issues - but other apps send and receive data as expected. So it's not a general connectivity issue but only for my clock face. So taking all that I'm a bit puzzled.

My question is - why this situation might happen and how to debug in this case. I didn't try the system memory API yet, to see if there are any issues, but do not want to install the app again but rather try to debug somehow the current state. What would you suggest to me?

[JonFitbit]

Can you tell us a bit more about your setup?

• Mobile phone OS
• Fitbit app version
• Device firmware version

Thanks!

[my8bit]

Hi @JonFitbit !
Yes, gladly

Device firmware: 32.70.7.14
iOS version: 13.3
Fitbit app version: 3.13 (919)

I noticed that I got a bunch of messages from the Fitbit app with next content:
We are unable to update/install one or more apps. Please try again

What I've tried is to login into the device's REPL and check the memory throught system API's, everything looks normal.

Also, I have to mention that I used to use the Fitbit application from Android mobile. Since this issue apeard I uninstalled it with the hope that it fixes the issue. But it didn't.

One small clarification about the first message. I do see only
AppLifecyceMessage:launchApp / terminateApp 
- messages from companion logs, despite that I have my own console.logs in the companion app.

[my8bit]

@JonFitbit Issue still persists. Is there any additional information that I can provide to help you? Generally speaking, from my side, I want to make sure that this issue is caused by the platform, not by my clockface. Is it possible to confirm, at this stage, that such behavior could not be caused by the clock face itself but rather is a system issue