-
Notifications
You must be signed in to change notification settings - Fork 27
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
StrictMode error: Explicit termination method 'response.body().close()' not called #17
Comments
These warnings seemed to have resurfaced after: #14 |
Hi, can you share how do you set the StrictMode, I tried with
And
Could not manage to see any StrictMode complains. Also seems that should be safe to do call.cancel() from Main thread, it used to be an issue but now is fixed |
From OkHttp docs
|
@skimarxall we setup Strict mode like so:
|
I did not try the VM policy either with the penalty log, I will, but as mentioned in the other comment is it safe to call cancel from any thread |
I think my PR is resolving this. #24 |
I just merged the fix, please try the new version and let me know if the warning is solved |
Seems like problem still exists. |
@kashesoft could you make sure you are using the last version and if so, copy the logcat and the strict policy configuration you are using? |
Yes, we are using
Logcat:
|
0.9.0 suffers from a response body leak [1] [1] heremaps/oksse#17 Signed-off-by: Danny Baumann <[email protected]>
Fixes #1560 * Update OkSse to latest master branch. 0.9.0 suffers from a response body leak [1] [1] heremaps/oksse#17 Signed-off-by: Danny Baumann <[email protected]> * Simplify code Co-Authored-By: mueller-ma <[email protected]>
The following code throws a StrictMode error:
Version:
The text was updated successfully, but these errors were encountered: