Failed requests show a "failed" response instead of the actual response received by the server

[ayaxan7]

[siddharthjaswal]

Thanks for the report — you're right that "(failed)" is useless. The interceptor actually captures the exception, but the plugin was never displaying it.

Fixed in #2:

• The Response card now shows the captured exception (e.g. connection reset, timeout, CLEARTEXT communication not permitted) instead of "(failed)", and the Overview card surfaces it too.
• On the library side, the interceptor now captures any throwable from the chain (not just IOException), so a failure can no longer leave a transaction stuck "pending".

One thing worth clarifying about "the actual response received by the server": in the screenshot the call threw before OkHttp handed a Response back to the interceptor, so there genuinely isn't a response object to render — the most we can show is why it failed, which is what the fix now does.

If you're seeing this on requests where the server did respond (e.g. a non-2xx that another interceptor turns into an exception), that usually means LogPose is registered before that interceptor and the response is consumed before it reaches us. LogPose needs to be the last addInterceptor(...) so it sees the final response. Can you share where LogPoseInterceptor sits in your OkHttpClient.Builder chain? That'll tell us which case you're hitting.

[siddharthjaswal]

Resolved and merged to main via #2.

• Plugin (v0.9.10): failed requests now show the captured exception in the Response and Overview cards instead of "(failed)". The signed build will appear on the JetBrains Marketplace shortly.
• Library: the interceptor now captures any throwable from the chain, so failures can't leave a transaction stuck "pending". Ships via JitPack on the next tag.

Closing this out. If you find the response is still missing on calls where the server did respond, that's the interceptor-ordering case mentioned above — drop your OkHttpClient.Builder chain here and we'll take another look.

[ayaxan7]

@Provides
@Singleton
fun provideOkHttpClient(): OkHttpClient {
    val logging = HttpLoggingInterceptor().apply {
        level = HttpLoggingInterceptor.Level.BODY
    }

    return OkHttpClient.Builder()
        .addInterceptor(logging)
        .addInterceptor(LogPoseInterceptor(LogPoseConfig(enabled = BuildConfig.DEBUG)))
        .connectTimeout(30, TimeUnit.SECONDS)
        .readTimeout(30, TimeUnit.SECONDS).writeTimeout(30, TimeUnit.SECONDS).build()
}

this is how i used it and got the below issue, it is a network error btw