07-16-2020 13:27
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-16-2020 13:27
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I have a laptop and a Desktop. The simulator on my desktop does not start anymore. One of the things changed is that I started using the CLI.
Tried all things already suggested on the forum.
Deleted folder "C:\Users\Pieter\AppData\Roaming\Fitbit OS Simulator"
deleted folder "C:\Users\Pieter\AppData\Local\Programs\@fitbitsimulator"
This is the Log file from the simulator
[2020-07-16 22:20:08.573] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2020-07-16 22:20:09.319] [info] appsim exit code: 3221225477 (signal null)
[2020-07-16 22:20:11.073] [warn] 10 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2020-07-16 22:20:12.077] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2020-07-16 22:20:14.577] [warn] 9 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2020-07-16 22:20:16.583] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2020-07-16 22:20:19.081] [warn] 8 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2020-07-16 22:20:22.085] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2020-07-16 22:20:24.584] [warn] 7 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2020-07-16 22:20:28.588] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2020-07-16 22:20:31.088] [warn] 6 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2020-07-16 22:20:36.090] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2020-07-16 22:20:38.590] [warn] 5 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2020-07-16 22:20:44.595] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2020-07-16 22:20:47.095] [warn] 4 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2020-07-16 22:20:54.098] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2020-07-16 22:20:56.598] [warn] 3 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2020-07-16 22:21:04.603] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2020-07-16 22:21:07.115] [warn] 2 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2020-07-16 22:21:16.128] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2020-07-16 22:21:18.625] [warn] 1 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2020-07-16 22:21:28.631] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2020-07-16 22:21:31.130] [error] Simulator hosts failed to start: MethodCallTimeout: No response received for RPC call to 'initialize'
Answered! Go to the Best Answer.

Accepted Solutions
07-16-2020 19:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-16-2020 19:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hello Pietero,
When I test answers I bounce back and forth between CLI and Fitbit Studio. There doesn't appear to be any difference between the 2 how the simulator works, though it will only connect to the one that connected to it first (after starting up)
Have you tried deleting the simulator and starting over?
There's no real value in keeping your original install.
The last time they updated the simulator, that seemed the easiest way; I uninstalled it, then downloaded using Fitbit studio and have been using it with ever CLI since.
Regards,
Good Luck,
Reign

07-16-2020 19:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-16-2020 19:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hello Pietero,
When I test answers I bounce back and forth between CLI and Fitbit Studio. There doesn't appear to be any difference between the 2 how the simulator works, though it will only connect to the one that connected to it first (after starting up)
Have you tried deleting the simulator and starting over?
There's no real value in keeping your original install.
The last time they updated the simulator, that seemed the easiest way; I uninstalled it, then downloaded using Fitbit studio and have been using it with ever CLI since.
Regards,
Good Luck,
Reign

07-20-2020 00:54
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-20-2020 00:54
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@morningReign Thank you for your eleborate reply.
I found the cause.. I was using Remote desktop to met Desktop upstairs. That cause was hidden in my questions.
Normally i did the development on my laptop and desktop from Fitbit studio and running the simulator locally. Since i moved over to the CLI I can only do the development on my desktop. My laptop has limiations due to company restrictions.

