Studio. Build apps easily from anywhere with the new Fitbit Studio.

[Andre_o]

My decision to purchased a Fitbit Sense was finalised by this statement in the title above that is advertised on the the Fitbit dev site! https://dev.fitbit.com/ 
I have installed and reinstalled, uninstalled and reinstalled so many times. The simulator will not accept a new project regardless of how many times I uninstall and reinstall. When I look for help in the community, The Fitbit representatives mention the same solutions that do not work. Make sure you are logged in! Change the certificate with cacert.pem etc.etc.... None of these solutions work, the tutorials and information is so limited, the Q&A appears to cover none of the answers that so many complain about on the dev community with a level of clarity. I have spent weeks on this and now give up. I am so disappointed.

[Guy_]

Hi @Andre_o  - it is most likely the certificate problem.

To be sure, when you start a watch in the simulator, and go to the settings tab are both options at the top ok?

If not then it could be that studio and the simulator are not logged in on the same account or the certificate has not been replaced after installing the simulator.

See the topic about SSL pinned at the top for how to resolve it.

[MarioDings]

Let's break this problem into pieces.

1. You can install the simulator.
   1. On what OS?
   2. With what account is the simulator logged in?
2. You can start studio.
   1. On what OS, browser. (I think not relevant)
   2. With what account is studio logged in?
   3. Does studio see the simulator?
   4. When you connect your physical device to the developer bridge, does it show ( after refresh) in studio?
   5. when you connect your phone to the bridge, does it show?

It may help us find the problem.

For me, I run studio on a chromebook and I run the simulator on a Windows computer. Not neccessarily on the same network.

[Andre_o]

Hi Guy, 

Apologies for the delay, unfortunate Achilles injury.

Thank you very much for your response. I did previously replace the cacert.pem with no improvement. However, I uninstalled the simulator and started again, replacing the cacert.pem and I got a little further. Thank you.

[Andre_o]

Hi Mario,

Apologies for the delay.

• i7 laptop with Windows 10 64 bit.
• Google Chrome browser version:  Version 99.0.4844.74 (Official Build) (64-bit).
• Login ????
• Studio does see the simulator, but the run button is greyed out. 
• The run button only becomes active when I connect my device to the bridge.
• The simulator will only show if I reinstall which I have done many times.
• The simulator will only pick up an old project and not the current project.
• Both the Studio and simulator were logged in.
• I am using Window 10 desktop Fitbit app and Android 10 Samsung mobile.

I removed the login details above in case this is public. Since uninstalling and reinstalling the simulator again. Then replacing the cacert.pem, I managed to get connected this time.
Then I had a connection issue with both the Device Bridge debugger and the Companion Bridge debugger. Following this I had a series of errors that I tackled one by one. App cluster & Developer ID's, then other issues arose such as having to create companion/index.js and settings/index.jsx directories and files. Then there were build issues because there was nothing to say what needed to be in these files. I placed some JS in the files which improved the errors, but I am assuming that I need to import an npm package into the companion/index.js file such as settings, is this correct? If so, where do I find more information on importing packages and do they vary depending on whether its an app, a clock face etc?
Many thanks.

[Guy_]

Hi @Andre_o  - all you need is Studio and optionally OS Simulator, because with the device bridge on the watch you can also load directly to the watch with Run. (You may need developer bridge on the phone too if using a companion).

Sometimes the OS Simulator gets disconnected and it may be necessary to switch to a different watch in Settings. (And back again possibly)

Make sure you loaded the cert to all the watch model folders and that the type of watch you select matches the definition you choose in the packag.json file, for the SDK version and watch.

[MarioDings]

@Andre_o  ,

Dit you take a look at Github?

https://github.com/Fitbit

There's a lot to get you going.

You' re having a lot of issues and asking a lot of questions .

I guess you 're able to connect your simulator to studio.