Filepicker uploads fail with 404 when using AFNetworking version 2.6.1

[mobilejohnw]

UPDATE: Per the comment from @newyorkpizza below, I have confirmed that this issue is related to the AFNetworking version. On AFnetworking version 2.6.1 I see the problem, on 2.6.0 everything seems to work.

ORIGINAL COMMENT: I integrated filepicker into the ios app we are building a couple of months ago. At that time it was working fine, but coming back to that feature now we are getting errors that look like this:

+[FPLibrary uploadLocalURLToFilepicker:named:ofMimetype:usingOperationQueue:success:failure:progress:] [Line 266] Uploading multipart 2015-10-30 10:51:03.173 Pairade[5573:767340] __96+[FPLibrary uploadDataURL:named:toPath:ofMimetype:usingOperationQueue:success:failure:progress:]_block_invoke115 [Line 157] File upload failed with Error Domain=com.alamofire.error.serialization.response Code=-1011 "Request failed: not found (404)" UserInfo=0x7fb288ddaf10 {NSUnderlyingError=0x7fb28b37f210 "Request failed: unacceptable content-type: text/html", com.alamofire.serialization.response.error.response=<NSHTTPURLResponse: 0x7fb28b2f7bf0> { URL: https://dialog.filepicker.io/api/path/computer/?multipart=start } { status code: 404, headers { "Content-Length" = 16; "Content-Type" = "text/html; charset=utf-8"; Date = "Fri, 30 Oct 2015 15:51:03 GMT"; Server = nginx; "Set-Cookie" = "session=\"oWXYg2NwHaBHSxoHUvtmtM7wh5w=?_id=UydceDgyXHhhNXNPXHg5YVx4YzZceGM3XHQ/ZFx4MTFceGVhXHhlOFx4MGNceGM5XHhjNScKcDEKLg==\"; Domain=dialog.filepicker.io; Path=/; HttpOnly"; } }, NSErrorFailingURLKey=https://dialog.filepicker.io/api/path/computer/?multipart=start, com.alamofire.serialization.response.error.data=<4170694b 6579206e 6f742066 6f756e64>, NSLocalizedDescription=Request failed: not found (404)}, response was: (null)

I tested changing the api on the account and updating the app, but that didn't help. What could be happening?

[newyorkpizza]

@mobilejohnw, I hit the same problem. Are you using AFNetworking 2.6.1? Going back to 2.6.0 solved the problem for me. The cause seems to be a changed in behavior in AFURLRequestSerialization.m.

[mobilejohnw]

@newyorkpizza, Yes! regressing to AFNetworking 2.6.0 restores the functionality! I'll amend this issue to reflect its nature.

[nitinhayaran]

+1