CODEWITHSUNDEEP
javaandroidrx-javarx-android
xorgate
xorgate

Reputation: 2264

In RxJava, how to retry/resume on error, instead of completing the observable

What I want to achieve is:

I know when the change happens, now I presume I need to call onNext on a Subject. This should then trigger a Rx chain, and in the end I can update the UI.

mViewPeriodSubject = PublishSubject.create();

mAdapterObservable =
    mViewPeriodSubject
        .flatMap(period -> MyRetrofitAPI.getService().fetchData(period)) // this might fail
        .flatMap(Observable::from)
        .map(MyItem::modifyItem)
        .toList()
        .map(obj -> new MyAdapter(obj));


mViewPeriodSubject.onNext("week"); // this one starts the chain
mViewPeriodSubject.onNext("year"); // this one does not

But in the case of the network call failing, the observable errors, and calling onNext() does not result in another network call.

So my question is, how should I handle this? How can I keep the Observable intact so I can just throw another value at it? I can imagine for example a simple retry button that just wants to ignore the fact that an error occurred.

Upvotes: 6

Views: 6179

Answers (1)

dwursteisen
dwursteisen

Reputation: 11515

You don't have to deal error with your mViewPeriodSubject but instead, deal with errors on your retrofit Observable. This retrofit Observable won't resume, but at least, it won't affect your "main" Observable.

mAdapterObservable =
mViewPeriodSubject
    .flatMap(period -> MyRetrofitAPI.getService().fetchData(period).onErrorResumeNext(e -> Observable.empty()) // this might fail
    .flatMap(Observable::from)
    .map(MyItem::modifyItem)
    .toList()
    .map(obj -> new MyAdapter(obj));

Upvotes: 7

Related Questions