11-26-2019 14:59
11-26-2019 14:59
When connecting to my windows 10 desktop from my windows 10 laptop via remote desktop, the OS simulator refuses to launch. The error is simply "Simulator failed to start". These seem to be the appropriate lines from the log file:
[2019-11-26 14:29:04.296] [warn] 1 retries left: MethodCallTimeout: No response received for RPC call to 'initialize'
[2019-11-26 14:29:14.302] [info] shell->app: {"id":0,"method":"initialize","params":{"capabilities":{"protocol":{"maxMessageSize":536870912}}},"jsonrpc":"2.0"}
[2019-11-26 14:29:16.803] [error] Simulator hosts failed to start: MethodCallTimeout: No response received for RPC call to 'initialize'
The simulator works fine on the desktop without remote desktop. I can also start the simulator on the desktop then connect via remote desktop and launch the app.
Does anyone have any ideas why remote desktop would interfere with the simulator?
Thanks, Rich
11-29-2019 08:47 - edited 11-29-2019 08:48
11-29-2019 08:47 - edited 11-29-2019 08:48
Same here, worked perfectly the last couple of days. Stopped working today with the same error message... Win 10 desktop, nothing changed in firewall settings...
12-02-2019 14:25
12-02-2019 14:25
Same issue here, but not on Remote Desktop. I'm using macOS Mojave 10.14.6 and latest Fitbit OS Simulator
12-14-2019 01:42
12-14-2019 14:23
12-14-2019 14:23
@vinnesthanks for the info. Unfortunately it didn't work for me. Still crashing under remote desktop.
05-18-2021 03:37
05-18-2021 03:37
Thank you for the code! I managed to run it. However, nothing works when I want to run their Team-viewer. I tried to fix the bugs for a while, but nothing worked. Then I looked for suitable software that would not limit me in this and found one cheap RDP that at least loads quickly and reacts as I need. This is a useful thing when it is more convenient for you to work with a high-quality image of the desktop of another computer with remote access. I probably shouldn't have underestimated the purchase of servers before.