You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can also use Isolate.debugName, which has no such limitation. It's also not specific to Flutter, but to dart:io. But then again rootIsolateToken is also bound to dart:io and web has no threads.
rootIsolateToken on the other hand is non-null on the main-isolate vs null on non-main-isolates. So it has less information than Isolate.debugName. (Not saying that one is better, just that each has their own drawbacks)
we could verify that the current Isolate is in the main isolate or not with rootIsolateToken and then we know that the Isolate.current.debugName is referring to the main isolate and not any other and use it then properly
Description
Issue: getsentry/team-mobile#153
We can use rootIsolateToken but this is currently blocked by Flutter min version
3.7
The text was updated successfully, but these errors were encountered: