-
-
Notifications
You must be signed in to change notification settings - Fork 735
ParseRequestException: i/o failure in ParseDecompressInterceptor on 1.12.0 on API<19 devices #355
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
Comments
Seems to be similar to #325. |
…d#355 and convert the DonationCategory fetch to an Observable.
Thank you for your feedback. We prioritize issues that have clear and concise repro steps. Please see our Bug Reporting Guidelines about what information should be added to this issue.
|
Hi @aphexcx, could you try ParseLogInterceptor and paste your request here? |
Added it (version 0.0.2) and the problem went away. Very strange how adding the interceptor made the query work, like what happened to the guy in #326. I expected it to still fail, but show some additional logging. Here's the ParseLogInterceptor log. As you can see, the query succeeds after a few errors (looks like it retries):
|
Should be noted that like in #326 (comment), I'm also trying to query for 9 items and running into failure. Weird edge case! |
Having the same issue testing with a Samsung Galaxy S2. API 16. |
Hi @aphexcx, I can repo this issue. It seems like a valid bug. I will dig into this issue and update the status. |
The cause of this problem is related gzip response stream. There are two reasons:
Thus, in 1.12.0, when we use ApacheHttp, since we always have |
A lot of my users are facing this bug too, whats the solution? Fixed in next release? |
The solution for now is simply to rollback to Parse 1.11.0. Looks like he On Fri, Jan 22, 2016, 15:31 Alex Black [email protected] wrote:
|
I'm still experiencing |
I (and other developers) are getting errors with 1.12.0 on older devices (seemingly API 19 and below). http://stackoverflow.com/questions/34561280/android-parse-sdk-i-o-failure-unknown-format-magic-number-227b
My stacktrace, from an API 18 device:
The text was updated successfully, but these errors were encountered: