Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(encoded or binary body omitted) in Request and Response #5

Closed
mapm14 opened this issue Nov 7, 2018 · 6 comments
Closed

(encoded or binary body omitted) in Request and Response #5

mapm14 opened this issue Nov 7, 2018 · 6 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@mapm14
Copy link

mapm14 commented Nov 7, 2018

I have changed from Chuck to Chucker using the steps in the README but now in the Request and Response I get this message instead of the JSON: (encoded or binary body omitted).

I'm using this version of OkHttp: 3.8.1

@olivierperez olivierperez self-assigned this Nov 7, 2018
@olivierperez olivierperez added the bug Something isn't working label Nov 7, 2018
@olivierperez olivierperez added this to the 2.0.2 milestone Nov 7, 2018
@olivierperez
Copy link
Member

This issue has been fixed on the master branch. We will release a 2.0.2 in less than a week.

@mapm14
Copy link
Author

mapm14 commented Nov 8, 2018

That's great! 😃 Thank you, guys. A really awesome job with this fork.

@olivierperez
Copy link
Member

olivierperez commented Nov 12, 2018

Version 2.0.2 is released. Let us know if you still face issues ;-) Have fun!

@mapm14
Copy link
Author

mapm14 commented Nov 19, 2018

Great guys, is solved 👍🏻. But changing from Chuck to Chucker, makes the app crash, you need to clear the data of the app, there is a problem with the database:

Caused by: android.database.sqlite.SQLiteException: no such table: RecordedThrowable (code 1 SQLITE_ERROR): , while compiling: SELECT _id, tag, clazz, message, date FROM 'RecordedThrowable' ORDER BY date DESC

But I'm not sure if this is considered as a bug (maybe yes, because usually people will upgrade from Chuck). Regardless, thank you so much.

@cortinico
Copy link
Member

Yeah this should be considered a bug as we probably use a different DB than Chuck

@olivierperez
Copy link
Member

@mapm14 The crash when updating the database while migrating from Chuck to Chucker is fixed and released in 2.0.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants