RxJava 未处理的 SocketTimeoutException

SocketTimeoutException unhandled by RxJava

我有一个使用 sdk 版本 25 开发的 Android 项目。我使用 RXJava 作为我的线程管理和 Retrofit 库来访问网络。

我还实现了自定义拦截器以添加覆盖乐趣拦截(链:Interceptor.Chain):响应? {

    val request = addHeader(chain)

    val response = chain.proceed(request)
    checkErrorResponse(response)

    return response

api 调用将始终在 RX Java 流中,我正在确保它。在我将我的 APK 放入 Playstore 后,Crashlytics 检测到崩溃。

#0. Crashed: main: 0 0 0x0000000000000000
   at okio.Okio.newTimeoutException(Okio.java:230)
   at okio.AsyncTimeout.exit(AsyncTimeout.java:285)
   at okio.AsyncTimeout.read(AsyncTimeout.java:241)
   at okio.RealBufferedSource.indexOf(RealBufferedSource.java:345)
   at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:217)
   at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:211)
   at okhttp3.internal.http1.Http1Codec.readResponseHeaders(Http1Codec.java:189)
   at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.java:75)
   at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
   at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:45)
   at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
   at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
   at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
   at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
   at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
   at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
   at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
   at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:120)
   at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
   at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
   at com.payfazz.data.base.net.PayfazzInterceptor.intercept(PayfazzInterceptor.kt:24)
   at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
   at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
   at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:185)
   at okhttp3.RealCall.execute(RealCall.java:69)
   at retrofit2.OkHttpCall.execute(OkHttpCall.java:180)
   at retrofit2.adapter.rxjava2.CallExecuteObservable.subscribeActual(CallExecuteObservable.java:41)
   at io.reactivex.Observable.subscribe(Observable.java:10842)
   at io.reactivex.internal.operators.observable.ObservableMap.subscribeActual(ObservableMap.java:33)
   at io.reactivex.Observable.subscribe(Observable.java:10842)
   at io.reactivex.internal.operators.observable.ObservableMap.subscribeActual(ObservableMap.java:33)
   at io.reactivex.Observable.subscribe(Observable.java:10842)
   at io.reactivex.internal.operators.observable.ObservableDefer.subscribeActual(ObservableDefer.java:39)
   at io.reactivex.Observable.subscribe(Observable.java:10842)
   at io.reactivex.internal.operators.observable.ObservableDefer.subscribeActual(ObservableDefer.java:39)
   at io.reactivex.Observable.subscribe(Observable.java:10842)
   at io.reactivex.internal.operators.observable.ObservableSubscribeOn$SubscribeTask.run(ObservableSubscribeOn.java:96)
   at io.reactivex.internal.schedulers.ExecutorScheduler$ExecutorWorker$BooleanRunnable.run(ExecutorScheduler.java:260)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
   at java.lang.Thread.run(Thread.java:818)

当我调查堆栈跟踪时,我发现我的代码正好在我的自定义拦截器中。据我所知,崩溃是由 SocketTimeoutException 然后是超时请求引起的。然后我尝试重现超时,但无法完成。在我的环境中,异常总是被 RX Java 捕获并发送到 onError() 方法。

崩溃怎么可能不被RX捕获Java?为了安全起见,我应该用 catch 块包装 proceed() 方法吗?

这些类型的崩溃是在 RxJava 生命周期之外抛出异常时引起的。这意味着您的异常可能是由以下任一选项引起的:

  1. 根据 retrofit sourcecode,可能存在竞争条件,其中 Disposable.dispose() 被调用但超时发生在基础 Call 被取消之前。这将导致在 disposed 之后将超时发送给观察者,从而引发崩溃。
  2. onError 处理程序内部抛出错误。根据 RxJava 协议,这不应该发生,并且会导致崩溃 CompositeException。由于您发布的错误不包括确切的异常 class 不能排除这种情况。