Simulator SSL Problem

[JonFitbit]

We are aware of an issue with SSL certificates that will impact use of the developer bridge with the simulator. We will be issuing a fix for the simulator in the comings days, in the meantime please use a physical device for development.

[BeatYT · Accepted solution]

I found a way to fix it for windows!

(You need to repeat these steps for every devices)

1: Navigate to %localappdata%\Programs\@fitbitsimulator\resources\static\devicesim\win

2: Go to the device folder you want to fix (for example atlas)

3: replace cacert.pem with the one below

 Here is the cert: cacert.pem 

For mac users: https://community.fitbit.com/t5/SDK-Development/Simulator-SSL-Problem/m-p/5003210/highlight/true#M16... 

[tanmoythander]

Any workaround for MacOS?

[JonFitbit]

Looks like you can do this same in:

/Applications/Fitbit OS Simulator.app/Contents/Resources/static/devicesim/mac/atlas.app/Contents/Resources

[tanmoythander]

It worked! Thank you so much.

[JJUK]

Where did this certificate come from and why does this work and not the one shipped with the app?

[BeatYT]

I took the cert from https://027-v3-api-soa.fitbit.com/ 

On chrome:

padlock icon -> Connection is secure -> Certificate is valid -> Details  -> Export

[nkmb]

I would love to trust this answer but https://027-v3-api-soa.fitbit.com/ is a 404 right now and I'm not going to install a random cert linked from a discord server. 😓 Nothing personal BeatYT but a working link to the source would be appreciated.

[BeatYT]

---

@nkmb wrote:

I would love to trust this answer but https://027-v3-api-soa.fitbit.com/ is a 404 right now and I'm not going to install a random cert linked from a discord server. 😓 Nothing personal BeatYT but a working link to the source would be appreciated.

---

It doesn't really matter that it's a HTTP 404, the connection is still https and you can view the certificate from the padlock icon.

I'm not asking you to install it, it is just going to be used to verify the connection to https://027-v3-api-soa.fitbit.com/ . Also, if the cert would be mine, it wouldn't work since it wouldn't be the cert that Fitbit's Server use. Also, the discord server is not a random one, its the fitbit discord server.

The cert is root trusted, to view it, simply rename the file extension to .cer and open it (for windows)

[BeatYT]

https://www.thesslstore.com/blog/how-to-view-ssl-certificate-details-in-chrome-56/

[nkmb]

Nice, thank you for clarifying that!

[Krish_2009]

Thank you! It works now

[TanviK]

Hi Jon, 

Is this issue fixed? I tried connecting the Fitbit studio to the Simulator (v 0.9.2). While it connects to the phone simulator, there are no devices available to connect.

The simulator says that the "Device Bridge is disconnected".

Is this the same issue or a new bug? I just upgraded my simulator to the latest version.

[ag87]

I'm also having the same problem today, on mac-os the studio says connected with the green light, while also showing no devices available, as well as the simulator saying "device bridge disconnected", and "companion bridge is connected to a debugger".

[ag87]

Did the atlas content app cert change as suggested and it worked, thank you

[BlythMeister]

I don't seem to be able to start the simulator at all even with the changed cer file.

 The app just says "Here we go" and spinning

Is this a new problem...or something related/known

The logs state this:

[2021-12-02 11:22:37.336] [warn] 10 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2021-12-02 11:22:38.348] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2021-12-02 11:22:53.359] [warn] 9 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2021-12-02 11:22:55.381] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2021-12-02 11:23:10.393] [warn] 8 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2021-12-02 11:23:13.432] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2021-12-02 11:23:28.434] [warn] 7 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2021-12-02 11:23:32.478] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2021-12-02 11:23:47.483] [warn] 6 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2021-12-02 11:23:52.539] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2021-12-02 11:24:07.552] [warn] 5 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2021-12-02 11:24:13.616] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2021-12-02 11:24:28.625] [warn] 4 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2021-12-02 11:24:35.702] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2021-12-02 11:24:50.712] [warn] 3 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2021-12-02 11:24:58.789] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2021-12-02 11:25:13.798] [warn] 2 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2021-12-02 11:25:22.897] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2021-12-02 11:25:37.906] [warn] 1 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2021-12-02 11:25:48.004] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2021-12-02 11:26:03.009] [error] Simulator hosts failed to start: MethodCallTimeout: No response received for RPC call to 'initialize'

[MDeeJ]

Hi, has this been fixed now? I've just started using the simulator using the latest version and have run into this problem.

Thanks

[Gondwana]

Not yet.

[guit4eva]

Same issue, MacOs.

"Device bridge is disconnected".