gestore errori RxJava predefinito

Question

Spiacente, esiste la possibilità di impostare il gestore errori predefinito in RxJava?

Per esempio, ho un po 'di codice nel file di Utils.kt:

fun BaseFragment.callGallery(view: View){ 
    view.clicks().bindToLifecycle(this).subscribe { 
     RxPaparazzo.takeImage(this) 
     .usingGallery() 
     .subscribe { response -> 
      throw RuntimeException("Where is this exception from?") 
     } 
    } 
} 

Ma in stacktrace non c'è alcun accenno su Utils.kt o di qualsiasi del mio file.

Capisco che posso impostare onError in ogni utente. con codice del tipo:

.subscribe ({ response -> 
    .... 
}, { it.printStackTrace() }) 

Ma preferirei impostare un errore predefinito suErrore per tutti gli abbonati. Come posso farlo?

Stacktrace:

05-07 12:11:48.246 10966-10966/ru.egslava.rxfluxtest E/AndroidRuntime: FATAL EXCEPTION: main 
Process: ru.egslava.rxfluxtest, PID: 10966 
java.lang.RuntimeException: Unable to destroy activity {ru.egslava.rxfluxtest/rx_activity_result.HolderActivity}: rx.exceptions.OnErrorNotImplementedException: Where is this exception from? 
    at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3831) 
    at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:3849) 
    at android.app.ActivityThread.-wrap5(ActivityThread.java) 
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1398) 
    at android.os.Handler.dispatchMessage(Handler.java:102) 
    at android.os.Looper.loop(Looper.java:148) 
    at android.app.ActivityThread.main(ActivityThread.java:5417) 
    at java.lang.reflect.Method.invoke(Native Method) 
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726) 
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616) 
    Caused by: rx.exceptions.OnErrorNotImplementedException: Where is this exception from? 
    at rx.internal.util.InternalObservableUtils$ErrorNotImplementedAction.call(InternalObservableUtils.java:374) 
    at rx.internal.util.InternalObservableUtils$ErrorNotImplementedAction.call(InternalObservableUtils.java:371) 
    at rx.internal.util.ActionSubscriber.onError(ActionSubscriber.java:44) 
    at rx.observers.SafeSubscriber._onError(SafeSubscriber.java:157) 
    at rx.observers.SafeSubscriber.onError(SafeSubscriber.java:120) 
    at rx.exceptions.Exceptions.throwOrReport(Exceptions.java:204) 
    at rx.observers.SafeSubscriber.onNext(SafeSubscriber.java:144) 
    at rx.internal.operators.OperatorOnErrorResumeNextViaFunction$4.onNext(OperatorOnErrorResumeNextViaFunction.java:153) 
    at rx.internal.operators.OperatorMap$MapSubscriber.onNext(OperatorMap.java:74) 
    at rx.internal.operators.OperatorMerge$MergeSubscriber.emitScalar(OperatorMerge.java:391) 
    at rx.internal.operators.OperatorMerge$MergeSubscriber.tryEmit(OperatorMerge.java:353) 
    at rx.internal.operators.OperatorMerge$InnerSubscriber.onNext(OperatorMerge.java:838) 
    at rx.observers.Subscribers$5.onNext(Subscribers.java:229) 
    at rx.internal.operators.OperatorZip$Zip.tick(OperatorZip.java:264) 
    at rx.internal.operators.OperatorZip$Zip$InnerSubscriber.onNext(OperatorZip.java:335) 
    at rx.internal.operators.OperatorMap$MapSubscriber.onNext(OperatorMap.java:74) 
    at rx.internal.util.ScalarSynchronousObservable$WeakSingleProducer.request(ScalarSynchronousObservable.java:268) 
    at rx.Subscriber.setProducer(Subscriber.java:211) 
    at rx.internal.operators.OperatorMap$MapSubscriber.setProducer(OperatorMap.java:99) 
    at rx.internal.util.ScalarSynchronousObservable$1.call(ScalarSynchronousObservable.java:79) 
    at rx.internal.util.ScalarSynchronousObservable$1.call(ScalarSynchronousObservable.java:75) 
    at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:50) 
    at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:30) 
    at rx.Observable.unsafeSubscribe(Observable.java:8452) 
    at rx.internal.operators.OperatorZip$Zip.start(OperatorZip.java:214) 
    at rx.internal.operators.OperatorZip$ZipSubscriber.onNext(OperatorZip.java:156) 
    at rx.internal.operators.OperatorZip$ZipSubscriber.onNext(OperatorZip.java:122) 
    at rx.internal.util.ScalarSynchronousObservable$WeakSingleProducer.request(ScalarSynchronousObservable.java:268) 
    at rx.Subscriber.setProducer(Subscriber.java:209) 
    at rx.internal.util.ScalarSynchronousObservable$1.call(ScalarSynchronousObservable.java:79) 
    at rx.internal.util.ScalarSynchronousObservable$1.call(ScalarSynchronousObservable.java:75) 
    at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:50) 
    at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:30) 
    at rx.Observable.unsafeSubscribe(Observable.java:8452) 
    at rx.internal.util.ScalarSynchronousObservable$4.call(ScalarSynchronousObservable.java:227) 
    at rx.internal.util.ScalarSynchronousObservable$4.call(ScalarSynchronousObservable.java:220) 
    at rx.Observable.unsafeSubscribe(Observable.java:8452) 
    at rx.internal.operators.OperatorMerge$MergeSubscriber.onNext(OperatorMerge.java:248) 

Answer 1

È possibile utilizzare l'operatore onErrorResumeNext. Utilizzo Esempio:

fun BaseFragment.callGallery(view: View){ 
    view 
     .clicks() 
     .bindToLifecycle(this) 
     .onErrorResumeNext { err -> log(err); Observable.empty() } 
     .subscribe { 
     // do stuff 
     } 
} 

Answer 2

RxJava ha Plugins sostenere preoccupazioni trasversali bene. In particolare RxJavaErrorHandler è desiged a allegato comportamento gestione degli errori globale in questo modo:

RxJavaPlugins.getInstance().registerErrorHandler(object : RxJavaErrorHandler() { 
    override fun handleError(e: Throwable?) { 
     println("Global error handler: $e") 
    } 
}) 

Observable.just(1).concatMap({ Observable.error<Int>(Exception("Just throwing $it")) }) 
     .subscribe({ 
      println("I'll not be called") 
     }, { 
      println("Specific error handler: $it") 
     }) 

Il codice di cui sopra sarebbe stampare:

Error occurred java.lang.Exception: Just throwing 1 
A default error handler: java.lang.Exception: Just throwing 1 

Ho il sospetto che si sarebbe anche essere interessati a migliorare le informazioni diagnostiche disponibili in stacktraces quando si verifica un errore non gestito. Per questo c'è un RxJavaStackTracer che quando usato RxJavaPlugins.getInstance().registerObservableExecutionHook(RxJavaStackTracer()) enfatizza le informazioni di traccia dello stack. Il problema Stacktraces and subscribeOn/observeOn su github è una buona lettura sull'argomento.