11-18-2020 13:52
11-18-2020 13:52
I have seen a few of these questions, but I can't find the os system to check (I've gone into the fitbit.com dashboard, nothing comes up for version, but my watch says 35.70.714), I've updated the app and tried to change the package.json (even going as far as deleting and remaking it).
I'm creating it for the versa 2, using sdk 4.2 and only using versa 2 as the target, I've tried giving all permissions and only those needed....
I did use code I originally wrote for a versa, but there's nothing specific about the target in the code that I can find - perhaps there are different imports or functions? I can show code if needed, I'm just not sure what else to check - I've tried all the previous answers and still the same error above.
Answered! Go to the Best Answer.
11-18-2020 14:14
11-18-2020 14:14
70.7.14 is SDK 4.1. The best option would be to update the firmware on your watch to SDK 4.2, which is probably 71.6.19 or later. This should be offered automatically if your phone and Fitbit app are fairly recent. It might take a day or two if your watch is brand new.
If you can't upgrade, rebuild your app targeting SDK 4.1; something like
"@fitbit/sdk": "~4.1.0"
Assuming you're using CLI, you'll need something like npm i to install the relevant node modules.
11-18-2020 14:14
11-18-2020 14:14
70.7.14 is SDK 4.1. The best option would be to update the firmware on your watch to SDK 4.2, which is probably 71.6.19 or later. This should be offered automatically if your phone and Fitbit app are fairly recent. It might take a day or two if your watch is brand new.
If you can't upgrade, rebuild your app targeting SDK 4.1; something like
"@fitbit/sdk": "~4.1.0"
Assuming you're using CLI, you'll need something like npm i to install the relevant node modules.
01-14-2021 16:30
01-14-2021 16:30
Thanks Though this is scary. My fit bit Versa is at 32.70.8.0 and it claims to be up to date, Though I get the msg
4:21:47 PM Side load of app failed. Connected device does not support API version requested by app.
4:21:57 PM App Started
4:22:11 PM App Closed
4:22:13 PM Launch complete - duration foregrounding(2156ms), first paint(152ms), total(2309ms).
and/or no display change on phone
Just the simple clock face example (versa, SDK 4.2)
01-14-2021 17:39
01-14-2021 17:39
70.8.0 is SDK 4.1.3, I think. Your watch firmware is not up to date. This might be because the Fitbit app on your phone isn't up to date, and that might be because your phone's operating system isn't up to date, and that might be because your phone's hardware isn't up to date. 🙂
01-14-2021 18:42
01-14-2021 18:42
Gondwana,
Thanks for the response. It turns out after about hours on line with support about my so called outdated phone OS that is the problem. I was presented two options get a new phone, we all have money to spend, or use a friends device so that their information can be collect. It's what we live with when we use technology to sell newer item, disposable income.
Thanks Again