If there is an exception while building for the simulator, devkit serve does not output it locally and the simulator just spins forever. It might be better if the simulator displayed the message body on 500 if available (currently it is sent the message and the stack trace), and devkit serve printed the error and/or stacktrace locally as well.
If there is an exception while building for the simulator,
devkit servedoes not output it locally and the simulator just spins forever. It might be better if the simulator displayed the message body on 500 if available (currently it is sent the message and the stack trace), and devkit serve printed the error and/or stacktrace locally as well.