Failed to open file at path ‘….default.realm.lock’: Operation not permitted

Hi,
I have a local realm which works great for the most part. But ever since the app is on the store, it seems sometimes the app just fails to open the realm. It’s rare, but it happens, and to the same users.

Fatal error: ‘try!’ expression unexpectedly raised an error: Error Domain=io.realm Code=3 “Failed to open file at path ‘/private/var/mobile/Containers/Shared/AppGroup/…/default.realm.lock’: Operation not permitted” UserInfo={Error Code=3, NSFilePath=/private/var/mobile/Containers/Shared/AppGroup/…/default.realm.lock, Error Name=PermissionDenied, NSLocalizedDescription=Failed to open file at path ‘/private/var/mobile/Containers/Shared/AppGroup/…/default.realm.lock’: Operation not permitted}

I noticed that when these crashes occur the deviceid for the vendor was also returning nil. Maybe it’s related. Currently it’s the highest frequency crash for my app.

Thanks!

No code to replicate the issue.
The error is happens on startup of the app, when initiating realm from the first view controller’s viewDidLoad method. I am not using shouldCompactOnLaunch. It’s worth mentioning the app is written mostly in ObjC, though the code initiating realm is in Swift.

ok this is my app startup:

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
    RLMRealmConfiguration *config = [RLMRealmConfiguration defaultConfiguration];
    config.schemaVersion = 1;
    NSURL *containerURL = [[NSFileManager defaultManager] containerURLForSecurityApplicationGroupIdentifier:@"group.forcam.app"];
    NSURL *realmURL = [containerURL URLByAppendingPathComponent:@"default.realm"];
    config.fileURL = realmURL;
    NSError *error;
    [[NSFileManager defaultManager] setAttributes:@{ NSFileProtectionKey:
                                                         NSFileProtectionNone } ofItemAtPath:[realmURL absoluteString] error:&error];
    [RLMRealmConfiguration setDefaultConfiguration:config];

I added the setAttributes function because of a GitHub issue I tracked (iOS crash due to default.realm.lock': open() failed: Operation not permitted Path · Issue #7874 · realm/realm-swift · GitHub) that I thought could help.

Then in the viewDidLoad of the main app view controller I called:

    @objc static func getAllFavorited(sortedBy sortOption: FavoriteSort = .unsorted) -> [Models] {
        let realm = try! Realm()

and it crashes here.

I add this:

[[NSFileManager defaultManager] setAttributes:@{ NSFileProtectionKey: NSFileProtectionNone } ofItemAtPath:[containerURL absoluteString] error:&error];

But no change. The crash remains.

Hi,
Not entirely sure what you mean, the url returns something like
"file:///Users/myuser/Library/Developer/CoreSimulator/Devices/AA079473-39F2-48EF-906F-39859FA1550B/data/Containers/Shared/AppGroup/BE41F274-4897-435D-A9A2-CD60C0C1DE50/

(on the simulator).

I use `containerURLForSecurityApplicationGroupIdentifier because I have a widget that references the database.

Got it.

Yes the same groupIdentifier is identical to the identifier groups entitlements as well as in the widget group entitlements.

Not using sync. It is a local realm. It does work most of the time.
Out of about around 1M of session in the last week, I have 62 crash reports from 38 users. So it doesn’t happen a lot, but when it does it happens more than once per user.
I can rule out it’s not related to free space on the device. And it’s not related to OS version.

Any other ideas on how to resolve this?

OK,
So because according to the logs, in all cases identifierForVendor is nil, according to identifierForVendor | Apple Developer Documentation

"If the value is nil, wait and get the value again later. This happens, for example, after the device has been restarted but before the user has unlocked the device.

The value in this property remains the same while the app (or another app from the same vendor) is installed on the iOS device. The value changes when the user deletes all of that vendor’s apps from the device and subsequently reinstalls one or more of them. The value can also change when installing test builds using Xcode or when installing an app on a device using ad-hoc distribution. Therefore, if your app stores the value of this property anywhere, you should gracefully handle situations where the identifier changes"

This had to be related. I.E. in this case there’s no access to the folder no matter what. I have to work around it somehow.

Hi,

I’m updating that I have changed the code to use the default path, and I am still able to crash as seen here:

``Fatal error: ‘try!’ expression unexpectedly raised an error: Error Domain=io.realm Code=3 “Failed to open file at path ‘/var/mobile/Containers/Data/Application/EA977B3A-F1CC-4AD1-9247-27298B20385B/Documents/default.realm.lock’: Operation not permitted” UserInfo={Error Code=3, NSFilePath=/var/mobile/Containers/Data/Application/EA977B3A-F1CC-4AD1-9247-27298B20385B/Documents/default.realm.lock, Error Name=PermissionDenied, NSLocalizedDescription=Failed to open file at path ‘/var/mobile/Containers/Data/Application/EA977B3A-F1CC-4AD1-9247-27298B20385B/Documents/default.realm.lock’: Operation not permitted}`

This only occurs when identifierForVendor is nil. It’s likely the device is still locked, or has been reset.

Hi,

I haven’t found a solution yet. But I need to look into this:

That might solve it. If you try please report back.