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
error!.localizedDescription gives some more information and is output twice (!):
Success: false, Error: The operation couldn’t be completed. (NSURLErrorDomain error -1011.)
If I ignore "success", I can:
log into the ftp server
list files with ".contentsOfDirectory()"
read files with ".contents()"
download files with ".copyItem()"
just fine and there are no more error messages (still dealing with everything being done twice but that's are different problem).
If I give it an invalid URL, the output after about a minute is pretty similar (the error code is the only difference):
Success: false, Error: The operation couldn’t be completed. (NSURLErrorDomain error -1001.)
Why is it throwing an error message, even though login seems to work and complete just fine?
The text was updated successfully, but these errors were encountered:
Nathipha
changed the title
FTPFileProvider.isReachable resturns error, even though everything's working properly
FTPFileProvider.isReachable returns error, even though everything's working properly
Jun 18, 2019
@Stermop I didn't find a solution when I was using the library. I ended up checking what error code means what and then just ignored the error that was thrown when it was successful.
I'm not using the library anymore though because it doesn't look like @amosavian is supporting it any more and there are a lot more problems than just this one: Even though they are small, the last one I found made the library unusable for me (simply didn't work with my server), so now I'm using BlueSocket and built my own reading/writing library around it.
I'm using the latest version of the library (with Swift 5, Xcode 10) and have just run into the same problem as the author of this closed one:
pretty much instantly always "fails" with the error:
error!.localizedDescription
gives some more information and is output twice (!):If I ignore "success", I can:
just fine and there are no more error messages (still dealing with everything being done twice but that's are different problem).
If I give it an invalid URL, the output after about a minute is pretty similar (the error code is the only difference):
Why is it throwing an error message, even though login seems to work and complete just fine?
The text was updated successfully, but these errors were encountered: