okhttp

Question

我在 android 应用程序中使用 Retrofit，这反过来意味着我在使用 OkHttp。我刚刚去了 Alpha 并在我的 crashlytics 报告中看到记录了许多非致命异常。所有这些都源于我的 okhttp 拦截器，然后记录的异常似乎都是在网络不稳定或连接断开等情况下有效的东西。

我怎样才能做到这些异常不会被注销到 crashlytics，从而使我对应用程序中发生的异常的看法变得混乱？

一些例外示例：

> Non-fatal Exception: javax.net.ssl.SSLHandshakeException
Connection closed by peer
okhttp3.internal.connection.RealConnection.connectTls (RealConnection.java:281)
okhttp3.internal.connection.RealConnection.establishProtocol (RealConnection.java:251)
okhttp3.internal.connection.RealConnection.connect (RealConnection.java:151)
okhttp3.internal.connection.StreamAllocation.findConnection (StreamAllocation.java:192)
okhttp3.internal.connection.StreamAllocation.findHealthyConnection (StreamAllocation.java:121)
okhttp3.internal.connection.StreamAllocation.newStream (StreamAllocation.java:100)
okhttp3.internal.connection.ConnectInterceptor.intercept (ConnectInterceptor.java:42)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.java:92)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.java:67)
okhttp3.internal.cache.CacheInterceptor.intercept (CacheInterceptor.java:93)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.java:92)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.java:67)
okhttp3.internal.http.BridgeInterceptor.intercept (BridgeInterceptor.java:93)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.java:92)
okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept (RetryAndFollowUpInterceptor.java:120)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.java:92)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.java:67)
MY_INTERCEPTOR.intercept (AuthenticationInterceptor.java:30)

和

> Non-fatal Exception: javax.net.ssl.SSLException
Read error: ssl=0xdee45cc0: I/O error during system call, Software caused connection abort
okio.Okio.read (Okio.java:139)
okio.AsyncTimeout.read (AsyncTimeout.java:237)
okio.RealBufferedSource.indexOf (RealBufferedSource.java:345)
okio.RealBufferedSource.readUtf8LineStrict (RealBufferedSource.java:217)
okio.RealBufferedSource.readUtf8LineStrict (RealBufferedSource.java:211)
okhttp3.internal.http1.Http1Codec.readResponseHeaders (Http1Codec.java:189)
okhttp3.internal.http.CallServerInterceptor.intercept (CallServerInterceptor.java:75)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.java:92)
okhttp3.internal.connection.ConnectInterceptor.intercept (ConnectInterceptor.java:45)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.java:92)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.java:67)
okhttp3.internal.cache.CacheInterceptor.intercept (CacheInterceptor.java:93)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.java:92)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.java:67)
okhttp3.internal.http.BridgeInterceptor.intercept (BridgeInterceptor.java:93)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.java:92)
okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept (RetryAndFollowUpInterceptor.java:120)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.java:92)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.java:67)
MY_INTERCEPTOR.intercept (AuthenticationInterceptor.java:30)

这是我的拦截器代码：

@Override
public Response intercept(Chain chain) throws IOException {
    Request request = chain.request();
    Response response = chain.proceed(request);

    if( response.code() == HTTP_AUTHENTICATION_ERROR_CODE ){
        Intent intent = new Intent(ACTION_LOGOUT_ACTION);
        mContext.sendBroadcast(intent);
    }
    return response;
}

我知道我可以从 "proceed" 调用中捕获任何 IOException，但这不会搞乱 OkHttp 对网络错误等的正确处理吗？

Answer 1

Non-fatal Exception 在代码中显式调用 Crashlytics.logException(Exception) 时被记录

请阅读以下信息：

Crashlytics for Android 让您可以在应用程序的 catch 块中记录捕获的异常！要使用此功能，只需将对 Crashlytics.logException(Exception) 的调用添加到您的 catch 块：

try {
  myMethodThatThrows();
} catch (Exception e) {
  Crashlytics.logException(e);
  // handle your exception here! 
}

所有记录的异常将在 Crashlytics 仪表板中显示为 "non-fatal" 个问题。您的问题摘要将包含您用于从崩溃中获取的所有状态信息以及 Android 版本和硬件设备的故障。

Answer 2

Crashlytics only stores Non-fatal Exception when you use
Crashlytics.logException(), see the below code for interceptor , it's throwing IOException but exception will not be visible on dashboard on Non-fatal Exception section , while we not log it.

@Override 
public Response intercept(Interceptor.Chain chain) throws IOException {
Request request = chain.request();

long t1 = System.nanoTime();
logger.info(String.format("Sending request %s on %s%n%s",
    request.url(), chain.connection(), request.headers()));

Response response = chain.proceed(request);

long t2 = System.nanoTime();
logger.info(String.format("Received response for %s in %.1fms%n%s",
    response.request().url(), (t2 - t1) / 1e6d, response.headers()));

return response;
}

so if you want to log the exception under Non-fatal Exception , just use Crashlytics.logException();

并且 Crashlytics 仅存储给定应用会话中最近的 8 个异常。如果您的应用在一个会话中抛出 8 个以上的异常，较旧的异常将丢失。

Answer 3

只需在您的代码库中搜索 Crashlytics.logException，您一定会在某个地方找到它。仅从那里记录。

否则 Response response = chain.proceed(request); 上的任何异常 将导致您的应用程序崩溃:)

大胆猜测 :), 您可能正在使用 RxJava 并且在您订阅者的 onError(throwable: Throwable) 中您可能会像下面那样记录它

override fun onError(throwable: Throwable) {
       Crashlytics.logException(throwable) 
}

okhttp - 拦截器 - 阻止非致命异常记录到 Crashlytics

okhttp - Interceptor - Stopping non-fatal exceptions from being logged to Crashlytics

java

android

interceptor

retrofit2