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 Code running in simulator, but not when loaded to a Versa 2 and iPhone

‎08-12-2020 14:12

‎08-12-2020 14:12

Hi guys.

I’m finding that my companion code will work when in the simulator, but when it’s on my Versa 2 and iPhone it won't run at all...

 

Any ideas why?

 

Cheers

Best Answer
0 Votes
2 REPLIES 2

‎08-12-2020 14:28

‎08-12-2020 14:28

Permissions?

Stick a console.log('x') at the start of companion index.js and see if it starts.

Peter McLennan
Gondwana Software
Best Answer
0 Votes

‎08-12-2020 14:32

In response to Gondwana

‎08-12-2020 14:32

@Gondwana already did that. That's how I confirmed that the companion code is not even running the first line.

 

I'm a little confused with the permissions tho. So on my Fitbit Studio, I select the permissions required but when I load onto my versa and phone I don't get any messages asking if I allow the permissions... Is that normal? 

 

 

Best Answer
0 Votes