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: 

Companion app not starting

‎10-18-2017 01:29

‎10-18-2017 01:29

Hi.

I am having problems with the Companion app not starting.  Using the BART example (also tried  another app that is working for others) the companion app does not start.  There are no console messages from  companion/index.js in Fitbit Studio or on the Fitbit Android App – Sideloaded Apps.  Here the logs are empty and Status is Unavailable.  If I try to Delete Application from Sideloaded Apps I get ‘Failed to delete app’.  Developer Bridge is enabled and connected on the Ionic and the Android app. 

I have tried, along with many restarts of the phone and the Ionic:

  1. Unpair/pair the Ionic from the mobile App
  2. Clear Android Apps data and reinstall the Fitbit app.  
  3. 1 and 2 together.

This did not help.

 

I performed a Factory Reset on the Ionic along with 1 and 2 above and this temporarily resolved the issue, the BART companion app did start.  However when I make any change to the Sideloaded app and redeploy, or add another Sideloaded app the issue reoccurs and the previously working companion app will never start again.  The Factory reset is taking around 30 mins so this is not really a usable workaround. 

Any ideas? 

Thanks Lee

Ionic: 27.30.3.2

Fitbit (Android): 2.60 (2193190)

Android: 7.0 (Galaxy S8)

Best Answer
6 REPLIES 6

‎10-18-2017 13:20

‎10-18-2017 13:20

This seems to be an Ionic or Fitbit app issue as I have confirmed the same behaviour on iOS.

Best Answer
0 Votes

‎10-26-2017 00:26

‎10-26-2017 00:26

I'm having the same issues, but I'm not willing to "Factory Reset" the device again.

 

This is quite annoying...

Best Answer
0 Votes

‎10-26-2017 07:33

‎10-26-2017 07:33

I encounter something similar. Sometimes, after sideloading a clockface of mine, the companion does not start. Sometimes a sync solves it but often I need to re-sideload it and then it does work. And keeps on working. Until I use the Music app which kills the traffic between the app and the companion. Not tried a workout app yet. Will try this evening.

Best Answer
0 Votes

‎10-26-2017 09:08

In response to PNLDesign

‎10-26-2017 09:08

I used the excersise app to track a walk. No stability issue with the clockface.

Best Answer
0 Votes

‎02-05-2018 18:03

In response to PNLDesign

‎02-05-2018 18:03

Not to jump on the me too bandwagon but I am experiencing the same issues with my Galaxt S8 +. 

Best Answer

‎05-27-2018 15:57

In response to larbac

‎05-27-2018 15:57

I face the same issue. When I start the application on my fitbit ionic connected to my Galaxy S8, the companion code is not started. The only way to fix this is to open the settings and change at least one. 

 

That's quite impacting for many scenario as without the companion started i can not make any fetch from the internet. 

Best Answer