Key Summary

Table 1 contains an alphabetical listing of Cocoa keys, the corresponding name for that key in the Xcode property list editor, a high-level description of each key, and the platforms on which you use it. Detailed information about each key is available in later sections.

GCSupportedGameControllers

GCSupportedGameControllers (array (dictionary (string : string)) - tvOS, iOS, and macOS) Optional key, used only during the App Store submission process, that specifies the types of game controllers allowed or required for your app.

The value for this key is an array. Each array element is a dictionary whose key string is “ProfileName” and whose value string is one of the following:

• Gamepad - Specifies the standard gamepad, supported in iOS 7.0 and later only, corresponding to a formfitting controller for an iOS device with a limited set of controls. Used with the GCGamepad class.

• ExtendedGamepad - Specifies the extended gamepad, supported in tvOS 9.0 and later, iOS 7.0 and later, macOS 10.9 and later, and corresponding to either a formfitting controller for an iOS device or a standalone controller for iOS, macOS, or tvOS with an extended set of controls. Used with the GCExtendedGamepad class.

• MicroGamepad - Specifies the micro gamepad, supported in tvOS 9.0 and later, and corresponding to a Siri Remote or the Apple TV Remote app running on a connected iOS device. Used with the GCMicroGamepad class.

Supported in tvOS 9.0 and later, iOS 7.0 and later, macOS v10.9 and later.

GCSupportsMultipleMicroGamepads

GCSupportsMultipleMicroGamepads (Boolean - tvOS). Specifies that the Apple TV Siri Remote and devices running the Apple TV Remote app should each operate as a discrete game controller. Default value is NO, indicating that input from all connected remotes is unified.

Specifically, in a Game Controller framework-based tvOS app that uses a value of NO for this key, all connected remotes are routed to a single GCController object in your app. When a user presses the A button on the Siri Remote, for example, the same in-app action is invoked as if they had pressed the A button on any connected Apple TV Remote app on a device.

If you instead specify a value of YES for this key, your tvOS app employs an independent GCController object for each connected remote.

Supported in tvOS 10.0 and later.

GKGameCenterBadgingDisabled

GKGameCenterBadgingDisabled (Boolean - iOS). This key determines if badges are added to your turn based app icon. Set the value of this key to YES to opt out of badging. Defaults to NO.

GKShowChallengeBanners

GKShowChallengeBanners (Boolean - iOS). This key determines if challenge banners are displayed within an app. Set the value of this key to YES to show challenge banners in the app. Set the value to NO to suppress challenge-related banners.

NETestAppMapping

NETestAppMapping (Dictionary - iOS, macOS) Use this key only during development and testing to help you create a per-app VPN app extension. By using this key, you can test per-app VPN communication without the use of a mobile device management (MDM) server. For more information, refer to NETunnelProviderManager Class Reference.

NFCReaderUsageDescription

NFCReaderUsageDescription (String - iOS). This key lets you describe the reason your app accesses the device’s NFC reader.

This key is supported in iOS 11 and later.

NSAppleMusicUsageDescription

NSAppleMusicUsageDescription (String - iOS). This key lets you describe the reason your app accesses the user’s media library. When the system prompts the user to allow access, the value that you provide for this key is displayed as part of the alert.

This key is supported in iOS 10 and later and in macOS 10.12 and later.

NSAppleScriptEnabled

NSAppleScriptEnabled (Boolean or String - macOS). This key identifies whether the app is scriptable. Set the value of this key to YES (when typed as Boolean) or "YES" (when typed as String) if your app supports AppleScript.

NSAppTransportSecurity

NSAppTransportSecurity (Dictionary - iOS, macOS) Use this key to describe your app’s intended HTTP connection behavior if you require exceptions from best security practices or you want to enable new security features.

On Apple platforms, a networking security feature called App Transport Security (ATS) is available to apps and app extensions, and is enabled by default. It improves privacy and data integrity by ensuring your app’s network connections employ only industry-standard protocols and ciphers without known weaknesses. This helps instill user trust that your app does not accidentally leak transmitted data to malicious parties.

