"Projects failed to load" message while opening Fitbit studio

[m4rc3lv]

I'm getting the message "Projects failed to load" message while opening Fitbit studio. Deleting cookies/data in the browser doesn't help. Browser Chrome and Firefox both show the message.
Anybody else experiencing this same issue now?

[AnGue]

Same here...

[Guy_]

Hi @m4rc3lv @AnGue - this can be an account access issue.

You may be able to resolve it by logout and in to GAM, then try Studio again.

[m4rc3lv · Accepted solution]

It seemed a server issue because usign a newly isntalled browser (same as logging out and logging in again) did not even work. After the guys at Fitbit fixed their server everything worked again.

[Athar]

Still some server issues.

Sometimes I can get into my projects, but then, can't load a file/save it (and then, reloading the project page get the same issue as your first post).

Fitbit servers need to be fixed, since a few weeks, it's really unstable.

[ASegaloff]

Still not working for me. Multiple browsers.  

[Athar]

Yeah, definitively not an issue on client side, but on server side.

I just discovered a "bug" in my clockface, can't even build it to fix it... annoying.

[Athar]

Seems to be back online, for now... but for how many time ? mystery.

[Guy_]

Hi @Athar @ASegaloff @AnGue @m4rc3lv - while there may have been an issue it still works fine for me.

Did you try clearing the browser cache and the logout and in to GAM, then try Studio again?

[Athar]

I might be new to this forum (dev on studio since 2018), I know it was a server issue for sure.

Maybe because I'm also an IT engineer 😉

Clearly, from time to time :

- Studio didn't load at all, throwing the error the author post (so we pass the login step with success)

- Studio is in a loading loop checking for login/credential status.

For this one, most of the time, a refresh and we pass it.

- A modification inside a file is not saved (getting the "try again" pop-up). Most of the time, it pass on the second attempt, sometimes need more.

- Building failed (the server part who handle the compile system might be in an overload state). Same, need to insist to get it working if the server is alive behind.