Error Handling with RxJava
Observable can raise error by calling onError() and catch with Subscriber. But this is not the only way to manage error in RxJava. There are lot of useful operator that could help you to handle error with different strategy:
doOnError
onErrorResumeNext
onErrorResume
onErrorReturn
onErrorReturnItem
retry
retryUtil
retryWhen
…
First, this is how to print stack trace from an exception:
getMessages$.doOnError(e -> e.printStackTrace())
If your stream is a HTTP request, you might want to retry it:
getMessages$.retry(3)
Get Ming Choi’s stories in your inbox
Join Medium for free to get updates from this writer.
Or emit an empty result as default value:
getMessages$.onErrorReturnItem(new ArrayList<Message>())
Maybe fallback to another stream:
getMessages$.onErrorResumeNext(getOfflineMessages$)
Let’s put it all together:
getMessages$
.doOnError(e -> Log.e(“MessageActivity”, “Get message failed. retrying.”))
.retry(3)
.doOnError(e -> Log.e(“MessageActivity”, “Fallback to Get offline messages.”))
.onErrorResumeNext(getOfflineMessages$)
.doOnError(e -> e.printStackTrace())
.onErrorReturnItem(emptyMessagesList())
Quite easy, right?
![[LeetCode] 134. Gas Station — Solution with explanation (0ms, 100% faster, 100% less)](https://miro.medium.com/v2/resize:fit:1358/format:webp/1*6zBSkDnzgt1FlhHHVsES3Q.png)