By configuring this key’s value in your app’s Info.plist file, you can customize the security of your network connections in a variety of ways. You can:

• Allow insecure communication with particular servers

• Allow insecure loads for web views or for media, while maintaining ATS protections elsewhere in your app

• Enable new security features such as Certificate Transparency

The NSAppTransportSecurity key is supported in iOS 9.0 and later and in macOS 10.11 and later, and is available in both apps and app extensions.

Starting in iOS 10.0 and later and in macOS 10.12 and later, the following subkeys are supported:

• NSAllowsArbitraryLoadsForMedia

• NSAllowsArbitraryLoadsInWebContent

• NSRequiresCertificateTransparency

• NSAllowsLocalNetworking

In this section:

• ATS Configuration Basics

• Using ATS in Apple Frameworks

• Availability of ATS for Remote and Local Connections

• Requirements for Connecting Using ATS

• Certificate Transparency

• ATS and HTTPS Server Trust Evaluation Requirements

• Supporting Older Operating Systems

• App Store Review for ATS

• ATS Dictionary Details

• ATS Examples

• Debugging ATS Connections

• Using the nscurl Tool to Diagnose ATS Connection Issues

NSAppTransportSecurity : Dictionary {

    NSAllowsArbitraryLoads : Boolean

    NSAllowsArbitraryLoadsForMedia : Boolean

    NSAllowsArbitraryLoadsInWebContent : Boolean

    NSAllowsLocalNetworking : Boolean

    NSExceptionDomains : Dictionary {

        <domain-name-string> : Dictionary {

            NSIncludesSubdomains : Boolean

            NSExceptionAllowsInsecureHTTPLoads : Boolean

            NSExceptionMinimumTLSVersion : String

            NSExceptionRequiresForwardSecrecy : Boolean   // Default value is YES

            NSRequiresCertificateTransparency : Boolean

        }

    }

}

NSAppTransportSecurity

    NSExceptionDomains

        "media-server.example.com"

            NSExceptionAllowsInsecureHTTPLoads = YES

NSAppTransportSecurity

    NSExceptionDomains

        "less-secure.example.com"

            NSExceptionRequiresForwardSecrecy = NO

            NSExceptionMinimumTLSVersion = "TLSv1.0"

NSAppTransportSecurity

    NSExceptionDomains

        "domain-i-control.example.com"

            NSExceptionAllowsInsecureHTTPLoads = NO

            NSExceptionRequiresForwardSecrecy = YES

            NSExceptionMinimumTLSVersion = "TLSv1.2"

        "other-domain-i-control.example.com"

            NSExceptionAllowsInsecureHTTPLoads = NO

            NSExceptionRequiresForwardSecrecy = YES

            NSExceptionMinimumTLSVersion = "TLSv1.2"

    NSAllowsArbitraryLoads = YES

CFNETWORK_DIAGNOSTICS=1

> /usr/bin/nscurl --ats-diagnostics https://apple.com

Starting ATS Diagnostics

Configuring ATS Info.plist keys and displaying the result of HTTPS loads to https://apple.com.

A test will "PASS" if URLSession:task:didCompleteWithError: returns a nil error.

Use '--verbose' to view the ATS dictionaries used and to display the error received in URLSession:task:didCompleteWithError:.

================================================================================

Default ATS Secure Connection

---

ATS Default Connection

2015-09-09 09:53:01.592 nscurl[9207:5187047] CFNetwork SSLHandshake failed (-9824)

2015-09-09 09:53:01.593 nscurl[9207:5187047] NSURLSession/NSURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9824)

Result : FAIL

---

================================================================================

Allowing Arbitrary Loads

---

Allow All Loads

Result : PASS

---

================================================================================

Configuring TLS exceptions for apple.com

---

TLSv1.2

2015-09-09 09:53:02.145 nscurl[9207:5187047] CFNetwork SSLHandshake failed (-9824)

