Technical issues?

[jllyh]

It seems that only my sleep and heart rate values are loading today. All other stats show as "Error loading: NetworkError when attempting to fetch resource." Interestingly, the heart rate values appear to be current and updating, so there is still some connection.

[jlai]

Seems to be working for me right now. Is it still happening for you? One other user reported this, maybe some temporary Fitbit API outage?

[jllyh]

Still happening. This is what I'm seeing in my usual Firefox browser:

I just tried Chrome and Edge as well, and I get similar results.

As I noted, what strikes me as curious is that the heart rate is populating and updating as expected.

[TLeafTO]

same here!

[JimmyG1814]

Having the problem as well

[jlai]

In Chrome, could you open up the developer console (Control-Shift-J or "..." menu -> More Tools -> Developer Tools) and take a screenshot of the error logs?

[jllyh]

[jllyh]

For what it's worth, here is the take from Firefox.

[jlai]

Thanks. Unfortunately the error message doesn't tell me much. Are you able to load other pages besides the dashboard, like the activity/sleep history pages?

[jllyh]

One more bit, from Network under the GET statement that's in error:

As for your question, in History only the Sleep and Weight logs appear to be loading. I'm not sure what to expect in Activities (that's empty) and Steps do not load for any date range (even when I use Custom to back today's date out of the range).

[jllyh]

For the drop-down in History, this seems to be the pattern. If it's not working, it's red. If it IS working, it's green. If it's unmarked, I either don't use it or don't know what to expect.

[jlai]

The cloudflare one is just for stats tracking (counting how many users are using the website). OK if that one is blocked.

What I'd be looking for is on the Network tab of the inspector, errors for api.fitbit.com. Choose a GET request, not OPTIONS. Look for the Response Headers (don't screenshot the Request Headers because it has login/authorization tokens) and the Response tab (enable Raw checkbox).

(note, there may be a couple of them with the date in the URL, hover over them and pick the one that has "steps" not "sleep" or other)

[jllyh]

Sorry, I missed that.

[jllyh]

Ah, I had RAW enabled for that but you hadn't requested it. Second attempt:

[jlai]

Thanks. So this seems to be some kind of issue with the Fitbit API so I'll need to contact their developer support. Unfortunately since it's a holiday weekend in the US, I don't expect a response for a few days.

[jllyh]

Thanks for the good work. Here's hoping for a swift resolution.

[jlai]

Thanks for helping investigate with the screenshots!

[Carmapet]

Same issue for me when I opened it up.

[TLeafTO]

Same here. It started a few days ago. Chrome/Windows 10

[jlai]

Seems to be affecting all users now. Most likely, they made some internal code changes which they didn't realize would break 3rd party apps, and then rolled it out incrementally.

[TLeafTO]

I did notice it happening about three days ago but it then resolved same day.

[mscatz-9]

Looks like it's impacting all 3rd party apps. https://community.fitbit.com/t5/Third-Party-Integrations/bd-p/other-apps as well as incorrect information on the Fitbit app.

[jllyh]

I'm not able to follow the link (404 error) but I'll take your word for it.
Ah ... the text in your link is different than the link itself.
https://community.fitbit.com/t5/Third-Party-Integrations/bd-p/other-apps

[jllyh]

I'm seeing steps data! There are still several unpopulated areas of the dashboard, but it's the first improvement in days. Here's hoping that it all gets resolved soon.

[jllyh]

I'm still seeing several 500 errors. Here's hoping that those resolve themselves soon.
-edit - As of 6:47 EDT, resolved!

[TLeafTO]

Yay!!!! Fitness Dashboard is back! For me at least and I hope for you too!

[mscatz-9]

Back for me too. :-)

[TLeafTO]

Oh no, it's down again :(

[jlai]

401 is a different kind of error, usually a problem with the authentication token. Logging out and in again might help if you see that.

[TLeafTO]

..and now it's back again :)
Seems a little unstable?