RxUtil | [DEPRECATED]囊括了最实用的RxJava工具类集合

Looks issue in mocking

you are using

Mockito.when(workOrdersRepository.payWorkOrderInvoice(workOrderId, paymentRequest)).thenReturn(Single.just(response));

Reason of NPE is paymentRequest while mocking is not same as passed in following code

one approach i've used in the past is to share a Subject used for communicating error conditions.

• on the producer side, hold a reference to it a Subject type (Publish/Behavior/Replay/etc) so as to invoke onNext() with the next error the application has incurred. in this case the producer would be the ResponseCodeCheckInterceptor instance. rather than throwing the various exceptions, this instance would instead emit an ErrorState describing the error that just occurred. (assume ErrorState to be a custom type that carries just enough information about an error condition for consumers to decide how to react, e.g. update the UI, clean-up resources, etc).

• on the consumer side, hold a reference to the shared Subject as an Observable. as you seem to be doing MVP, the Presenter would likely be one of your consumers.

(dependency injection is a good way to go about sharing the Subject instance).

hope that helps!

Update with some rough sample code...

If you are only trying to kill the current activity and go back to the previous activity, you can call finish() instead of onBackPressed().

It seems that the mock can't be read. Try to put any() on the parameters:

Instead of this:

If RxUtils.applySchedulers is applying the following then at the point you go through the mapping operation and subsequently hit service.downloadFileByUrl this will be executed on the main thread.

Your doOnSubscribe executes the content on the same thread where getServerSettings() is executed which belongs to Schedulers.io(). Hence, your mView.showLoadingIndicator(true, "Checking Server ....") is trying to update the UI off the main thread (which is not allowed) and so this error terminates your Observable execution - you may see it in your mView.showErrorMessage(throwable.getLocalizedMessage()) call but I don't know what exactly you're doing there.

What you should do is to send a message from your doOnSubscribe to the main thread as follows:

flatMap is generally the operator to use when you the second operation depends on the result of the first. flatMap works like an inline subscriber. For your example above you could write something like:

If it relates to the SDK, it probably won't work in a unit test. You didn't include your imports, so it's impossible to tell at a glance, but I know from experience that you can't use this in a unit test

Your second data Object is missing [ and later ] at options: