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: 

My app isn't available on multiple devices.

‎12-09-2018 11:08

‎12-09-2018 11:08

My app - Xmas Timer - should be available to both Ionic and Versa devices, and as far as I'm aware it is available to neither. It is apparently not just an issue on my end. Is there something that can be done about it? I have gone through other channels and I have not received any support.

Best Answer
0 Votes
2 REPLIES 2

‎12-09-2018 18:23

‎12-09-2018 18:23

When you go to the Gallery App Manager and click on your project, does it say (in the upper right hand corner):

 

Published

Your Clockface is available to users in the

Fitbit App Gallery

 

If not, you haven't completed the submission and publishing process.

 

If you have, what version of the SDK did you specify in your package.json file?

 

John

Best Answer
0 Votes

‎12-10-2018 04:26 - edited ‎12-10-2018 04:35

In response to Drifty26

‎12-10-2018 04:26 - edited ‎12-10-2018 04:35

 

It shows up on my phone when I search for apps named "Xmas" but says "This app cannot be installed on your device".  I'm using a Versa with the V1 firmware. Was it built for SDK V2?  Unless that version is required, try changing it to V1 and publish it again.

 

John

Best Answer
0 Votes