Codecov Report

Base: 90.11% // Head: 90.16% // Increases project coverage by +0.04% 🎉

Coverage data is based on head (faf2626) compared to base (3e17cfa).
Patch coverage: 100.00% of modified lines in pull request are covered.

@@            Coverage Diff             @@
##           v7.0.0    #1260      +/-   ##
==========================================
+ Coverage   90.11%   90.16%   +0.04%     
==========================================
  Files         164      164              
  Lines        5121     5136      +15     
==========================================
+ Hits         4615     4631      +16     
+ Misses        506      505       -1     

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

I'd like to add the event.thread.main=true|false as well but since Isolate.current always returns the main Isolate during unhandled callbacks, we can't really tell which Isolate threw the error, if it was the main or not.

Ideally, unhandled callbacks such as onError would return the faulty Isolate in the exception or even an extra parameter.

So its better to not report at all instead of reporting everything as the main Isolate.
@ueman ideas around this?

With Flutter 3.7 you can actually initialize Sentry Flutter on a background isolate, where Isolate.current != 'main'. When the exceptions are passed from one isolate to another, I believe there's unfortunately no automatic way to detect it. For a lot of cases that's not a problem, though, I think. A lot of background computing is done with the compute() method from Flutter where the exception just gets rethrown. While the exception is technically from a background isolate, it still affects the main isolate.