2015-09-09 09:53:02.146 nscurl[9207:5187047] NSURLSession/NSURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9824)

Result : FAIL

---

---

TLSv1.1

2015-09-09 09:53:02.270 nscurl[9207:5187047] CFNetwork SSLHandshake failed (-9824)

2015-09-09 09:53:02.271 nscurl[9207:5187047] NSURLSession/NSURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9824)

Result : FAIL

---

---

TLSv1.0

2015-09-09 09:53:02.407 nscurl[9207:5187047] CFNetwork SSLHandshake failed (-9824)

2015-09-09 09:53:02.408 nscurl[9207:5187047] NSURLSession/NSURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9824)

Result : FAIL

---

================================================================================

Configuring PFS exceptions for apple.com

…

> /usr/bin/nscurl --ats-diagnostics --verbose https://apple.com

Starting ATS Diagnostics

…

Configuring PFS exceptions and allowing insecure HTTP for apple.com

---

Disabling Perfect Forward Secrecy and Allowing Insecure HTTP

ATS Dictionary:

{

    NSExceptionDomains =     {

        "apple.com" =         {

            NSExceptionAllowsInsecureHTTPLoads = YES;

            NSExceptionRequiresForwardSecrecy = NO;

        };

    };

}

Result : FAIL

Error : Error Domain=NSURLErrorDomain Code=-1022 "The resource could not be loaded because the App Transport Security policy requires the use of a secure connection." UserInfo={NSUnderlyingError=0x7fc6a9d11900 {Error Domain=kCFErrorDomainCFNetwork Code=-1022 "(null)"}, NSErrorFailingURLStringKey=http://www.apple.com/apple-events/september-2015/, NSErrorFailingURLKey=http://www.apple.com/apple-events/september-2015/, NSLocalizedDescription=The resource could not be loaded because the App Transport Security policy requires the use of a secure connection.}

---

…

NSBluetoothPeripheralUsageDescription

NSBluetoothPeripheralUsageDescription (String - iOS) This key lets you describe the reason your app uses Bluetooth. When the system prompts the user to allow usage, the value that you provide for this key is displayed as part of the alert.

This key is supported in iOS 6.0 and later.

NSCalendarsUsageDescription

NSCalendarsUsageDescription (String - iOS) This key lets you describe the reason your app accesses the user’s calendars. When the system prompts the user to allow access, this string is displayed as part of the alert.

This key is supported in iOS 6.0 and later.

NSCameraUsageDescription

NSCameraUsageDescription (String - iOS) describes the reason that the app (including an iMessage app) accesses the device’s camera. When the system prompts the user to allow access, this string is displayed as part of the alert.

This key is supported in iOS 7.0 and later.

NSContactsUsageDescription

NSContactsUsageDescription (String - iOS) The key lets you describe the reason your app accesses the user’s contacts. When the system prompts the user to allow access, this string is displayed as part of the alert.

This key is supported in iOS 6.0 and later.

NSDockTilePlugIn

NSDockTilePlugIn (String - macOS). This key contains the name of a plug-in bundle with the .docktileplugin filename extension and residing in the app’s Contents/PlugIns directory. The bundle must contain the Dock tile plug-in for the app. For information about creating a Dock tile plug-in, see Dock Tile Programming Guide.

NSFaceIDUsageDescription

NSFaceIDUsageDescription (String - iOS). This key lets you describe the reason your app uses Face ID.

This key is supported in iOS 11 and later.

NSHealthClinicalHealthRecordsShareUsageDescription

NSHealthClinicalHealthRecordsShareUsageDescription (String - iOS). This key contains a string that is displayed in an authorization prompt when your app requests access to the user’s clinical records. This string should provide justification for accessing these records.

This key is supported in iOS 12.0 and later.

NSHealthRequiredReadAuthorizationTypeIdentifier

NSHealthRequiredReadAuthorizationTypeIdentifier (Array - iOS). This key must contain an array of three or more HealthKit type identifiers. If the user does not authorize permission for all the required types, authorization fails with a HKErrorRequiredAuthorizationDenied error.

This key is supported in iOS 12.0 and later.

NSHealthRequiredWriteAuthorizationTypeIdentifiers

NSHealthRequiredWriteAuthorizationTypeIdentifiers (Array - iOS). This key must contain an array of three or more HealthKit type identifiers. If the user does not authorize permission for all the required types, authorization fails with a HKErrorRequiredAuthorizationDenied error.

This key is supported in iOS 12.0 and later.

NSHealthShareUsageDescription

NSHealthShareUsageDescription (String - iOS). This key lets you describe the reason your app reads the user’s health data. The system prompts the user to allow access when you call the requestAuthorizationToShareTypes:readTypes:completion: method, and this string is displayed as part of the alert. For more information, read HKHealthStore Class Reference and Setting Up HealthKit. This string is localizable.

This key is supported in iOS 8.0 and later.

NSHealthUpdateUsageDescription

NSHealthUpdateUsageDescription (String - iOS). This key lets you describe the reason your app makes changes to the user’s health data. The system prompts the user to allow access when you call the requestAuthorizationToShareTypes:readTypes:completion: method, and this string is displayed as part of the alert. For more information, read HKHealthStore Class Reference and Setting Up HealthKit. This string is localizable.

This key is supported in iOS 8.0 and later.

NSHomeKitUsageDescription

NSHomeKitUsageDescription (String - iOS, watchOS). This key lets you describe the reason your app access the user’s HomeKit configuration data. When the system prompts the user to allow access, this string is displayed as part of the alert.

NSHumanReadableCopyright

NSHumanReadableCopyright (String - macOS). This key contains a string with the copyright notice for the bundle; for example, © 2016, My Company. You can load this string and display it in an About dialog box. The system uses this string in the app’s Info window in Finder.

This key can be localized by including it in your InfoPlist.strings files.

This key replaces the obsolete CFBundleGetInfoString key.

See also CFBundleShortVersionString.

NSJavaNeeded

NSJavaNeeded (Boolean or String - macOS). This key specifies whether the Java VM must be loaded and started up prior to executing the bundle code. This key is required only for Cocoa Java apps to tell the system to launch the Java environment. If you are writing a pure Java app, do not include this key.

You can also specify a string type with the value “YES” instead of a Boolean value if desired.

Deprecated in OS X v10.5.

NSJavaPath

NSJavaPath (Array - macOS). This key contains an array of paths. Each path points to a Java class. The path can be either an absolute path or a relative path from the location specified by the key NSJavaRoot. The development environment (or, specifically, its jamfiles) automatically maintains the values in the array.

Deprecated in OS X v10.5.

NSJavaRoot

NSJavaRoot (String - macOS). This key contains a string identifying a directory. This directory represents the root directory of the app’s Java class files.

NSLocationAlwaysUsageDescription

NSLocationAlwaysUsageDescription (String - iOS) This key lets you describe the reason your app accesses the user’s location information at all times. Include this key when your app uses location services in a potentially nonobvious way while running in the foreground or the background. For example, a social app might include this key when it uses location information to track the user’s location and display other users that are nearby. In this case, the fact that the app is tracking the user’s location might not be readily apparent. The system includes the value of this key in the alert panel displayed to the user when requesting permission to use location services.

This key is required when you use the requestAlwaysAuthorization method of the CLLocationManager class to request authorization for location services. If this key is not present and you call the requestAlwaysAuthorization method, the system ignores your request and prevents your app from using location services.

This key is supported in iOS 8.0 and later.

NSLocationUsageDescription

NSLocationUsageDescription (String - iOS) Unused in iOS 8 and later. If you link your app on or after iOS 8, use the NSLocationAlwaysUsageDescription or NSLocationWhenInUseUsageDescription key instead.

This key lets you describe the reason your app accesses the user’s location information. When the system prompts the user to allow access, this string is displayed as part of the alert panel.

This key is supported in iOS 6.0 through iOS 7. This key is ignored in iOS 8 and later.

NSLocationWhenInUseUsageDescription

NSLocationWhenInUseUsageDescription (String - iOS) This key lets you describe the reason your app accesses the user’s location information while your app runs in the foreground and otherwise when in use. Include this key when your app uses location services to track the user’s current location directly. This key does not support using location services to monitor regions or monitor the user’s location using the significant location change service. The system includes the value of this key in the alert panel displayed to the user when requesting permission to use location services.

This key is required when you use the requestWhenInUseAuthorization method of the CLLocationManager class to request authorization for location services. If the key is not present when you call the requestWhenInUseAuthorization method without including this key, the system ignores your request.

This key is supported in iOS 8.0 and later.

NSMainNibFile

NSMainNibFile (String - iOS, macOS). This key contains a string with the name of the app’s main nib file (minus the .nib extension). A nib file is an Interface Builder archive containing the description of a user interface along with any connections between the objects of that interface. The main nib file is automatically loaded when an app is launched.

This key is mutually exclusive with the UIMainStoryboardFile key. You should include one of the keys in your Info.plist file but not both.

NSMicrophoneUsageDescription

NSMicrophoneUsageDescription (String - iOS) This key lets you describe the reason your app (including an iMessage app) accesses any of the device’s microphones. When the system prompts the user to allow access, this string is displayed as part of the alert.

This key is supported in iOS 7.0 and later.

NSMotionUsageDescription

NSMotionUsageDescription (String - iOS) This key lets you describe the reason your app accesses the device’s accelerometer. When the system prompts the user to allow access, this string is displayed as part of the alert.

This key is supported in iOS 7.0 and later.

NSPersistentStoreTypeKey

NSPersistentStoreTypeKey (String - macOS). This key contains a string that specifies the type of Core Data persistent store associated with a document type (see CFBundleDocumentTypes).

NSPhotoLibraryAddUsageDescription

NSPhotoLibraryAddUsageDescription (String - iOS) This key lets you describe the reason your app seeks write-only access to the user’s photo library. When the system prompts the user to allow access, this string is displayed as part of the alert.

This key is supported in iOS 11.0 and later.

NSPhotoLibraryUsageDescription

NSPhotoLibraryUsageDescription (String - iOS) This key lets you describe the reason your app accesses the user’s photo library. When the system prompts the user to allow access, this string is displayed as part of the alert.

Although this keys governs read and write access to the user’s photo library, it’s best to use NSPhotoLibraryAddUsageDescription if your app needs only to add assets to the library and does not need to read any assets.

This key is supported in iOS 6.0 and later.

NSPrefPaneIconFile

NSPrefPaneIconFile (String - macOS). This key contains a string with the name of an image file (including extension) containing the preference pane’s icon. This key should only be used by preference pane bundles. The image file should contain an icon 32 by 32 pixels in size. If this key is omitted, the System Preferences app looks for the image file using the CFBundleIconFile key instead.

NSPrefPaneIconLabel

NSPrefPaneIconLabel (String - macOS). This key contains a string with the name of a preference pane. This string is displayed below the preference pane’s icon in the System Preferences app. You can split long names onto two lines by including a newline character (‘\n’) in the string. If this key is omitted, the System Preferences app gets the name from the CFBundleName key.

This key can be localized and included in the InfoPlist.strings files of a bundle.

NSPrincipalClass

NSPrincipalClass (String - macOS). This key contains a string with the name of a bundle’s principal class. This key is used to identify the entry point for dynamically loaded code, such as plug-ins and other dynamically-loaded bundles. The principal class of a bundle typically controls all other classes in the bundle and mediates between those classes and any classes outside the bundle. The class identified by this value can be retrieved using the principalClass method of NSBundle. For Cocoa apps, the value for this key is NSApplication by default.

NSRemindersUsageDescription

NSRemindersUsageDescription (String - iOS) This key lets you describe the reason your app accesses the user’s reminders. When the system prompts the user to allow access, this string is displayed as part of the alert.

This key is supported in iOS 6.0 and later.

NSServices

NSServices (Array - macOS). This key contains an array of dictionaries specifying the services provided by the app. Table 4 lists the keys for specifying a service:

In OS X v10.6 and later, the NSRequiredContext key may contain a dictionary or an array of dictionaries describing the conditions under which the service appears in the Services menu. If you specify a single dictionary, all of the conditions in that dictionary must be met for the service to appear. If you specify an array of dictionaries, all of the conditions in only one of those dictionaries must be met for the service to appear. Each dictionary may contain one or more of the keys listed in Table 5. All keys in the dictionary are optional.

For additional information about implementing services in your app, see Services Implementation Guide.

NSSiriUsageDescription

NSSiriUsageDescription (String - iOS) This key lets you describe the reason your app sends user data to Siri. The first time that your app explicitly requests access to Siri, the system displays this string as part of the alert. If the user’s first interaction with your app occurs in Siri itself, a default string may be used instead.

NSSpeechRecognitionUsageDescription

NSSpeechRecognitionUsageDescription (String - iOS) This key lets you describe the reason your app sends user data to Apple’s speech recognition servers. When the system prompts the user to allow access, this string is displayed as part of the alert.

NSSupportsAutomaticTermination

NSSupportsAutomaticTermination (Boolean - macOS). This key contains a Boolean value that indicates whether the app supports automatic termination in OS X v10.7 and later. Automatic termination allows an app that is running to be terminated automatically by the system when certain conditions apply. Primarily, the app can be terminated when it is hidden or does not have any visible windows and is not currently being used. The system may terminate such an app in order to reclaim the memory used by the app.

An app may programmatically disable and reenable automatic termination support using the disableAutomaticTermination and enableAutomaticTermination methods of NSProcessInfo. The app might do this to prevent being terminated during a critical operation.

NSSupportsPurgeableLocalStorage

NSSupportsPurgeableLocalStorage (Boolean - iOS). This key contains a Boolean value that indicates whether the app is designed to work, without disruption to the user, with the local data container treated as a volatile cache by the system. The default value of this key is NO. If your app supports Shared iPad (a feature of iOS device management), set this key’s value to YES.

When set to YES, the system is enabled to purge local storage, at the system’s discretion, when the user is logged out.

Supporting Shared iPad entails different work depending on where your app chooses to store nonlocal user data, as follows:

• User data stored in iCloud is automatically restored by the system, as needed.

• Nonlocal user data that is not stored in iCloud must be restored explicitly, by your app, from the app’s non-iCloud service.

If your app uses only local storage and does not depend on its persistence (for example, a simple calculator app), you can declare support for Shared iPad by setting this key’s value to YES.

NSSupportsSuddenTermination

NSSupportsSuddenTermination (Boolean - macOS). This key contains a Boolean value that indicates whether the system may kill the app outright in order to log out or shut down more quickly. Use this key to specify whether the app can be killed immediately after launch. The app can still enable or disable sudden termination at runtime using the methods of the NSProcessInfo class. The default value of this key is NO.

NSUbiquitousContainers

NSUbiquitousContainers (Dictionary - iOS and macOS) Specifies the iCloud Drive settings for each container. This dictionary’s keys are the container identifiers for your app’s iCloud containers. The values are dictionaries containing the NSUbiquitousContainerIsDocumentScopePublic, NSUbiquitousContainerName and NSUbiquitousContainerSupportedFolderLevels entries for each container. You must specify the sharing permissions separately for each container.

NSUbiquitousContainerIsDocumentScopePublic

NSUbiquitousContainerIsDocumentScopePublic (Boolean - iOS and macOS) Specifies whether the iCloud drive should share the contents of this container. Defaults to NO.

NSUbiquitousContainerName

NSUbiquitousContainerName (String - iOS and macOS) Specifies the name that the iCloud Drive displays for your container. By default, the iCloud Drive will use the name of the bundle that owns the container.

NSUbiquitousContainerSupportedFolderLevels

NSUbiquitousContainerSupportedFolderLevels (String - iOS and macOS) Specifies the maximum number of folder levels inside your container’s Documents directory. This key can take three different values:

• None

  The iCloud Drive only has access to the container’s Documents directory. Your app promises that it does not create any directories inside the Document’s directory. In macOS, the Finder prevents users from creating subdirectories inside your iCloud Drive directory.

• One

  The iCloud Drive has access to the container’s Documents directory and one additional layer of subdirectories. Your app promises that it only creates a single layer of directories inside the Documents directory. In macOS, the Finder prevents users from creating more than one layer of subdirectories inside your iCloud Drive directory.

• Any

  The iCloud Drive has complete access to your container’s Documents directory. Both your app and the Finder can create as many layers of subdirectories as you (or the user) desire.

NSUbiquitousDisplaySet

NSUbiquitousDisplaySet (String - iOS, macOS) contains the identifier string that you configured in iTunesConnect for managing your app’s storage. The assigned display set determines from which mobile data folder (in the user’s mobile account) the app retrieves its data files.

If you create multiple apps, you can use the same display set for your apps or assign different display sets to each. For example, if you create a “lite” version of your app, in addition to a full-featured version, you might use the same display set for both versions because they create and use the same basic data files. Each app should recognize the file types stored in its mobile data folder and be able to open them.

NSUserActivityTypes

NSUserActivityTypes (Array of strings - iOS and macOS) Specifies the user activity types that the app supports. This key is valid in iOS 8 and macOS 10.10 and later.

NSUserNotificationAlertStyle

NSUserNotificationAlertStyle (String - macOS) specifies the notification style the app should use. The default value, banner, is recommended; most apps should not need to use the alert style.

NSVideoSubscriberAccountUsageDescription

NSVideoSubscriberAccountUsageDescription (String - tvOS). This key lets you describe the reason your app access the user’s TV provider account. When the system prompts the user to allow access, this string is displayed as part of the alert.

UTExportedTypeDeclarations

UTExportedTypeDeclarations (Array - iOS, macOS) declares the uniform type identifiers (UTIs) owned and exported by the app. You use this key to declare your app’s custom data formats and associate them with UTIs. Exporting a list of UTIs is the preferred way to register your custom file types; however, Launch Services recognizes this key and its contents only in OS X v10.5 and later. This key is ignored on versions of OS X prior to version 10.5.

The value for the UTExportedTypeDeclarations key is an array of dictionaries. Each dictionary contains a set of key-value pairs identifying the attributes of the type declaration. Table 6 lists the keys you can include in this dictionary along with the typical values they contain. These keys can also be included in array of dictionaries associated with the UTImportedTypeDeclarations key.

The way you specify icon files in macOS and iOS is different because of the supported file formats on each platform. In iOS, each icon resource file is typically a PNG file that contains only one image. Therefore, it is necessary to specify different image files for different icon sizes. However, when specifying icons in macOS, you use an icon file (with extension .icns), which is capable of storing the icon at several different resolutions.

This key is supported in iOS 3.2 and later and in OS X v10.5 and later. For more information about UTIs and their use, see Uniform Type Identifiers Overview.

UTImportedTypeDeclarations

UTImportedTypeDeclarations (Array - iOS, macOS) declares the uniform type identifiers (UTIs) inherently supported (but not owned) by the app. You use this key to declare any supported types that your app recognizes and wants to ensure are recognized by Launch Services, regardless of whether the app that owns them is present. For example, you could use this key to specify a file format that is defined by another company but which your program can read and export.

The value for this key is an array of dictionaries and uses the same keys as those for the UTExportedTypeDeclarations key. For a list of these keys, see Table 6.

This key is supported in iOS 3.2 and later and in OS X v10.5 and later. For more information about UTIs and their use, see Uniform Type Identifiers Overview.