Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How to create a project on CLI using 4.3.0

ANSWERED

I installed @Fitbit/sdk 4.3.0 and the associated CLI, however using this command 

npx create-fitbit-app <project-name>

creates a fitbit project for the latest SDK even though I'm only developing for the 4.3.0.
How can I properly create a app on 4.3.0 using CLI

PS. Yes I know you can use Fitbit Studio to create it, but that won't support SDK 4.3.0 soon, so I'm ignoring answers that require the fitbit studio 

Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions

You can use an optional argument to create-fitbit-app to specify the SDK version: see here. I'm not sure of the exact syntax required for <alternative-package>.

Or, create an app for the default SDK and adapt it.

Or, don't use create-fitbit-app and create/install the files manually.

Peter McLennan
Gondwana Software

View best answer in original post

Best Answer
6 REPLIES 6

You can use an optional argument to create-fitbit-app to specify the SDK version: see here. I'm not sure of the exact syntax required for <alternative-package>.

Or, create an app for the default SDK and adapt it.

Or, don't use create-fitbit-app and create/install the files manually.

Peter McLennan
Gondwana Software
Best Answer

The command to create for 4.3.0 is

npx create-fitbit-app <project-name> --sdk-version 4.3.0

 

Thank you

Best Answer

There seems to be problems with builds using 4.3.0 in Studio, so probably in CLI as well.

 

There may be a bug with the introduction of the SDK 6.0 release, as it seems to generate larger and incorrect code using 4.3.0.

 

Having considerably trimmed an existing project it still exceeds memory whereas the original loaded fine [built with 4.2.0].

 

So it looks like development for pre Versa 2 watches has ended already!

Author | ch, passion for improvement.

Best Answer

What problems?

 

Best Answer
0 Votes

@SomeDeveloper  See 

Author | ch, passion for improvement.

Best Answer

Fair enough, shouldn't take long, just another SDK 4.3.1 and probably a Fitbit os update

Best Answer