In RxJava, Publisher emits events and you can subscribe to those events with Consumer. While subscribing, emitted events can be used to update the view or to do something else. Below example shows a simple example:
This code work well while Publisher emits events without any error. However, there could be several issues to emit events. Those vary depending on where events are generated. For example, if Publisher is related to the network, it could have a bad connection or no response from a backend service. In that situation, an error will be thrown. The current code doesn’t have any logic to consume that error,
OnErrorMissingConsumer exception happens. That exception makes an app crash.
The crash will tell you what went wrong. Although it is useful, you don’t want to make a crash in some cases. Some logic doesn’t affect the main experience, or a user can trigger to subscribe again easily. So, you can set an error consumer to handle those errors and avoid a crash. One way is just to print an error log.
It looks good, but it has some potential issues.
- This doesn’t make a crash, so it is easy to miss. Error logs are often not enough to grab attention.
- There is no way to know how many people have errors. If your backend service is down, all users will have a network error. By tracking errors, you can keep giving a better experience continuously.
Thus, what we want to achieve is to track errors in the release and to make a crash while developing, which helps early detection. Crashlytics is one of the useful tools for tracking errors. You can track errors by calling
BuildConfig.DEBUG tells whether the build is a release or a debug. TO sum up, you can resolve those issues like below.
Some exceptions/throwables could be not needed to make a crash in your application. You can check with
instanceofand ignore them.