-
Notifications
You must be signed in to change notification settings - Fork 7.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.x Exception unhandled after dispose() #4991
Comments
|
This is a grey area and can be considered as bug. Fix in #4992. |
In my situation, I used a |
Closing via #4992 |
I also encountered this problem when using the
and the exception is
|
@xudshen Indeed the |
@akarnokd I test the same logic with |
This still crashes at RxJava 2.1.16
With custom break operator it also behaves weird, keeps deliver value to the doOnNext method
Output is
|
This is by design, your You implemented |
@akarnokd with onTerminateDetach the error still slips and i have UndeliverableException. Can you please guide how to disable error routing in case when the flowable was created from callable? Or how to write "BreakIfUnsubscribedFlowable" operator properly? |
Do not let it crash into RxJava. https://github.com/ReactiveX/RxJava/blob/2.x/docs/Writing-operators-for-2.0.md |
@akarnokd Thanks. Looks like such operator work as expected (even error is ignored). Do you see any issues in such implementation? May i rely on
|
Have |
@akarnokd thank you very much for your help. |
I built a simple wrapper to resolve this issue
Then you can just do
|
Exception unhandled if dispose() called.
Did I used it in a wrong way ?
error stack:
sample code:
The text was updated successfully, but these errors were encountered: