Fitbit Studio never loads

[skeletom]

As the title says, it is basically impossible to access Fitbit studio. I have probably less than a 20% success rate getting the page to load. It hangs on:

Here we go

Checking login...

For hours at a time. In the rare instance that it actually times out, it will say "Projects couldn't load" and the console will reveal that it gets a 404 to the project API. But sometimes, this exact same process works! So clearly the project API url exists.

Is there any way to develop for Fitbit offline? I have lost days of productivity to the inability to load the IDE.

I have tried Chrome v108, Firefox and Edge. No change in behavior across any browser. I have also tried launching Fitbit Studio in Incognito mode, hoping that it was due to some sort of caching issue, but the behavior is the same there, too.

[skeletom]

It finally timed out for me again, so here is the full error as produced by the Inspector console.

GET https://studio.fitbit.com/api/projects 404

"API request to 'https://studio.fitbit.com/api/projects failed with 404 "

t {response: Response, message: "API request to 'https://studio.fitbit.com/api/projects failed with 404 ", name: 'APIError', stack: "APIError: API request to 'https://studio.fitbit.co…h (https://accounts.fitbit.com/client.js:1:11156)"}

[ASegaloff]

I have also tried multiple computers/browsers/incognito modes.  I can work around the login by logging into fitbot.com first, but them am stuck with "Projects couldn't load"  Debugger log from Chrome on Login Issue is: 

console.js:35 SSO: initialising

DevTools failed to load source map: Could not load content for https://corporate-webapps.fitbit.com/fsc-web-client/channels/prod/fsc.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

vendor-fdd8d08edc98754150fcb3e6c30beb81.js:5 [Violation] 'setTimeout' handler took 50ms

[Gondwana]

---

@skeletom wrote:

...Is there any way to develop for Fitbit offline?...

---

CLI. It's not entirely off-line, but doesn't depend on Studio. You'll still need to be able to authenticate.

[ChunkySoup703]

What you are stating has been the norm for me for months and I usually have to refresh several times to get it to work or just give up and come back another day. I have tried 4 different browsers and the same result. Today it is extra special broken apparently. No matter what I do, what browser I use, what computer I use I get "That didn't work. Projects Failed to Load. Please try again" and this error log - t {response: Response, message: "API request to 'https://studio.fitbit.com/api/projects failed with 404 ", name: 'APIError', stack: "APIError: API request to 'https://studio.fitbit.co…h (https://accounts.fitbit.com/client.js:1:11156)"}

[Gondwana]

I'm getting that too at the moment, and I usually don't. I think something is down.

[Gorbs]

Finally got in here, everyone else start working or was I just lucky?

[Dlewis145]

I 100% agree.... the whole fitbit studio is super hard to just open; why is their authentication system such garbage.

I managed to get into the system (switched to Edge), but then none of the files worked and it eventually failed to show a 'Projects failed to load' screen.

[skeletom]

Just lucky, it seems. 

[odeezee]

Glad it is not just me. Just started using Studio.Fitbit last week.

[Dlewis145]

I second your API error.

[Gondwana]

It seems to be working for me now. Fixed?

[odeezee]

It's working on my end. I had a build issue at first but right now its completely working

[Dlewis145]

It worked for me 2min after I posted the error... But was still super
hit/miss whether it was throwing error messages. It would fail to load
something, but then work when I hit refresh.

Working or not, it still seems far from bulletproof reliability.

[ASegaloff]

Still not working for me over multiple browsers.

[backlogfrog]

Same deal with me, tried logging out, refreshing page, restarting computer, different browsers...I can't seem to replicate a cause so I have no idea why it works sometimes and why it doesn't others.

It also fails at saving files before finishing the build, for ~5 minutes, so I have to walk away before I drill through my monitor.