Catch and handle startup errors

[richburdon]

• Detect and catch startup errors
• Report to user in consistent way -- with remedy
• Capture and track errors (e.g., KUBE service with HTTP API to report and log errors to IPFS)

react_devtools_backend.js:2273 Client.initialize is taking more then 3 seconds to complete. Something probably went wrong.
overrideMethod @ react_devtools_backend.js:2273
eval @ client.ts?951c:130
setTimeout (async)
initialize @ client.ts?951c:129
eval @ main.js?56d7:35
async function (async)
eval @ main.js?56d7:19
eval @ main.js?56d7:18
3348 @ main~493df0b3.bundle.js:1
l @ runtime.bundle.js:1
t @ runtime.bundle.js:1
r @ runtime.bundle.js:1
(anonymous) @ main~493df0b3.bundle.js:1
feed-store-adapter.js?5147:55 Uncaught (in promise) TypeError: Cannot read property 'equals' of undefined
    at eval (feed-store-adapter.js?5147:55)
    at Array.find (<anonymous>)
    at FeedStoreAdapter.queryWritableFeed (feed-store-adapter.js?5147:55)
    at PartyManager.open (party-manager.js?9e8c:50)

[alexwykoff]

I'm curious if this is an SDK issue or if it is a Teamwork issue. That is, if we do expect client init to fail, what should the SDK expose as a handler?

[richburdon]

Discussed with @marik-d. react-appkit should provide consistent error reporting and the app (Teamwork) should use this to bootstrap the system.

NOTE: in this case this looks like the same profile override error. @rzadp I added a resolution to this -- was it removed?

[rzadp]

Discussed with @marik-d. react-appkit should provide consistent error reporting and the app (Teamwork) should use this to bootstrap the system.

NOTE: in this case this looks like the same profile override error. @rzadp I added a resolution to this -- was it removed?

@richburdon Are you talking about the resolution in SDK or the resolution in Teamwork?
In Teamwork, the PR is unmerged - see comment: dxos-deprecated/teamwork#316 (comment)