3

Right now I'm in the process of migrating from Swift 1.2 to Swift 2.0.

The project I'm working on uses Realm as a database. Everything works fine in Swift 1.2 on both, device and simulator. But I get this error with Swift 2.0 when running app on device:

fatal error: 'try!' expression unexpectedly raised an error: Error
Domain=io.realm Code=1 "open() failed: Operation not permitted"
UserInfo=0x145e2bc0 {Error Code=1, NSLocalizedDescription=open() failed:
Operation not permitted}: file /Library/Caches/com.apple.xbs/Sources/swiftlang/swiftlang-
700.0.57.3/src/swift/stdlib/public/core/ErrorType.swift, line 50

Realm is being initialized with this base path:

NSSearchPathForDirectoriesInDomains(.DocumentDirectory,
      .UserDomainMask, true).first!

i.e. user documents directory. I can access files with NSFileManager and actually see Realm files there.

Any clues how to debug this issue? Seems that Realm just crashes on initialization.

Keith Smiley
  • 61,481
  • 12
  • 97
  • 110
Richard Topchii
  • 7,075
  • 8
  • 48
  • 115

1 Answers1

2

If you're getting an open() failed error, more often than not, it means that the path you've supplied is still invalid in some way.

In this case, I'm guessing you might not have specified the actual file name of the Realm file you wish to create in that Documents path. When setting the path of a Realm file (Whether the default one, or a new one), you have to make sure the path is an absolute one, down to and including the file name.

TiM
  • 15,812
  • 4
  • 51
  • 79
  • 1
    You were quite close to the actual solution: The problem was that `NSSearchPathForDirectoriesInDomains(.DocumentDirectory, .UserDomainMask, true).first!` returned path with `/` at the end in Swift 1.2 and started to return without ending `/` in Swift 2.0. Adding `/` to the path solved the issue: `let documentsDirectory = NSSearchPathForDirectoriesInDomains(.DocumentDirectory, .UserDomainMask, true).first!` `let realmPath = "\(documentsDirectory)/database.realm"` – Richard Topchii Sep 10 '15 at 09:23
  • 1
    Oh, cool! Good to hear! Hmm, if it's simply a a case of needing to account for a trailing slash or not, I'd totally recommend using `stringByAppendingPathComponent` method from `NSString` here, since it can account for those automatically. :) Good luck! – TiM Sep 12 '15 at 15:28
  • Reminder that `stringByAppendingPathComponent` is deprecated use NSURL going forward. For example, `NSURL(string:NSTemporaryDirectory())!.URLByAppendingPathComponent("yourrealm.realm").absoluteString` –  Oct 06 '15 at 20:48
  • Ah, that would explain why I couldn't find it in any Swift documentation. Thanks for the heads-up! – TiM Oct 08 '15 at 09:12