10-12-2019 10:47
10-12-2019 10:47
I got an message to update my versa to latest version. I didn't realize I wouldn't be able to test my watch faces and updated the watch to 4.0.1. Now I am not able to test the watch faces on my watch.
I have never seen before where a company doesn't release support for developers even though they have released the version publically
Answered! Go to the Best Answer.
10-12-2019 15:22
10-12-2019 15:22
I've been developing for the Versa 2 for a couple weeks now and found that "fitbit/sdk v3.1.2" doesn't even support launching to the Versa 2. It complains that the build target "mira" isn't supported, which is the internal name for the Versa 2. I went to Github to look at the fitbit SDK and found an in-development version that DOES support mira, "sdk v4.0.0-pre.4" and I've been using that with fitbit's SDK CLI implementation since. Two nights ago, I got the firmware update for my Versa 2. After a little testing, it looks as though the V4 version also supports the new firmware version as well.
TL;DR: If you're using the fitbit SDK through CLI, you can specify the following build and it might work:
"devDependencies": {
"@fitbit/sdk": "4.0.0-pre.4",
"@fitbit/sdk-cli": "1.7.0"
}
10-12-2019 12:57
10-12-2019 12:57
I haven't fully thought this through, but you may be able to do it by specifying SDK 4 in your package.json. You may also need to manually install the SDK 4 beta if npm or yarn doesn't pull it in automatically.
10-12-2019 15:22
10-12-2019 15:22
I've been developing for the Versa 2 for a couple weeks now and found that "fitbit/sdk v3.1.2" doesn't even support launching to the Versa 2. It complains that the build target "mira" isn't supported, which is the internal name for the Versa 2. I went to Github to look at the fitbit SDK and found an in-development version that DOES support mira, "sdk v4.0.0-pre.4" and I've been using that with fitbit's SDK CLI implementation since. Two nights ago, I got the firmware update for my Versa 2. After a little testing, it looks as though the V4 version also supports the new firmware version as well.
TL;DR: If you're using the fitbit SDK through CLI, you can specify the following build and it might work:
"devDependencies": {
"@fitbit/sdk": "4.0.0-pre.4",
"@fitbit/sdk-cli": "1.7.0"
}
10-12-2019 17:37
10-12-2019 17:37
Thanks! That worked
10-16-2019 02:58
10-16-2019 02:58
Unfortunately this didn't work for me... I have those two latest packages and still get the same error message.
I hope I can run my app on my new Fitbit one day!
10-16-2019 17:08
10-16-2019 17:08
A funny thing happened after I answered this question on Saturday: Fitbit updated the SDK to 4.0.0! I was going to edit my initial reply, but I guess I'll just write that now you can use
"devDependencies": {
"@fitbit/sdk": "^4.0.0",
"@fitbit/sdk-cli": "1.7.0"
}
to build your apps.
All that aside, what's the error you're getting? Are you using the simulator or are you using a physcial device and phone?
10-20-2019 18:35
10-20-2019 18:35
@KrellKincaid Is it the official release of v4? I ask because Fitbit studio still doesn't have support for the Versa 2, and I haven't been able to find the official release of v4 (only the beta)
10-20-2019 19:14
10-20-2019 19:14
It's hard to say if Fitbit considers this the official release of v4. While their github account for their SDK shows that it is now v4.0.0, I haven't seen any articles, blog posts or mentions from officials indicating that v4 is actually out. I've also noticed that Fitbit Studio is starting to lag further behind the SDK and device releases. As such, I've been using an IDE (PhpStorm in this case, not free) and NodeJS to help with the development of my Versa2 compatible app.
10-21-2019 01:27
10-21-2019 01:27
We haven't officially released 4.0 yet, hence no announcement yet. There will be a blog post etc when it ships. https://community.fitbit.com/t5/SDK-Development/SDK-4-0-status/td-p/3800000