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

Decompression failed: incorrect header check #5

Closed
edwin123chen opened this issue Aug 5, 2015 · 5 comments
Closed

Decompression failed: incorrect header check #5

edwin123chen opened this issue Aug 5, 2015 · 5 comments

Comments

@edwin123chen
Copy link

When i use the source, but i will raise error to say: Decompression failed: incorrect header check

How can i fix the problem?

I try a lot to search help from google, but no good answer and i still have such problem, can you please help?

@1024jp
Copy link
Owner

1024jp commented Aug 5, 2015

Hmm, it can related to #4.
I'll check the code later.

@1024jp
Copy link
Owner

1024jp commented Aug 5, 2015

Anyway, did you confirmed the followings?:

  1. The data (file) can be decompressed with other application (e.g. Finder).
  2. The error always raises, or with a specific data.

@edwin123chen
Copy link
Author

thanks for the answer.
Actually, i try to compose data from network (with below url: http://hq.sinajs.cn/list=sh600208).
In the closure, i am using below code:
var task = session.dataTaskWithURL(url) {
(data, response, error) -> Void in
if error !=nil {
...
}else{
println("data is: (data.gunzippedData())")
}
}

Then error raise in the console to say: Decompression failed: incorrect header check.

@edwin123chen
Copy link
Author

Anyway, did you confirmed the followings?:

The data (file) can be decompressed with other application (e.g. Finder).
=>yes, it can be open in chrome
=> and if i print the data directly, i can print some data even it is not my expected data format
The error always raises, or with a specific data.
=>yes. the error always raise...

@1024jp
Copy link
Owner

1024jp commented Apr 20, 2024

This issue was closed because it has been inactive for years since the last update and may be outdated.

@1024jp 1024jp closed this as not planned Won't fix, can't repro, duplicate, stale Apr 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants