Launch Services Keys
Launch Services (part of the Core Services framework in OS X) provides support for launching apps and matching document types to apps. As a result, the keys recognized by Launch Services allow you to specify the desired execution environment for your bundled code. (In iOS, Launch Services is a private API but is still used internally to coordinate the execution environment of iOS apps.)
Launch Services keys use the prefix
LS to distinguish them from other keys. For more information about Launch Services in OS X, see Launch Services Programming Guide and Launch Services Reference.
Table 1 contains an alphabetical listing of Launch Services 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.
Contains a string with the UTI that categorizes the app for the App Store. See LSApplicationCategoryType for details.
Contains an array of strings identifying the supported code architectures and their preferred execution priority. See LSArchitecturePriority for details.
“Application is background only”
Specifies whether the app runs only in the background. (Mach-O apps only). See LSBackgroundOnly for details.
Contains a list of key/value pairs, representing environment variables and their values. See LSEnvironment for details.
“File quarantine enabled”
Specifies whether the files this app creates are quarantined by default. See LSFileQuarantineEnabled.
Specifies directories for which files should not be automatically quarantined. See LSFileQuarantineExcludedPathPatterns.
“Application should get App Died events”
Specifies whether the app is notified when a child process dies. See LSGetAppDiedEvents for details.
“Minimum system version”
Specifies the minimum version of OS X required for the app to run. See LSMinimumSystemVersion for details.
“Minimum system versions, per-architecture”
Specifies the minimum version of OS X required to run a given platform architecture. See LSMinimumSystemVersionByArchitecture for details.
“Application prohibits multiple instances”
Specifies whether one user or multiple users can launch an app simultaneously. See LSMultipleInstancesProhibited for details.
“Application requires iPhone environment”
Specifies whether the app is an iOS app. See LSRequiresIPhoneOS for details.
“Application requires native environment”
Specifies whether the app must run natively on an Intel-based Mac, as opposed to under Rosetta emulation. See LSRequiresNativeExecution for details.
“Application is agent (UIElement)”
Specifies whether the app is an agent app, that is, an app that should not appear in the Dock or Force Quit window. See LSUIElement for details.
“Application UI Presentation Mode”
Sets the visibility of system UI elements when the app launches. See LSUIPresentationMode for details.
“Application is visible in Classic”
Specifies whether an agent app or background-only app is visible to other apps in the Classic environment. See LSVisibleInClassic for details.
“Minimum system version”
Do not use. Use LSMinimumSystemVersion instead.
String - OS X) is a string that contains the UTI corresponding to the app’s type. The App Store uses this string to determine the appropriate categorization for the app. Table 2 lists the supported UTIs for apps.
Graphics & Design
Healthcare & Fitness
Table 3 lists the UTIs that are specific to games.
Role Playing Games
Array - OS X) is an array of strings that identifies the architectures this app supports. The order of the strings in this array dictates the preferred execution priority for the architectures. The possible strings for this array are listed in Table 4.
The 32-bit Intel architecture.
The 32-bit PowerPC architecture.
The 64-bit Intel architecture.
The 64-bit PowerPC architecture.
If a PowerPC architecture appears before either of the Intel architectures, OS X runs the executable under Rosetta emulation on an Intel-based Mac. To force OS X to use the current platform’s native architecture, include the LSRequiresNativeExecution key in your information property list.
Boolean - OS X) specifies whether this app runs only in the background. If this key exists and is set to “1”, Launch Services runs the app in the background only. You can use this key to create faceless background apps. You should also use this key if your app uses higher-level frameworks that connect to the window server, but are not intended to be visible to users. Background apps must be compiled as Mach-O executables. This option is not available for CFM apps.
Dictionary - OS X) defines environment variables to be set before launching this app. The names of the environment variables are the keys of the dictionary, with the values being the corresponding environment variable value. Both keys and values must be strings.
These environment variables are set only for apps launched through Launch Services. If you run your executable directly from the command line, these environment variables are not set.
Boolean - OS X) specifies whether files this app creates are quarantined by default.
Files created by this app are quarantined by default. When quarantining files, the system automatically associates the timestamp, app name, and the bundle identifier with the quarantined file whenever possible. Your app can also get or set quarantine attributes as needed using Launch Services.
(Default) Files created by this app are not quarantined by default.
This key is available in OS X v10.5 and later.
Array - OS X) contains an array of strings indicating the paths for which you want to disable file quarantining. You can use this key to prevent file quarantines from affecting the performance of your app. Each string in the array is a shell-style path pattern, which means that special characters such as
? are automatically expanded according to the standard command-line rules. For example, a string of the form
~/Library/Caches/* would allow you to disable the quarantine for files created by your app in the user’s cache directory.
Boolean - OS X) indicates whether the operation system notifies this app when when one of its child process terminates. If you set the value of this key to
YES, the system sends your app an
kAEApplicationDied Apple event for each child process as it terminates.
String - OS X) indicates the minimum version of OS X required for this app to run. This string must be of the form n.n.n where n is a number. The first number is the major version number of the system. The second and third numbers are minor revision numbers. For example, to support OS X v10.4 and later, you would set the value of this key to “10.4.0”.
If the minimum system version is not available, OS X tries to display an alert panel notifying the user of that fact.
Dictionary - OS X) specifies the earliest OS X version for a set of architectures. This key contains a dictionary of key-value pairs. Each key corresponds to one of the architectures associated with the LSArchitecturePriority key. The value for each key is the minimum version of OS X required for the app to run under that architecture. This string must be of the form n.n.n where n is a number. The first number is the major version number of the system. The second and third numbers are minor revision numbers. For example, to support OS X v10.4.9 and later, you would set the value of this key to “10.4.9”.
If the current system version is less than the required minimum version, Launch Services does not attempt to use the corresponding architecture. This key applies only to the selection of an execution architecture and can be used in conjunction with the LSMinimumSystemVersion key, which specifies the overall minimum system version requirement for the app.
Boolean - OS X) indicates whether an app is prohibited from running simultaneously in multiple user sessions. If true, the app runs in only one user session at a time. You can use this key to prevent resource conflicts that might arise by sharing an app across multiple user sessions. For example, you might want to prevent users from accessing a custom USB device when it is already in use by a different user.
Launch Services returns an appropriate error code if the target app cannot be launched. If a user in another session is running the app, Launch Services returns a
kLSMultipleSessionsNotSupportedErr error. If you attempt to launch a separate instance of an app in the current session, it returns
Boolean - iOS) specifies whether the app can run only on iOS. If this key is set to
YES, Launch Services allows the app to launch only when the host platform is iOS.
Boolean - OS X) specifies whether to launch the app using the subbinary for the current architecture. If this key is set to
YES, Launch Services always runs the app using the binary compiled for the current architecture. You can use this key to prevent a universal binary from being run under Rosetta emulation on an Intel-based Mac. For more information about configuring the execution architectures, see LSArchitecturePriority.
String - OS X) specifies whether the app runs as an agent app. If this key is set to “1”, Launch Services runs the app as an agent app. Agent apps do not appear in the Dock or in the Force Quit window. Although they typically run as background apps, they can come to the foreground to present a user interface if desired. A click on a window belonging to an agent app brings that app forward to handle events.
The Dock and loginwindow are two apps that run as agent apps.
Number - OS X) identifies the initial user-interface mode for the app. You would use this in apps that may need to take over portions of the screen that contain UI elements such as the Dock and menu bar. Most modes affect only UI elements that appear in the content area of the screen, that is, the area of the screen that does not include the menu bar. However, you can request that all UI elements be hidden as well.
This key is applicable to both Carbon and Cocoa apps and can be one of the following values:
Normal mode. In this mode, all standard system UI elements are visible. This is the default value.
Content suppressed mode. In this mode, system UI elements in the content area of the screen are hidden. UI elements may show themselves automatically in response to mouse movements or other user activity. For example, the Dock may show itself when the mouse moves into the Dock’s auto-show region.
Content hidden mode. In this mode, system UI elements in the content area of the screen are hidden and do not automatically show themselves in response to mouse movements or user activity.
All hidden mode. In this mode, all UI elements are hidden, including the menu bar. Elements do not automatically show themselves in response to mouse movements or user activity.
All suppressed mode. In this mode, all UI elements are hidden, including the menu bar. UI elements may show themselves automatically in response to mouse movements or other user activity. This option is available only in OS X v10.3 and later.
String - OS X). If this key is set to “1”, any agent apps or background-only apps with this key appears as background-only processes to the Classic environment. Agent apps and background-only apps without this key do not appear as running processes to Classic at all. Unless your process needs to communicate explicitly with a Classic app, you do not need to include this key.
String - iOS). When you build an iOS app, Xcode uses the iOS Deployment Target setting of the project to set the value for the
MinimumOSVersion key. Do not specify this key yourself in the
Info.plist file; it is a system-written key. When you publish your app to the App Store, the store indicates the iOS releases on which your app can run based on this key. It is equivalent to the
LSMinimumSystemVersion key in OS X.