Respond to internal development errors by hitting a network catch () request

Question

I am going to keep this relatively high level since I cannot recreate it in a demo application ... But I have the weirdest problem in React Native on iOS.

When an error occurs during the execution of React Native code in dev mode, it falls into a random block catch()from an old request fetchthat was completed in the past. This fetch block has .done()and is being completed.

This leads to a very strange series of errors:

1st: ExceptionsManager.js:70 Warning: There is an internal error in the React performance measurement code. Did not expect componentDidUpdate timer to start while render timer is still in progress for another instance.

2nd: ExceptionsManager.js:55 Cannot read property 'getHostNode' of null

3rd: ExceptionsManager.js:70 Unhandled JS Exception: Cannot read property 'getHostNode' of null