Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Version 3.1.0 always claims that response body is empty

See original GitHub issue

📢 Describe the bug

After upgrading chucker to version 3.1.0 every single response shows 0 byte size and null body. In app everything works as expected. Downgrading to 3.0.1 fixes the issue

💣 To Reproduce

Do some api request. Go to chucker and click on it. Request is properly shown, but response body is “null”. Response size is always 0 bytes"

🔧 Expected behavior

Body should be always properly shown.

📷 Screenshots

📱 Smartphone

Device: Android Emulator
OS: Android 9
Lib version: 3.1.0

📄 Additional context

Whole request copied as text:

URL: <redacted>
Method: GET
Protocol: http/1.1
Status: Complete
Response: 200 OK
SSL: Yes

Request time: Fri Jan 24 10:58:58 GMT+01:00 2020
Response time: Fri Jan 24 10:58:58 GMT+01:00 2020
Duration: 67 ms

Request size: 0 B
Response size: 0 B
Total size: 0 B

---------- Request ----------

appInstallId: cc5a34e6-9ccf-46d4-9297-04f74a18355e
User-Agent: Android: 1.0.7-rc-dbg-dev (5) ; debug ; debuggableDev
Device-Name: AOSP On IA Emulator
HMAC: 6a2b11
Authorization: Bearer <token here>



---------- Response ----------

content-type: application/json; charset=utf-8
vary: Accept-Encoding
server: envoy
api-supported-versions: 1.0
date: Fri, 24 Jan 2020 09:58:56 GMT
x-envoy-upstream-service-time: 22

null

My chucker setup is fairly typical:

// setup collector
val chuckerCollector = ChuckerCollector(
            context = applicationContext,
            showNotification = false,
            retentionPeriod = RetentionManager.Period.ONE_DAY
        )

// adding interceptor
builder.addInterceptor(
            ChuckerInterceptor(
                context,
                collector = chuckerCollector
            )
        )

I have quite a few interceptors along the way. ChuckerInterceptor is almost last in the chain, after it there is only RetryInterceptor

Issue Analytics

State:
Created 4 years ago
Comments:13

Top GitHub Comments

2reactions

vbuberencommented, Jan 24, 2020

Thanks for a really fast feedback. We are going to release a hot-fix today in the evening.

@cortinico It is also might be the case for adding some other test requests into sample to catch such cases as well as add tests in code.

1reaction

jakosscommented, Jan 26, 2020

Sure I’ll move it first thing tomorrow morning.

Just a big json

Top Results From Across the Web

c# - Response body empty after updating from Core 2.0 to 3.1.1

The token is created correctly and from what I can tell everything is just as before, except the response body becomes empty.

HTTPie 3.2.1 (latest) docs

There are no restrictions regarding which request methods can include a body. You can send an empty POST request: $ http POST pie.dev/post....

How to Build CRUD REST APIs with ASP.NET Core 3.1 and ...

This blog post explains how to build CRUD REST APIs with ASP.NET Core 3.1 and Entity Framework, create a JWT, and secure APIs....

Table of Contents - Micronaut Documentation

UriBuilder methods queryParam and replaceQueryParam ignore null values. It is possible to stop the Netty server without stopping the Application context. You ...

ASP.NET Core breaking changes | Microsoft Learn

NET Core breaking changes for versions 3.0 and 3.1 ... The infrastructure backing an HTTP response body has changed.