A service that provides a custom communication channel between your app and a File Provider extension.
- iOS 11.0+
- macOS 10.13+
- Mac Catalyst 13.0+
To communicate, both your app and the File Provider extension must implement their part of the service:
Your app requests the proxy object, and calls its methods.
The File Provider extension declares the supported services and vends a proxy object that implements the protocol for each service.
The app and File Provider extension communicate using an XPC service. This service performs actions only on items managed by the File Provider extension. For more information, see Creating XPC Services.
Defining the Service’s Protocol
Services let you define custom actions that are not provided by Apple’s APIs. Both the app and the File Provider extension must agree upon the service’s name and protocol. Communicate the name and protocol through an outside source (for example, posting a header file that defines both the name and protocol, or publishing an library that includes them both).
The service can be defined by either the app or the File Provider extension:
Apps can define a service for features they would like to use. File providers can then choose to support those features by implementing the service.
File Provider extensions can provide a service for the features they support. Apps can then choose to use the specified service.
When defining a service’s protocol, the parameters for each method must adhere to the following rules:
The parameter’s class must conform to
The parameter’s class must be defined in both the app and the File Provider extension (for example, standard system types or classes defined in a library imported by both sides).
If a collection parameter contains types other than property list types (see Property List Types and Objects), declare the valid types using the
argument Index: of Reply:)