Large json responses result in bad user experience about chucker HOT 9 CLOSED

Just tried out this library and it looks great, but the one thing keeping me from migrating over from Chuck is this issue where large json responses cause Chucker to hang and then eventually crash after you try and swipe from the Overview tab to either the Request or Response tab (probably when the data starts to get loaded into the Response tab).

Chuck is able to show these responses (even if there is no ability to search) so for now, I'll have to stay with Chuck.

Looking forward to trying this library again in the future, it looks great!

from chucker.

Actually, being able to open any response as a file with another viewer sounds like a great idea!

from chucker.

@cortinico yes this is still happening. I am using 3.0.1

from chucker.

Part of this issue was addressed by @redwarp in #72

Edit 2: Maybe just show the first x amount of lines, but still provide a way to export or view the json as a file?

You can set the maxContentLength on the ChuckerInterceptor to truncate the body if needed (but still you won't be able to export or share the full body afterwards).

Curious to hear what others think about this

from chucker.

Gotcha. I think after a certain size maybe 500k or something the text just gets treated as a file. Then in the response tab it can say "Response exceed x" with a button that opens the file in another file viewer. Also, the share as text would turn into a "Share as file" button?

from chucker.

Sounds more like as a feature-request.
Definitely valuable to implement :)

from chucker.

Just bumping this. Tried using Chucker on a new project and it's completely useless because of large json. It just ANRs. 😭

from chucker.

Just bumping this. Tried using Chucker on a new project and it's completely useless because of large json. It just ANRs.

Thanks for bumping. Is this still happening? If yes, which version are you using? 3.0.1?

from chucker.

Ok so after some investigation, turns out the issue is on the TransactionPayloadFragment. When dealing with big payloads, we hang the UI thread by setting the text of a TextView with a huge String:

I do have a proposed fix for this, that unfortunately has a couple of drawbacks.

Chuck is able to show these responses (even if there is no ability to search)
so for now, I'll have to stay with Chuck.

@kmayoral I've tried Chuck with the HTTP request that was suggested on top of this thread (https://data.cityofnewyork.us/api/views/kku6-nxdu/rows.json) and the behavior is exactly the same. Are you sure of this?

from chucker.