When I use files/rm or cp, it report Error "sending request failed" about gomobile-ipfs

[jefft0]

Hello @westice007 . I am able to reproduce your error with files/cp . For me, I see this error. But if I use files/ls, then it shows that the file was added by files/cp . What does files/ls show on your system?

[westice007]

@jefft0 Instead of using files/ls, I use files/stat to check file, files/ls should be used to check folders

[jefft0]

@westice007 , thanks for the clarification. I mean to ask, even if files/cp shows an error, is the file created on your phone?

[westice007]

When I use files/cp, I get an error, but the file copy is successful, and then I can check the result with files/stat
this is my code:

func exeCpCmd(srcPath: String, mfsPath: String) -> String? {
    do {
        let res = try self.ipfs?.newRequest("files/cp")
            .with(argument: srcPath).with(argument: mfsPath)
            .send()
    } catch let error {
        print("this is bug: exeCpCmd cp: \(error) hashId:\(srcPath) mfsPath:\(mfsPath)")
    }
    
    var changedHash: String?

    do {
        var fileInfo : [String: Any]? = [String: Any]()
        fileInfo = try self.ipfs!.newRequest("files/stat")
        .with(argument: mfsPath)
        .sendToDict()
        changedHash = fileInfo?["Hash"] as? String
    } catch let error {
        //print("exeCpCmd cp: \(error) hashId:\(srcPath) mfsPath:\(mfsPath)")
        
    }
    return changedHash
}

[jefft0]

Thank you for confirming. This is the same behavior for me. We have found the cause of the error. Because files/cp returns an empty response, the return value should be nil. This works in Java (Android), but there is a behavior in the Swift/Go binding code which prevents returning a nil result. We are working on resolving it.

[jefft0]

Hello @westice007 . We merged pull request #135 into master which fixes this crash in the Swift code. Can you please check if it fixes your problem? Thanks.

[jefft0]

As mentioned. We merged a fix. Closing this issue as resolved. If you still see the error, then please open another issue. Thank you.