hasSpaceAvailable become "false" and no failure blocks are called #2496
Conversation
+1 I'm having the issue too. The fix provided seems to do the trick. Any ETA for this fix to be integrated in the POD ? |
it should be already in the current version because was fixed by mattt on 14 feb. |
Still not fixed in 2.6.0 |
Sorry I missed this issue. I'll get it updated soon. Thanks! |
I'm also having this same issue, about 10% of the times. In my tests, the problem seems to be related with low disk space on the device. Although I think this wasn't the case in all the tests. Maybe low disk space or low memory is the reason why NSOutputstream doesn't accept any more data? I also used the provided fix, but I'm not completely sure about it(maybe I just don't understand the way this works):
Maybe there is a way to recognize why hasSpaceAvailable stays false and provide this information to the failure block? |
I'l get this one in today. Hopefully will cut a release before EOD |
hasSpaceAvailable become "false" and no failure blocks are called
Not needed in the 3_0_0 branch since |
It's needs merge to 1.0 version |
I'm using AFNetworking (2.5.0) via Cocoapod in an iOS >7.0 application.
I need to download a binary file so i configured the
outputStream
property90% of the times it works correctly, but in some case the line AFURLConnectionOperation.m@655 became false (i put a breakpoint) and the library enters in an endless loop and no failure blocks are called.
I put here the current implementation of the method
I think that if
[self.outputStream hasSpaceAvailable]
is false (for some reason) but there is not error on the outputStream the while() enters in an infinite loop.