blocks|key|74579|text|尝尝这个|type|unstyled|depth|inlineStyleRanges|entityRanges|data|74580|initLocalSettingsIfNeed()
++++.andThen(initGlobalSettingsIfNeed(configuration))
++++.subscribe({completed->
++++++++callback.onSuccess()
++++},{throwable->
++++++++callback.onError(throwable.getLocalizedMessage())
++++})|code-block|syntax|javascript|74581|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

try this 

<pre><code>initLocalSettingsIfNeed()
 .andThen(initGlobalSettingsIfNeed(configuration))
 .subscribe({completed-&gt;
 callback.onSuccess()
 },{throwable-&gt;
 callback.onError(throwable.getLocalizedMessage())
 })
</code></pre>

blocks|key|2580455|text|关于你最初的问题，你必须知道doOnError不是onError的替代品。你在this+blog中有一个很好的简短的解释|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2580456|2580457|，实际上，它们之间有一个关键的区别。doOnError()基本上只触发它的回调，然后将遇到的错误向下传递到下游。subscribe，因此如果订阅了整个流而没有在subscribe()中调用onError回调，那么您的应用程序将因OnErrorNotImplementedException.而崩溃|blockquote|2580458|2580459|另一方面，subscribe()中的onError回调确实使用了错误。意味着，它将捕获错误，并允许您处理这些错误，而无需重新抛出错误本身。|2580460|2580461|关于你在一条评论中提到的警告：|2580462|2580463|这种方法是有效的，但我有警告‘订阅未使用的结果’，因为我知道这需要在调用onError或onComplete时自动处理，有没有办法避免这个警告？-+Pavel+Poley|2580464|2580465|2580466|一个不错的方法是让Repository中的方法返回一个Observable，然后您可以在ViewModel中订阅它们。然后，在每个ViewModel类中，您可以拥有一个带有CompositeDisposable的成员变量，您可以在其中将每个订阅的disposable添加到存储库返回的可观察对象中。最后，您应该重写onCleared方法来处理存储在CompositeDisposable中的所有可处置物品。|2580467|public+class+MyViewModel+extends+ViewModel+{

++++private+MyRepository+myRepository;
++++private+final+CompositeDisposable+disposables;

++++@Inject
++++public+MyViewModel(MyRepository+myRepository)+{
++++++++...
++++++++this.myRepository+=+myRepository;
++++++++disposables+=+new+CompositeDisposable();
++++++++...
++++}

++++public+void+callObservableInRepository()+{
+++++++++disposables.add(myRepository.myObservable()
++++++++++++++++++++++++++++++.subscribe(onSuccess+->+{...}+,+onError+->+{...}));
++++}

++++@Override
++++protected+void+onCleared()+{
++++++++disposables.clear();
++++}

}|code-block|syntax|javascript|2580468|entityMap|0|LINK|mutability|MUTABLE|url|https://thuytrinh.github.io/rxjava/android/2018/06/23/onerror-doonerror.html^0|E|9|P|7|13|9|0|0|0|0|0|0|0|0|0|0|0|0|9|A|R|A|18|9|1T|9|2E|J|4D|9|4U|J|0|0^^$0|@$1|2|3|4|5|6|7|19|8|@$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]]|D|@$9|1E|A|1F|1|1G]]|E|$]]|$1|F|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|1I|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|1J|8|@]|D|@]|E|$]]|$1|K|3|L|5|6|7|1K|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1M|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|1N|8|@]|D|@]|E|$]]|$1|Q|3|R|5|I|7|1O|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1P|8|@]|D|@]|E|$]]|$1|T|3|-4|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|U|3|V|5|6|7|1R|8|@$9|1S|A|1T|B|C]|$9|1U|A|1V|B|C]|$9|1W|A|1X|B|C]|$9|1Y|A|1Z|B|C]|$9|20|A|21|B|C]|$9|22|A|23|B|C]|$9|24|A|25|B|C]]|D|@]|E|$]]|$1|W|3|X|5|Y|7|26|8|@]|D|@]|E|$Z|10]]|$1|11|3|-4|5|6|7|27|8|@]|D|@]|E|$]]]|12|$13|$5|14|15|16|E|$17|18]]]]

Regarding your original question, you have to know that <code>doOnError</code> is not a replacement of <code>onError</code>. You have a good and short explanation about it in <a href="https://thuytrinh.github.io/rxjava/android/2018/06/23/onerror-doonerror.html" rel="nofollow noreferrer">this blog</a>:

<blockquote>
 Actually there’s one key difference between them. doOnError() basically only triggers its callback, then passes down the encountered errors to the down stream. So if the whole stream is subscribed without the onError callback in subscribe(), your app will crash by OnErrorNotImplementedException.
 
 The onError callback in subscribe() in the other hand does consume the
 errors. That means, it will catch the errors, and let you handle them
 without re-throwing the errors by itself.
</blockquote>

About the warning you mention in one comment:

<blockquote>
 This approach is working, but i have warning 'the result of subscribe
 not used', as i know this need to be disposed automatically when
 onError or onComplete is called, is there way to avoid this warning? – Pavel Poley
</blockquote>

A good approach is that your methods inside your <code>Repository</code> return a <code>Observable</code>, and then you can subscribe to them in your <code>ViewModel</code>. Then, in every <code>ViewModel</code> class you can have a member variable with a <code>CompositeDisposable</code> where you can add the disposable of each subscription to the Observables returned by your repository. Finally, you should override the <code>onCleared</code> method to dispose all the disposables stored in the <code>CompositeDisposable</code>.

<pre><code>public class MyViewModel extends ViewModel {

 private MyRepository myRepository;
 private final CompositeDisposable disposables;

 @Inject
 public MyViewModel(MyRepository myRepository) {
 ...
 this.myRepository = myRepository;
 disposables = new CompositeDisposable();
 ...
 }

 public void callObservableInRepository() {
 disposables.add(myRepository.myObservable()
 .subscribe(onSuccess -&gt; {...} , onError -&gt; {...}));
 }

 @Override
 protected void onCleared() {
 disposables.clear();
 }

}
</code></pre>

I am try to use the following code
<pre><code>initLocalSettingsIfNeed()
 .andThen(initGlobalSettingsIfNeed(configuration))
 .doOnComplete(callback::onSuccess)
 .doOnError(throwable -&gt; callback.onError(throwable.getLocalizedMessage()))
 .subscribe();
</code></pre>
But I have exception
<blockquote>
The exception was not handled due to missing onError handler in the
subscribe() method call.
</blockquote>
I guess I am not using this methods correctly, I thought can replace <code>doOnComplete</code> <code>doOnError</code> with observer inside <code>subscribe()</code> method, I am wrong?

RxJava doOnError vs onError

我正在尝试使用以下代码initLocalSettingsIfNeed()                            .andThen(initGlobalSettingsIfNeed(configuration))                            .doOnComplete(callb...

问RxJava doOnError vs onError
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问RxJava doOnError vs onErrorEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问RxJava doOnError vs onError
EN