Simulator will not load

[Streeter80]

Is anyone else having issues with the simulator not opening and loading? I have uninstalled and reinstalled it, rebooted the computer, logged out and logged back in to everything and yet the simulator refuses to load. I cannot get past the Hang Tight simulator loading screen before it going to Dang lets try that again. 

[Michael-Powell]

Yes, same here too..

[allan175]

Same here, and has been the same for the last few versions. I haven't been able to run the simulator for a long time (and hence not done any Fitbit coding).

The log file seems to be complaining about an "ECONNREFUSED" error, then failing to start.

It's very frustrating.

[JonFitbit · Accepted solution]

Try deleting the following folders:

macos: ~/Library/Application Support/Fitbit OS Simulator

windows: C:\Users\%user%\AppData\Roaming\Fitbit OS Simulator

[allan175]

Still the same.

It says "Here we go. Simulator loading" for a while, before saying "Dang! Simulator failed to start."

[allan175]

Here's the log file:-
https://pastebin.com/kAzSwbKd

[Streeter80]

Perfect!!! it's back up and working again. Thank you so much. 

[eamodio]

Didn't help for me. Still get the same issue (sometimes a full uninstall will work once, but that seemed to only work twice so far).

Here is what is in the logs:

```

[2019-12-08 23:33:22.779] [warn] 10 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2019-12-08 23:33:23.782] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2019-12-08 23:33:26.282] [warn] 9 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'

```

[Lars.E]

This does not work for me either, and its quite frustrating.

As far as i can discern this has to do with the fact that my user profile, where the mentiones directory is placed, is located on a network share, and has a symbolic link to it.

This would be quite easy to work around if the installation asked where the installation should be made, instead of using profile directories that might or might not be locally stored.

There is also no "settings" file with a link to the working directory that can be adjusted, but instead that seems to be coded into the simulator. 

Please make the installation process more configurable to make the product usable for more developers

[curxxx]

The entire Fitbit development process is buggy so this doesn't surprise me. I've had this issue a few times, but it's probably the least annoying issue I have to deal with in regards to developing for this platform.

Fitbit is pushing away developers with all these issues. It's time for us to speak up. 

[dkjr1]

that did not work

[Mindmaster14]

Deleting this file did not resolve the issue for my Windows 10 Surface ProX.