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

iOS 9 compatability/readiness? #404

Open
ghost opened this issue Aug 6, 2015 · 9 comments
Open

iOS 9 compatability/readiness? #404

ghost opened this issue Aug 6, 2015 · 9 comments

Comments

@ghost
Copy link

ghost commented Aug 6, 2015

Are there are any known issues with iOS9?

@jhollida24
Copy link

I'm curious about this as well. App Transport Security Layer requirements worry me.

@hirenj102
Copy link

Why asihttp,asiformdatarequest not working in iOS 9?Please help me

@michalcichon
Copy link

Hi, for us, the library is generally working in iOS 9 (we have a project with deployment target set to 6.0) but have strange issues in iOS 9 with cutting responses. We have some services that gives us Base64 images in responses (responses are in JSON) but sometimes (randomly), JSONs are cut in random places. We checked whether the server responds correctly, but JSONs in revers proxy are OK.

Have anyone any idea what can be wrong? The library works fine in iOS 6, 7, 8 and in most cases (really, about 90% of our services) in iOS 9.

@pabloburnio
Copy link

@michalcichon - I'm also looking into intermitted issues with requests failing (seems to be since our release on ios9) - mainly for larger requests and for people on poorer connections. All traffic is over https in our case so wouldn't have thought it was ATS as I would have expected all, not just some requests to fail.

Did you manage to find anything at all? Appreciate any info - thanks.

@michalcichon
Copy link

@pabloburnio We checked whether it's the issue with decompression because our requests differed only in IDs (that we are randomising because of some security issues) but the decompression was OK. We found out that the length of the request is OK, but some requests had some last bits set to NULL. That's strange.

It was not ATS issue but we cannot find connection between poor connection and the issue. We use https only and most of our services work great. The problem is only with one service with Base64 images.

@pabloburnio
Copy link

@michalcichon - Ah I see, thanks for the info anyway! Could be your base64 implementation, possibly not flushing the remaining bytes? Best of luck!

@michalcichon
Copy link

@pabloburnio Nope. Base64 is OK and it works on the different layer. ;) It's probably the issue with the library. We will probably change the lib to the other one, since we cannot find the root of the problem.

@chatvenkat
Copy link

hi i'm trying to use this in ios 9 and getting -[CFString release]: message sent to deallocated instance 0x7fe1b5b796f0

caused by this line when i segue to different view upon successful completion of this request.
[asiRequest setData:imageData1 withFileName:@"avatar.jpg" andContentType:@"image/jpeg" forKey:@"avatar"];

any one faced this issue ?

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

6 participants