NSFileManager creating folder (Cocoa error 513.)

Question

I\'m trying to create a folder inside the /sounds folder of my app.

-(void)productPurchased:(UAProduct*) product {
    NSLog(@\"[StoreFrontDelegate] Purchase         


        

Answer 1

This is because you should never modify the bundle of your application at runtime. Instead, you should have a folder elsewhere where you can add resources.

EDIT:
The error you are seeing is most likely because you cannot write to the bundle.

Answer 2

I'm still not totally clear on the meaning of the 513 error in my case, but I was getting it when just trying to read an opened file URL using [NSFileHandle fileHandleForReadingFromURL:theUrl error:&err ].

I realized from this answer that with iOS 13, I now need to use startAccessingSecurityScopedResource to access external files that are opened in the app. When I wrapped my file calls as follows, then the error 513 stopped occurring:

if( [myURL startAccessingSecurityScopedResource] ) 
{
    NSFileHandle* myFile = [NSFileHandle fileHandleForReadingFromURL:myURL error:&err ];
    // ...Do file reads here...
    [theUrl stopAccessingSecurityScopedResource];
}

Answer 3

If you search Google on the error domain NSCocoaErrorDomain you find that the code 513 translates to the error NSFileWriteNoPermissionError.

This provides you with the critical clue for solving this problem:

This is the bundle directory containing the application itself. Because an application must be signed, you must not make changes to the contents of this directory at runtime. Doing so may prevent your application from launching later.

Specifically, you cannot modify the contents of a compiled app's bundle folder. This is because the bundle is the compiled application.

When you eventually distribute the app through the iTunes App Store, the application has a digital signature that validates the contents of the app. This signature is generated at compile time.

If you try to change the bundle after compilation, the app changes and the digital signature is no longer valid. This invalidates the application — who knows what code is in there, right? — and end users won't be able to run it. So Apple has set up iOS to throw an error if you try to modify the bundle.

Instead of writing to the bundle, your app can write to one of three accepted app-specific folders: Documents, Temp and Cache. Most likely, you will want to write to the Documents folder.

These folders are only accessible to your app. No other app can access the contents of these folders. (Likewise, your app cannot access another app's folders.)

You can set up your app to allow the end user to manage access to file data through iTunes, via desktop file sharing support.

Answer 4

I encounter the same problem, when using a Log library. Finally, it's path format problem. Check the dataPath format. If it is Case 1, it is valid. In my case, it's Case 2, so I failed to create directory.

// Case 1
/var/mobile/Containers/Data/Application/5FB2CD2D-91DC-4FB2-8D6F-06369C70BB4A/Library/Caches/AppLogs

// Case 2, invalid format
file://var/mobile/Containers/Data/Application/5FB2CD2D-91DC-4FB2-8D6F-06369C70BB4A/Library/Caches/AppLogs

If the dataPath has a prefix, ex: file://, it is invalid.

---

As for an instance of NSURL, path will return the string like case 1, and absolutePath will return the string like case 2.