Returns bookmark data for a URL, created with specified options and resource values.
- iOS 4.0+
- macOS 10.6+
- tvOS 9.0+
- watchOS 2.0+
- Core Foundation
The allocator to use to allocate memory for the new
kto use the current default allocator.
The URL that bookmark data is being created for.
Options taken into account when creating the bookmark data.
To create a security-scoped bookmark to support App Sandbox, include (by way of bitwise
ORoperators with any other options in this parameter) the
When you later resolve the bookmark, you can use the resulting security-scoped URL to obtain read/write access to the file-system resource pointed to by the URL.
If you instead want to create a security-scoped bookmark that, when resolved, enables you to obtain read-only access to a file-system resource, bitwise
ORthis parameter’s value with both the
withoption and the
Scope Allow Only Read Access
An array of names of URL resource properties. The values of these properties must be of a type that the bookmark generation code can serialize. Specifically, the values can contain any of the following primitive types:
In addition, the properties can contain the following collection classes:
CFArraycontaining only the above primitive types
CFStringkeys, in which all values contain only the above primitive types
The URL that the bookmark data is relative to.
If you are creating a security-scoped bookmark to support App Sandbox, use this parameter as follows:
To create an app-scoped bookmark, use a value of
To create a document-scoped bookmark, use the absolute path (despite this parameter’s name) to the document file that is to own the new security-scoped bookmark.
The error that occurred in the case that the bookmark data cannot be created.
The bookmark data for the URL.
To use this function to create a security-scoped bookmark to support App Sandbox, you must first have enabled the appropriate entitlements for your app, as described in Enabling Security-Scoped Bookmark and URL Access. In addition, be sure to understand the behavior of the
For an app-scoped bookmark, no sandboxed app other than the one that created the bookmark can obtain access to the file-system resource that the URL (obtained from the bookmark) points to. Specifically, a bookmark created with security scope fails to resolve if the caller does not have the same code signing identity as the caller that created the bookmark.
For a document-scoped bookmark, any sandboxed app that has access to the bookmark data itself, and has access to the document that owns the bookmark, can obtain access to the resource.