Workbench uncaught exceptions in React

[davemfish]

A few people have reported the Workbench starting up with a "blank screen":

I think this probably indicates an uncaught exception in a react component. The browser hasn't crashed and the main nodejs process seems fine also, looking at the logs.

Jade reports the Workbench was working fine for a while, then crashed one time, and then this started happening every time she starts the workbench, even after re-installing it.

I'm not sure what problem would persist between sessions, though there are a couple things the workbench looks for on the filesystem on startup.

First step is to setup a react ErrorBoundary to catch and log exceptions that we might be missing now. Especially since devtools is disabled in production.

[davemfish]

Okay the extra logging after catching the exception yielded this:

[10:49:14.583] [ErrorBoundary] Error: Cannot read properties of undefined (reading 'workspace_dir')
[10:49:14.585] [ErrorBoundary] {
  componentStack: '\n' +
    '    at RecentInvestJobs (file:///C:/Users/Jade%20DELEVAUX/AppData/Local/Programs/InVEST%203.9.2.post4001+g9e14f03cf%20Workbench/resources/app.asar/build/assets/index.1d3a8bde.js:346:5)\n' +
    '    at div\n' +
    '    at 

That's an error from RecentInvestJobs trying to render a malformed InvestJob from the localforage database. We definitely need some better error-handling there! And/or better validation for the structure of those cached jobs.

[davemfish]

Deleting C:\Users\your username\AppData\Roaming\invest-workbench\ clears out that database and is generally worth suggesting to users if anything like this comes up in the future.