-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
IOException: ID1ID2: actual 0x00000a3c != expected 0x00001f8b #299
Comments
0x0a3c is a newline followed by |
Or, put another way, this isn't an Okio or OkHttp problem but likely a problem with the server you're talking to. You can set the |
ok, thank you for definition @JakeWharton! |
Sorry, We have the same problem in our project. The backend team said that no problem on their side. On the app side, we have a lot of network interceptors adding to okhttp client. Is this might be the cuase ? |
@JakeWharton same problem here: Server switched from not gzipped to gzipped and the |
@JakeWharton Same problem |
I sent header |
thank you |
Accept-Encoding: identity solved the issue. Thanks @JakeWharton |
Anyone who face this issue, check if something wrong with any of your interceptors before adding Accept-Encoding: identity. For me, I was using AndroidSnooper library for logging network calls and that (interceptor from library) was causing the issue. |
If this happens on production and you happen to be using proguard, try disabling it first and then test the app again to check if this issue gets resolved.
|
The text was updated successfully, but these errors were encountered: