You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 17, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 17, 2023. It is now read-only.
Added this to our app the other day and putObjectWithFile works great to send files to our S3 bucket, at least if the files are under 100MB. Ours is a video app and so quite often the upload will be larger.
What happens is when the files get too large (I was using 125MB zip) is that the app starts eating up 128MB chunks of memory until the OS shuts it down. This happens sometime after the call to putObjectWithFile but before the progress callback ever happens.
We never noticed similar problem from windows and browser apps - only mac fails.
Also found few similar problem on the web and stackoverflow- mulitpart fails with timeout when uploading large files.
Unfortunately I cannot find solution how to fix this.
Activity
mattt commentedon Feb 14, 2015
Use
postObjectWithFile:...instead, which uses an HTTP body stream.fitch commentedon Apr 7, 2015
postObjectWithFile:..seems to stall and fail with error code -1001 for me as well.adammordas commentedon Apr 20, 2015
I'm having the same problem too.
dzana commentedon Jun 24, 2015
I'm having the same problem.
I am using only AFNetworking and I created POST exactly the same as in this link:
http://stackoverflow.com/questions/20551548/timeout-posting-to-s3-from-ios-using-signed-urls
Upload fails: Error Domain=NSURLErrorDomain Code=-1001
We never noticed similar problem from windows and browser apps - only mac fails.
Also found few similar problem on the web and stackoverflow- mulitpart fails with timeout when uploading large files.
Unfortunately I cannot find solution how to fix this.