Apps and Companion apps, conflict?

[WauloK]

I have a Clockface and an App (clockface in testing). Both have Companion apps. Both the Clockface and App send the same "command" to their Companion apps.

It seems that if both have the same command, I have a problem where the peer socket doesn't open. I'm wondering if this is because the Companion apps are both listening for the same command and get confused? Or are there separate channels open for them to listen to?

If I have a different command for each, both the Clockface and App can communicate successfully (mostly) with their Companion app.

[JonFitbit]

The name of the command should not be relevant, each app/companion is sandboxed.

When one app is launched, the other should be terminated anyway.

Can you provide a cut down example app, so I can see how your companion is structured?

Thanks

[WauloK]

Email sent 🙂

[WauloK]

Also, I installed a Clockface I wrote which worked fine.

I installed an App I wrote and both worked.

I installed a second App and now the clockface app won't run and I get "Clock error. Go to the Fitbit mobile app and try another clock".

Both Apps work fine. But the Clockface is gone with the above error and the Clockface companion app is gone from the Fitbit Android app.