Open Source projects from That Thing in Swift

PermissionScope

PermissionScope

Intelligent iOS permissions UI and unified API — 2,241⭐️ — GithubDocumentation

PermissionScope

Pantry

The missing light persistence layer for Swift — 433⭐️ — GithubDocumentation

Writing files to the documents directory

Where you should write files

Just a quick one today: Pulling the proper documents directory on iOS has always been a pain and a bit of code that I always forget. Here’s a reminder for you and I.

Remember on iOS that we can only write to our application’s documents directory. We’re sandboxed out of most of the system and other applications to save us from each other and we can’t write into to the main bundle because that would defeat our code signature.

In Objective-C, something like this would get us the current documents directory:

NSString *documents = [NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES) objectAtIndex:0];
NSString *filePath = [documents stringByAppendingPathComponent:@"file.plist"];

And you typically find this paired with simple serialization of NSArray or NSDictionary objects:

// reading...
NSArray *objects = [NSArray arrayWithContentsOfFile:filePath];

// or writing
[objects writeToFile:filePath atomically:YES];

The Swift version is similar, but more compact with our more concise constants:

let documents = NSSearchPathForDirectoriesInDomains(.DocumentDirectory, .UserDomainMask, true)[0] as! String
let writePath = documents.stringByAppendingPathComponent("file.plist")

Note our new downcast syntax (as!) for Swift 1.2!

Reading and writing NSArray and NSDictionary is almost exactly alike, aside from checking the optional returned by contentsOfFile:.

let array = NSArray(contentsOfFile: filePath)
if let array = array {
    array.writeToFile(filePath, atomically: true)
}

This is nice if you’re doing something simple but often we’d like to deal with Swift-native Dictionary and Array. Luckily, it’s easy to convert between these older NS-types and our Swift natives. And the objects are much more powerful to deal with if you can cast them into their proper types:

let swiftArray = NSArray(contentsOfFile: filePath) as? [String]
if let swiftArray = swiftArray {
    // now we can use Swift-native array methods
    find(swiftArray, "findable string")
    // cast back to NSArray to write
    (swiftArray as NSArray).writeToFile(filePath, atomically: true)
}

That’s it. It truly is a wonder that I can’t remember it.

Finally, one thing to avoid. You may run into some old Objective-C code that uses this example:

// this returns an NSURL, *not* a NSString!
NSURL *documents = [NSFileManager.defaultManager URLsForDirectory:NSDocumentDirectory inDomains:NSUserDomainMask].firstObject;

I’ve had various permissions issues between the simulator/devices with file urls so I tend to avoid them in favor of path strings. You can go back and forth easily if there’s a particular API that demands one format or the other.


Questions or comments? Find us on twitter or submit an issue on github

You'll get 1-2 emails per month