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
B) Then the trouble, if we manage the future possible errors after CancelableOperation being constructed, via its value property, errors are not catched and app is crashing.
This problem began with Dio library on this issue.
Basically the thing is that be have a CancelableOperation being constructed from a Future value.
A) If we manage this future possible errors before constructing the CancelableOperation , it works fine: errors can be catched.
B) Then the trouble, if we manage the future possible errors after CancelableOperation being constructed, via its value property, errors are not catched and app is crashing.
Is it the normal behaviour?
It would not be preferable to propagate also the future's error?
The text was updated successfully, but these errors were encountered: