"Server connection error" from watch connecting to dev bridge

[FLGMwt]

I started playing around with Studio and my watch this morning. I successfully connected and deployed the sample clock face and deployed a few additional times with modifications. I started trying out the settings API by adding a settings/index.jsx and companion/index.js. After fixing a compilation error that resulted in a failed import (forgot to import messaging in the app/index.js), I tried build/deploying again. At that point, my watch became disconnected (red in Studio). I tried to reconnect from my watch (settings/dev bridge). When I try to connect now, it says "connecting to WiFi", "Connecting to Server", then briefly flashes "Connected to Server" before displaying "Server connection error". 

Is there any way to get more detail about my error? Phone is Nexus6P btw.

[FLGMwt]

Not *really* a solution, but I closed out of the app in Studio and came back and tried again and it worked. I don't know if that's what fixed it or the intermittent issues happened to stop at the same time. 

[DeepPurple]

I was having a similar issue and was getting rather frustrated. It would connect once and then I'd battle for 20 minutes to get connected again.

I realize that the WiFi signal in my home office is fine for phone / laptop but the Ionic shows very poor signal. Switching to a hidden network which is just outside my home office that I use primarily for my IOT devices resolved the issue and I now have a stable and consistent connection to Fitbit Studio.

The advice for people experiencing this issue is move as close as possible to your WiFi router / AP and see if that resolves the problem.

[Pietero]

---

@DeepPurple wrote:

The advice for people experiencing this issue is move as close as possible to your WiFi router / AP and see if that resolves the problem.

---

My advice to people without a strong wifi signal is to make an hotspot on your phone phone and lay in next to your watch. This workaround works for me.

[SHGrade]

---

@Pietero wrote:

---

@DeepPurple wrote:

The advice for people experiencing this issue is move as close as possible to your WiFi router / AP and see if that resolves the problem.

---

My advice to people without a strong wifi signal is to make an hotspot on your phone phone and lay in next to your watch. This workaround works for me.

---

Can you clarify, if I make my phone a hotspot, it turns of wifi, meaning I am no longer connected to the same network, and my phone will not appear in studio?

Maybe that is a phone problem, I turned my laptop into a mobile hotspot and did not lose either.

[Pietero]

If I turn on the hotspot the network does appear in the list in the fitbit app. I think it is a Phone thing. I use Android nougat.

Both my phone and Ionic are showing in the fitbit studio. I guess the phone and Ionic don't need to be on the same network in order to appear in studio. When you create an hotspot, your phone and ionic do have the same IP address. Maybe someone from Fitbit can clarify whether it is necessary that the ionic and the phone have the same IP address.

[JonFitbit · Accepted solution]

We've discovered and fixed some issues with the developer bridge, and the fixes will be included in the next update.

Hang in there!

PS: The phone and Ionic both connect to wifi independently, so they each have their own IP address.

[mikeatmarvel]

It's now 05/22/2020 and there was a recent update to the Fitbit App May 19, 2020 Version 3.21

We are running into this error with my users as I have used the Fitbit SDK into my app CARROT.  I am wondering if this issue has returned.

https://twitter.com/CarrotWellness/status/1263822869978546176/photo/1 

[Pietero]

hi @mikeatmarvel ,

Was having the same issue. Just restored.. seemed like a problem on the fitbit authentication service.