Closed volic closed 5 months ago
This feels like a misconfiguration of yours with Proguard. You should not use Proguard on debug builds (where Chucker is included)
Thank you for your quick response. We use the Chucker in release (named qa builds) builds. We use them for QA purposes where our testers can observe and extract the API data for bug tickets. Is there no way to use the Chucker in release builds?
We use the Chucker in release (named qa builds) builds. We use them for QA purposes where our testers can observe and extract the API data for bug tickets. Is there no way to use the Chucker in release builds
Well you can but then you'll have to configure proguard so that it doens't strip or obfuscate the classes you see in the stacktrace
@cortinico would you mind adding consumer rules for proguard?
We have the same use case as volic, where we have a separate flavor for QA.
@cortinico would you mind adding consumer rules for proguard?
Happy to receive a PR that adds them 👍
Thank you
:writing_hand: Describe the bug
I cannot export or see the API call information. The chucker is crashing with the release build with R8.
:bomb: Steps to reproduce
:wrench: Expected behavior
The information about API calls is accessible and not crashing.
:camera: Screenshots
:android: Tech info
:page_facing_up: Additional context