<@U3H5152AW> you can compose your stream to deal w...

# rx

[leosan]

@viliusk you can compose your stream to deal with the networking error as @alex.hart suggested but you shouldn't be finishing your upstream on networking error basically because what you want keep listening to your stream until your view is destroyed

[viliusk]

how do I prevent from finishing the upstream?

[viliusk]

Just handing errors and returning some other type of objects?

[leosan]

let me check your code

[viliusk]

It’s here: https://gist.github.com/anonymous/7babfd32c88eb1eed6b80d8490d23440

[leosan]

so basically on your getMemberDetails

[leosan]

instead of doOnError use onErrorResumeNext() and then you return something to your main stream

[leosan]

like an empty character or something that will not crash your stream

[viliusk]

Or could I return a new ErrorResponse object with parsed error message?

[leosan]

anything that is not an error it you be passed to your stream and ending on the onNext not sure if you want that

[leosan]

think in something like that

Flowable.just(1,2,3)
     .subscribe({int-> print(int+1})

[leosan]

and then you add an 4th element but is an parsed error

[leosan]

it will try to do calculation and crash

[alex.hart]

onErrorResumeNext takes a new stream, doesn’t it? Replaces the old “Error terminated” stream with the new one

[alex.hart]

Also, I believe onErrorReturn will complete the stream after emitting the value passed in