Temporary error when starting the server
I've been starting/stopping the server a bunch of times and once I got this error (which I unfortunately didn't copy/screenshot, but remember).
It was complaining about can't read 'needsSignature' in undefined or null from express.js viewDataMiddle
I think config.license is not set, because initialize hasn't returned yet, so possibly the
await expressReady is still awaiting when my request reached it. Note that I've only seen this when starting fvtt with --world.
Also note, that the error goes away if I reload a few seconds later, though when it had happened, I had to reload 3 times before it finally cleared it.
Ah! Poking at
/api/status endpoint right after it started, I was able to reproduce a similar error, probably same cause, though it's a different crash.
TypeError: Cannot read property 'users' of undefined at apiStatus (f:\Games\FVTTOnline\theforge\FVTT-Releases\foundryvtt-0.5.1\dist\views.js:1:11230) at Layer.handle [as handle_request] (f:\Games\FVTTOnline\theforge\FVTT-Releases\foundryvtt-0.5.1\node_modules\express\lib\router\layer.js:95:5) at next (f:\Games\FVTTOnline\theforge\FVTT-Releases\foundryvtt-0.5.1\node_modules\express\lib\router\route.js:137:13) at Route.dispatch (f:\Games\FVTTOnline\theforge\FVTT-Releases\foundryvtt-0.5.1\node_modules\express\lib\router\route.js:112:3) at Layer.handle [as handle_request] (f:\Games\FVTTOnline\theforge\FVTT-Releases\foundryvtt-0.5.1\node_modules\express\lib\router\layer.js:95:5) at f:\Games\FVTTOnline\theforge\FVTT-Releases\foundryvtt-0.5.1\node_modules\express\lib\router\index.js:281:22 at Function.process_params (f:\Games\FVTTOnline\theforge\FVTT-Releases\foundryvtt-0.5.1\node_modules\express\lib\router\index.js:335:12) at next (f:\Games\FVTTOnline\theforge\FVTT-Releases\foundryvtt-0.5.1\node_modules\express\lib\router\index.js:275:10) at SendStream.error (f:\Games\FVTTOnline\theforge\FVTT-Releases\foundryvtt-0.5.1\node_modules\serve-static\index.js:121:7) at SendStream.emit (events.js:305:20)
This one looks like it's
game.activity that's not yet defined. I haven't looked into how game.activity gets set, but I'd assume it's a similar cause.