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: 

Newbie issues

‎12-13-2021 05:12

‎12-13-2021 05:12

Hello all,

I thought I'd have a go at making a basic "always on" clock for the Fitbit Versa 3. I've opened the SDK in the browser as instructed, then downloaded the simulator (Fitbit OS Simulator-latest-0.9.2.exe) as suggested.

There ends the progress.

I open the simulator and log in and set the studio.fitbit.com to look for the simulator, it says it is connected. 

I've downloaded and built the sample project for clock face and it gives me errors:

1. This project is being built without a companion component. Create a file named companion/index.ts or companion/index.js to add a companion component to your project.

2. This project is being built without a settings component. Create a file named settings/index.tsx, settings/index.ts, settings/index.jsx or settings/index.js to add a settings component to your project.

I've read that these folders are optional so I assume the errors can be ignored BUT the run button is greyed out on the SDK so I cannot run anything. 

What is wrong?

 

I'm a software engineer so I know my way about files and SDK's but this gives no hint as to what could be wrong. Grrr.

Best Answer
0 Votes
5 REPLIES 5

‎12-13-2021 06:08

‎12-13-2021 06:08

I should also add that I have the simulator says The Device Bridge is disconnected and also that the Companion Bridge is connected to a debugger.

In the SDK web page whenever I hover over the Run icon it displays "Connect a device in order to run your app".

 

I can run the app on a real device but I don't want to yet, I'd like to get the simulator set up.

Best Answer
0 Votes

‎12-13-2021 06:17

In response to petesky

‎12-13-2021 06:17

Ignore all, it seems this is related to the Simulator SSL problem as already reported. I didn't think this was related. 

Problem has gone.

Best Answer

‎12-13-2021 11:28

In response to petesky

‎12-13-2021 11:28

Glad to hear it.

Bear in mind that the 'always-on' API is only usable on real hardware by developers who have been specifically approved to do so by Fitbit. Even they can't install AOD products on their watches (eg, for testing) before they've been approved by Fitbit.

Peter McLennan
Gondwana Software
Best Answer

‎12-27-2021 18:08

In response to petesky

‎12-27-2021 18:08

Do you think you could run me through how you solved it? Im having troubles with this too

Best Answer
0 Votes

‎12-27-2021 18:16

In response to Ineedhelp_

‎12-27-2021 18:16

Nevermind i was missing some code lol

Best Answer
0 Votes