用拦截器包装非IOException为IOException是否安全？会影响OkHttpClient状态吗？

First, let's break down what's happening here. Your stack trace points to NoSuchElementException coming from RouteSelector.next() — this typically occurs when OkHttp runs out of available routes to try for a connection, but in your OkHttp 3.14.0 version, this isn't being wrapped into an IOException as expected. That's why you're seeing an uncaught runtime exception crashing your app.

Your WrapExceptionsInterceptor Approach Is Valid #

The interceptor you've written is a solid way to handle this scenario:

public class WrapExceptionsInterceptor implements Interceptor {
    @NonNull
    @Override
    public Response intercept(@NonNull Chain chain) throws IOException {
        try {
            return chain.proceed(chain.request());
        } catch (IOException e) {
            throw e;
        } catch (Exception e) {
            throw new IOException(e);
        }
    }
}

By catching all non-IOException exceptions and wrapping them into an IOException, you ensure Retrofit treats them as network failures (instead of uncaught runtime exceptions that crash the app). This aligns with how OkHttp is designed to signal request failures.

Will This Leave OkHttpClient in an Invalid State? No #

Your main concern is totally reasonable, but rest assured this won't break your OkHttpClient's state:

• OkHttpClient is designed to be thread-safe and stateless for global configuration — all request-specific state (like Transmitter, Exchange, RouteSelector) is isolated to individual requests.
• The interceptor operates on a per-request Chain object, which contains all context for that single request. Wrapping an exception here only affects that specific request's outcome, not the underlying OkHttpClient instance.
• In OkHttp 3.14.0, core client state (like connection pools, dispatcher) isn't modified by request-level exceptions. Even if a request throws an exception, the client remains ready to handle future requests normally.

Additional Tips #

• Add context to wrapped exceptions: Modify the wrapping line to include a message for easier debugging:

  throw new IOException("Wrapped non-IO exception during HTTP request execution", e);
  

• Place the interceptor correctly: Add it using OkHttpClient.Builder.addInterceptor() (not addNetworkInterceptor()) so it catches exceptions from all parts of the request lifecycle — including application-level interceptors, OkHttp's internal logic, and network interceptors.
• Consider upgrading OkHttp (if possible): Newer OkHttp versions (4.x+) fix this specific NoSuchElementException issue by automatically wrapping it into an IOException. If you can't upgrade right now, your interceptor is a perfect workaround.

内容的提问来源于stack exchange，提问作者Nikola Knežević