help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Messaging not ready after app has been closed and companion app has been unloaded

‎03-10-2022 13:25 - edited ‎03-10-2022 13:26

‎03-10-2022 13:25 - edited ‎03-10-2022 13:26

I am experiencing an issue with a watch face I am developing on my Versa 3. I installed the watch face by sideloading it onto the phone via command line interface. The watchface uses a companion app to request weather information from my android 11 phone half an hour. In general it works as expected but in the night time the logs for the sideloaded app say:

 

10.03.2022 00:24:58: App wurde auf dem Gerät geschlossen. Companion wird in 3 Sekunden entladen…
10.03.2022 00:25:01: Companion wird entladen …
10.03.2022 00:25:03: Companion entladen

 

 

As you can see the app is closed - probably due to inactivity I guess - and therefore the companion is being unloaded. Problems start in the morning when both the companion and the watch face have a pretty hard time to get together again.

 

Here you can see that my watch face is getting multiple "Messaging not ready" errors between eight and ten o'clock:

FLav0ured_1-1646946276888.jpeg

 

While the companion app on my phone is regularly woken up through a wake interval during the same time:

 

10.03.2022 08:10:02: Companion wird entladen …
10.03.2022 08:10:10: Companion entladen
10.03.2022 08:24:14: Loaded and evaluated: file:///android_asset/bootstrap.js
10.03.2022 08:24:15: Activating wake interval.
10.03.2022 08:24:15: Started due to wake interval.
10.03.2022 08:24:15: Up and running.
10.03.2022 08:24:15: Loaded and evaluated: file:///data/user/0/com.fitbit.FitbitMobile/app_companions/339a2411-3207-42e3-8733-a0bc4f4038d9/0x0ad6428ae32af34b/companion.js
10.03.2022 08:24:15: Companion wird bis [wakeUp] gestartet, Companion wird in 15 Sekunden entladen…
10.03.2022 08:24:16: Already awake.
10.03.2022 08:24:16: Already awake.
10.03.2022 08:24:16: Already awake.
10.03.2022 08:24:36: Companion wird entladen …
10.03.2022 08:24:47: Companion entladen
10.03.2022 08:39:56: Loaded and evaluated: file:///android_asset/bootstrap.js
10.03.2022 08:39:56: Activating wake interval.
10.03.2022 08:39:56: Started due to wake interval.
10.03.2022 08:39:56: Up and running.
10.03.2022 08:39:56: Loaded and evaluated: file:///data/user/0/com.fitbit.FitbitMobile/app_companions/339a2411-3207-42e3-8733-a0bc4f4038d9/0x0ad6428ae32af34b/companion.js
10.03.2022 08:39:56: Companion wird bis [wakeUp] gestartet, Companion wird in 15 Sekunden entladen…
10.03.2022 08:39:56: Already awake.
10.03.2022 08:39:56: Already awake.
10.03.2022 08:39:56: Already awake.
10.03.2022 08:39:56: Already awake.
10.03.2022 08:40:47: Companion wird entladen …
10.03.2022 08:40:49: Companion entladen
10.03.2022 08:55:05: Loaded and evaluated: file:///android_asset/bootstrap.js
10.03.2022 08:55:05: Activating wake interval.
10.03.2022 08:55:05: Started due to wake interval.
10.03.2022 08:55:05: Up and running.
10.03.2022 08:55:05: Companion wird bis [wakeUp] gestartet, Companion wird in 15 Sekunden entladen…
10.03.2022 08:55:05: Already awake.
10.03.2022 08:55:05: Already awake.
10.03.2022 08:55:05: Already awake.
10.03.2022 08:55:57: Companion wird entladen …
10.03.2022 08:55:59: Companion entladen
10.03.2022 09:12:17: Loaded and evaluated: file:///android_asset/bootstrap.js
10.03.2022 09:12:17: Activating wake interval.
10.03.2022 09:12:17: Started due to wake interval.
10.03.2022 09:12:17: Up and running.
10.03.2022 09:12:17: Loaded and evaluated: file:///data/user/0/com.fitbit.FitbitMobile/app_companions/339a2411-3207-42e3-8733-a0bc4f4038d9/0x0ad6428ae32af34b/companion.js
10.03.2022 09:12:17: Companion wird bis [wakeUp] gestartet, Companion wird in 15 Sekunden entladen…
10.03.2022 09:12:19: Already awake.

 

 

The thing is synchronizing data between smartwatch and phone is never an issue. However the only way to get both companion app and watch face to recognize each other again is forcing the watch face to restart by opening the settings on the smartwatch and switching back to the watch face.

 

I used to see similar behaviour on my Fitbit Ionic back in the days. Hence I was adding a logging screen and a wake interval. I had hoped that this issue would have been solved in the new SDK so I migrated my project but as it seems the issue still persists.

 

What am I supposed to do to solve this issue? What else can I do other than implementing a wake interval? Could this be an issue of sideloading the watch face? Would it help to release the watch face and install it "normally"?

Best Answer
0 Votes
2 REPLIES 2

‎03-11-2022 01:06

‎03-11-2022 01:06

Hi @FLav0ured  - possibly a sideload issue, try creating a Gallery Application Manager project and load it via a private link.

 

See also Ensure Companion starts

 

The only sure way is to do what you do, force the watch face to restart for now.

 

There is an option in the package.json to run companion in background this may have an affect in your case.

Author | ch, passion for improvement.

Best Answer

‎03-11-2022 07:01

In response to Guy_

‎03-11-2022 07:01

Thank you very much @Guy_ . I will do so and report back.

Best Answer