11-13-2021 23:40 - edited 11-13-2021 23:41
11-13-2021 23:40 - edited 11-13-2021 23:41
Since some days Fitbit Studio is stuck in "Here we go, checking login".
Clearing the Firefox browser cache and restarting the browser and even the PC does nothing, it seems permanently locked, even on a phone.
It may be related to the new requesting cookies [what for?] which started recently or new ad services [possibly being blocked], or the same SSL issue affecting the OS Simulator.
When will this be fixed?
Author | ch, passion for improvement.
Answered! Go to the Best Answer.
11-15-2021 07:25
11-15-2021 07:25
Had to delete the mozilla cache and then it works.
Author | ch, passion for improvement.
11-14-2021 01:20
11-14-2021 01:20
I have the same problems, I found a possible solution by using Edge rather Chrome. Edge seems to be less sensible.
I found a lot of:
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
Another problem: Trying to install and use fitbit sdk-cli to work off-line but I could not install it. Fitbit sdk could load but not fitbit sdk-cli.
11-14-2021 01:28
11-15-2021 07:25
11-15-2021 07:25
Had to delete the mozilla cache and then it works.
Author | ch, passion for improvement.
11-16-2021 05:27
11-16-2021 05:27
Delete cache did not help for Chrome.
11-16-2021 05:35
11-16-2021 05:35
HI @jmjobin - the problem started for me when prompted for cookies, it may be related to the account login, see about removing cookies, it seemed that unrelated ones might have been an issue. Took a fair bit of messing about with settings also to get it working. Though now with the original settings, so may be toggling something helped. Also restarted the PC and browser several times.
It was also stuck logged on at one point and when the session did finally time out, then it started working by asking to login again.
Author | ch, passion for improvement.
11-16-2021 09:43
11-16-2021 09:43
@Guy_ Thank you for the followup. I think the server does not answer. The matter of facts it keep sending me 404. Maybe someone at Fitbit could be interessted to answer about these problems?
11-16-2021 09:49 - edited 11-16-2021 09:50
11-16-2021 09:49 - edited 11-16-2021 09:50
@jmjobin- Its possible they have a general problem right now.Try https://gallery.fitbit.com/clocks it's not accessible.
Author | ch, passion for improvement.
11-16-2021 10:18