Toms Burgmanis

this would be super cool, it's also a feature in vscode 🤙

I've looked into this and I'm not sure what the best way to resolve this is. Should on error a tear down event be made, or would it make more...

Any update on this? I might have some time to help patch this if you would be able to give some high level overview of _how_ this should be fixed....

Thanks, that makes sense. One of the immediate things that come to mind is that we need to be able to differentiate between success and failure (i.e exit code 0...

After looking into this more, it seems like it was our fault from the beginning. Because we were overwriting `FlutterError.onError` in our app (without invoking the original value) it breaks...