Skip to content
- Yes, but because the observable ‘ends’ does not mean the code running inside
create(...) is stopped. To be fully safe in this case you need to use o.isDisposed() to see if the observable has ended downstream.
- The exception is there because RxJava 2 has the policy of NEVER allowing an
onError call to be lost. It is either delivered downstream or thrown as a global UndeliverableException if the observable has already terminated. It is up to the creator of the Observable to ‘properly’ handle the case where the observable has ended and an Exception occurs.
- The problem is the producer (
Observable) and the consumer (Subscriber) disagreeing on when the stream ends. Since the producer is outliving the consumer in this case, the problem can only be fixed in the producer.