Dropbox SDK for iOS works on simulator, not on actual device

[ Cross-linking for reference: https://stackoverflow.com/questions/30313546/dropbox-sdk-for-ios-works-on-simulator-not-on-actual-device ]

I posted an answer on your StackOverflow question a little while ago. Can you check if that was the issue?

Ah, I just noticed you did mention here that you cleared the device in this post. Can you add some logging to check the destination path explicitly and post the output then?

Hi Greg, appreciate the replies. I've been tearing my hair out tonight over the issue, but I'll try to do some logging tomorrow and post the results.

Hi again, I did some testing using NSFileManager. I Added this piece of code before downloading the file into the path:

if fileManager.fileExistsAtPath(localPath) {
    println("File exists")
} else {
    println("File does not exist")
}

On the simulator it prints "file exists", but it downloads the file to the desired location anyways, just overwriting the existing file. On my actual device it prints "file exists", but is unable to overwrite.

So i tried this:

if fileManager.fileExistsAtPath(localPath) {
     println("File exists")
     fileManager.removeItemAtPath(localPath, error: nil)
} else {
     println("File does not exist")
}

(This code twice in a row, to check if file was removed successfully)

On simulator i get: File exists, File does not exist.
So again, simulator working as expected.
On iPhone i get: File exists, File exists. -> (so still not able to download the item).

The error I get (when I'm not just setting error: nil), is the following on iPhone:

Error Domain=NSCocoaErrorDomain Code=513 "The operation couldn’t be completed. (Cocoa error 513.)" UserInfo=0x17407bf00 {NSFilePath=/private/var/mobile/Containers/Bundle/Application/28F41502-82FC-425D-AF49-31AF48A789E6/Home Alone.app/Units.txt, NSUserStringVariant=(Remove), NSUnderlyingError=0x1740578b0 "The operation couldn’t be completed. Operation not permitted"}

So it turns out permission issues with my chosen directory was the problem. Simulator just did not care about permissions, or does not use the same set of rules as the actual device as to where the user is allowed to edit the files. I got it working by using the default app documents folder, found by using applicationDocumentsDirectory() instead.

Great, I'm glad to hear you were able to sort this out.