Core Foundation Keys

The Core Foundation framework provides the underlying infrastructure for bundles, including the code used at runtime to load bundles and parse their structure. As a result, many of the keys recognized by this framework are fundamental to the definition of bundles themselves and are instrumental in determining the contents of a bundle.

Core Foundation keys use the prefix CF to distinguish them from other keys. For more information about Core Foundation, see Core Foundation Framework Reference.

Key Summary

Table 1 contains an alphabetical listing of Core Foundation 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.

Table 1  Summary of Core Foundation keys

Key

Xcode name

Summary

Platforms

CFAppleHelpAnchor

“Help file”

The bundle’s initial HTML help file. See “CFAppleHelpAnchor” for details.

OS X

CFBundleAllowMixedLocalizations

“Localized resources can be mixed”

Used by Foundation tools to retrieve localized resources from frameworks. See “CFBundleAllowMixedLocalizations” for details.

iOS, OS X

CFBundleDevelopmentRegion

“Localization native development region”

(Recommended) The native region for the bundle. Usually corresponds to the native language of the author. See “CFBundleDevelopmentRegion” for details.

iOS, OS X

CFBundleDisplayName

“Bundle display name”

(Recommended, Localizable) The actual name of the bundle. See “CFBundleDisplayName” for details.

iOS, OS X

CFBundleDocumentTypes

“Document types”

An array of dictionaries describing the document types supported by the bundle. See “CFBundleDocumentTypes” for details.

iOS, OS X

CFBundleExecutable

“Executable file”

(Recommended) Name of the bundle’s executable file. See “CFBundleExecutable” for details.

iOS, OS X

CFBundleHelpBookFolder

“Help Book directory name”

The name of the folder containing the bundle’s help files. See “CFBundleHelpBookFolder” for details.

OS X

CFBundleHelpBookName

“Help Book identifier”

The name of the help file to display when Help Viewer is launched for the bundle. See “CFBundleHelpBookName” for details.

OS X

CFBundleIconFile

“Icon file”

A legacy way to specify the app’s icon. Use the “CFBundleIcons” or “CFBundleIconFiles” keys instead. See “CFBundleIconFile” for details.

iOS, OS X

CFBundleIconFiles

“Icon files”

A top-level key for specifying the file names of the bundle’s icon image files. See “CFBundleIconFiles” for details.

See also “CFBundleIcons” as an alternative to this key.

iOS 3.2 and later

CFBundleIcons

None

File names of the bundle’s icon image files. See “CFBundleIconFiles” for details.

iOS 5.0 and later

CFBundleIdentifier

“Bundle identifier”

(Recommended) An identifier string that specifies the app type of the bundle. The string should be in reverse DNS format using only the Roman alphabet in upper and lower case (A–Z, a–z), the dot (“.”), and the hyphen (“-”). See “CFBundleIdentifier” for details.

iOS, OS X

CFBundleInfoDictionaryVersion

“InfoDictionary version”

(Recommended) Version information for the Info.plist format. See “CFBundleInfoDictionaryVersion” for details.

iOS, OS X

CFBundleLocalizations

“Localizations”

Contains localization information for an app that handles its own localized resources. See “CFBundleLocalizations” for details.

iOS, OS X

CFBundleName

“Bundle name”

(Recommended, Localizable) The short display name of the bundle. See “CFBundleName” for details.

iOS, OS X

CFBundlePackageType

“Bundle OS Type code”

The four-letter code identifying the bundle type. See “CFBundlePackageType” for details.

iOS, OS X

CFBundleShortVersionString

“Bundle versions string, short”

(Localizable) The release-version-number string for the bundle. See “CFBundleShortVersionString” for details.

iOS, OS X

CFBundleSignature

“Bundle creator OS Type code”

The four-letter code identifying the bundle creator. See “CFBundleSignature” for details.

iOS, OS X

CFBundleURLTypes

“URL types”

An array of dictionaries describing the URL schemes supported by the bundle. See “CFBundleURLTypes” for details.

iOS, OS X

CFBundleVersion

“Bundle version”

(Recommended) The build-version-number string for the bundle. See “CFBundleVersion” for details.

iOS, OS X

CFPlugInDynamicRegistration

“Plug-in should be registered dynamically”

If YES, register the plug-in dynamically; otherwise, register it statically. See “CFPlugInDynamicRegistration” for details.

OS X

CFPlugInDynamicRegistrationFunction

Plug-in dynamic registration function name”

The name of the custom, dynamic registration function. See “CFPlugInDynamicRegisterFunction” for details.

OS X

CFPlugInFactories

“Plug-in factory interfaces”

For static registration, this dictionary contains a list of UUIDs with matching function names. See “CFPlugInFactories” for details.

OS X

CFPlugInTypes

“Plug-in types”

For static registration, the list of UUIDs “CFPlugInTypes” for details.

OS X

CFPlugInUnloadFunction

“Plug-in unload function name”

The name of the custom function to call when it’s time to unload the plug-in code from memory. See “CFPlugInUnloadFunction” for details.

OS X

CFAppleHelpAnchor

CFAppleHelpAnchor (String - OS X) identifies the name of the bundle’s initial HTML help file, minus the .html or .htm extension. This file must be located in the bundle’s localized resource directories or, if the help is not localized, directly under the Resources directory.

CFBundleAllowMixedLocalizations

CFBundleAllowMixedLocalizations (Boolean - iOS, OS X) specifies whether the bundle supports the retrieval of localized strings from frameworks. This key is used primarily by Foundation tools that link to other system frameworks and want to retrieve localized resources from those frameworks.

CFBundleDevelopmentRegion

CFBundleDevelopmentRegion (String - iOS, OS X) specifies the native region for the bundle. This key contains a string value that usually corresponds to the native language of the person who wrote the bundle. The language specified by this value is used as the default language if a resource cannot be located for the user’s preferred region or language.

CFBundleDisplayName

CFBundleDisplayName (String - iOS, OS X) specifies the display name of the bundle. If you support localized names for your bundle, include this key in both your information property list file and in the InfoPlist.strings files of your language subdirectories. If you localize this key, you should also include a localized version of the CFBundleName key.

If you do not intend to localize your bundle, do not include this key in your Info.plist file. Inclusion of this key does not affect the display of the bundle name but does incur a performance penalty to search for localized versions of this key.

Before displaying a localized name for your bundle, the Finder compares the value of this key against the actual name of your bundle in the file system. If the two names match, the Finder proceeds to display the localized name from the appropriate InfoPlist.strings file of your bundle. If the names do not match, the Finder displays the file-system name.

For more information about display names in OS X, see File System Programming Guide.

CFBundleDocumentTypes

CFBundleDocumentTypes (Array - iOS, OS X) contains an array of dictionaries that associate one or more document types with your app. Each dictionary is called a type-definition dictionary and contains keys used to define the document type. Table 2 lists the keys that are supported in these dictionaries.

Table 2  Keys for type-definition dictionaries

Key

Xcode name

Type

Description

Platforms

CFBundleTypeExtensions

“Document Extensions”

Array

This key contains an array of strings. Each string contains a filename extension (minus the leading period) to map to this document type. To open documents with any extension, specify an extension with a single asterisk “*”. (In OS X v10.4, this key is ignored if the LSItemContentTypes key is present.) Deprecated in OS X v10.5.

OS X

CFBundleTypeIconFile

“Icon File Name”

String

This key contains a string with the name of the icon file (.icns) to associate with this OS X document type. For more information about specifying document icons, see “Document Icons.”

OS X

CFBundleTypeIconFiles

None

Array

An array of strings containing the names of the image files to use for the document icon in iOS. For more information about specifying document icons, see “Document Icons.”

iOS

CFBundleTypeMIMETypes

“Document MIME types”

Array

Contains an array of strings. Each string contains the MIME type name you want to map to this document type. (In OS X v10.4, this key is ignored if the LSItemContentTypes key is present.) Deprecated in OS X v10.5.

OS X

CFBundleTypeName

“Document Type Name”

String

This key contains the abstract name for the document type and is used to refer to the type. This key is required and can be localized by including it in an InfoPlist.strings files. This value is the main way to refer to a document type. If you are concerned about this key being unique, you should consider using a uniform type identifier (UTI) for this string instead. If the type is a common Clipboard type supported by the system, you can use one of the standard types listed in the NSPasteboard class description.

iOS, OS X

CFBundleTypeOSTypes

“Document OS Types”

Array

This key contains an array of strings. Each string contains a four-letter type code that maps to this document type. To open documents of any type, include four asterisk characters (****) as the type code. These codes are equivalent to the legacy type codes used by Mac OS 9. (In OS X v10.4, this key is ignored if the LSItemContentTypes key is present.) Deprecated in OS X v10.5.

OS X

CFBundleTypeRole

“Role”

String

This key specifies the app’s role with respect to the type. The value can be Editor, Viewer, Shell, or None. This key is required.

OS X

LSItemContentTypes

“Document Content Type UTIs”

Array

This key contains an array of strings. Each string contains a UTI defining a supported file type. The UTI string must be spelled out explicitly, as opposed to using one of the constants defined by Launch Services. For example, to support PNG files, you would include the string “public.png“ in the array. When using this key, also add the NSExportableTypes key with the appropriate entries. In OS X v10.5 and later, this key (when present) takes precedence over these type-identifier keys: CFBundleTypeExtensions, CFBundleTypeMIMETypes, CFBundleTypeOSTypes.

iOS, OS X

LSHandlerRank

“Handler rank”

String

Determines how Launch Services ranks this app among the apps that declare themselves editors or viewers of files of this type. The possible values are: Owner (this app is the creator of files of this type), Alternate (this app is a secondary viewer of files of this type), None (this app must never be used to open files of this type, but it accepts drops of files of this type), Default (default; this app doesn’t accept drops of files of this type). Launch Services uses the value of LSHandlerRank to determine the app to use to open files of this type. The order of precedence is: Owner, Alternate, None. This key is available in OS X v10.5 and later.

iOS, OS X

LSTypeIsPackage

“Document is a package or bundle”

Boolean

Specifies whether the document is distributed as a bundle. If set to true, the bundle directory is treated as a file. (In OS X v10.4 and later, this key is ignored if the LSItemContentTypes key is present.)

OS X

NSDocumentClass

“Cocoa NSDocument Class”

String

This key specifies the name of the NSDocument subclass used to instantiate instances of this document. This key is used by Cocoa apps only.

OS X

NSExportableAs

“Exportable As Document Type Names”

Array

This key specifies an array of strings. Each string contains the name of another document type, that is, the value of a CFBundleTypeName property. This value represents another data format to which this document can export its content. This key is used by Cocoa apps only. Deprecated in OS X v10.5.

OS X

NSExportableTypes

None

Array

This key specifies an array strings. Each string should contain a UTI defining a supported file type to which this document can export its content. Each UTI string must be spelled out explicitly, as opposed to using one of the constants defined by Launch Services. For example, to support PNG files, you would include the string “public.png“ in the array. This key is used by Cocoa apps only. Available in OS X v10.5 and later.

OS X

The way you specify icon files in OS X 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 OS X, 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 all versions of OS X. For detailed information about UTIs, see Uniform Type Identifiers Overview.

Document Roles

An app can take one of the following roles for any given document type:

  • Editor. The app can read, manipulate, and save the type.

  • Viewer. The app can read and present data of that type.

  • Shell. The app provides runtime services for other processes—for example, a Java applet viewer. The name of the document is the name of the hosted process (instead of the name of the app), and a new process is created for each document opened.

  • None. The app does not understand the data, but is just declaring information about the type (for example, the Finder declaring an icon for fonts).

The role you choose applies to all of the concrete formats associated with the document or Clipboard type. For example, the Safari app associates itself as a viewer for documents with the “.html”, “.htm”, “shtml, or “jhtml” filename extensions. Each of these extensions represents a concrete type of document that falls into the overall category of HTML documents. This same document can also support MIME types and legacy 4-byte OS types.

Document Icons

In iOS, the CFBundleTypeIconFiles key contains an array of strings with the names of the image files to use for the document icon. Table 3 lists the icon sizes you can include for each device type. You can name the image files however you want but the file names in your Info.plist file must match the image resource filenames exactly. (For iPhone and iPod touch, the usable area of your icon is actually much smaller.) For more information on how to create these icons, see iOS Human Interface Guidelines.

Table 3  Document icon sizes for iOS

Device

Sizes

iPad

64 x 64 pixels

320 x 320 pixels

iPhone and iPod touch

22 x 29 pixels

44 x 58 pixels (high resolution)

In OS X, the CFBundleTypeIconFile key contains the name of an icon resource file with the document icon. An icon resource file contains multiple images, each representing the same document icon at different resolutions. If you omit the filename extension, the system looks for your file with the extension .icns. You can create icon resource files using the Icon Composer app that comes with Xcode Tools.

Recommended Keys

The entry for each document type should contain the following keys:

  • CFBundleTypeIconFile

  • CFBundleTypeName

  • CFBundleTypeRole

In addition to these keys, it must contain at least one of the following keys:

  • LSItemContentTypes

  • CFBundleTypeExtensions

  • CFBundleTypeMIMETypes

  • CFBundleTypeOSTypes

If you do not specify at least one of these keys, no document types are bound to the type-name specifier. You may use all three keys when binding your document type, if you so choose. In OS X v10.4 and later, if you specify the LSItemContentTypes key, the other keys are ignored. You can continue to include the other keys for compatibility with older versions of the system, however.

CFBundleExecutable

CFBundleExecutable (String - iOS, OS X) identifies the name of the bundle’s main executable file. For an app, this is the app executable. For a loadable bundle, it is the binary that will be loaded dynamically by the bundle. For a framework, it is the shared library for the framework. Xcode automatically adds this key to the information property list file of appropriate projects.

For frameworks, the value of this key is required to be the same as the framework name, minus the .framework extension. If the keys are not the same, the target system may incur some launch-performance penalties. The value should not include any extension on the name.

CFBundleHelpBookFolder

CFBundleHelpBookFolder (String - OS X) identifies the folder containing the bundle’s help files. Help is usually localized to a specific language, so the folder specified by this key represents the folder name inside the .lproj directory for the selected language.

CFBundleHelpBookName

CFBundleHelpBookName (String - OS X) identifies the main help page for your app. This key identifies the name of the Help page, which may not correspond to the name of the HTML file. The Help page name is specified in the CONTENT attribute of the help file’s META tag.

CFBundleIconFile

CFBundleIconFile (String - iOS, OS X) identifies the file containing the icon for the bundle. The filename you specify does not need to include the extension, although it may. The system looks for the icon file in the main resources directory of the bundle.

If your Mac app uses a custom icon, you must specify this property. If you do not specify this property, the system (and other apps) display your bundle with a default icon.

CFBundleIconFiles

CFBundleIconFiles (Array - iOS) contains an array of strings identifying the icon files for the bundle. (It is recommended that you always create icon files using the PNG format.) When specifying your icon filenames, it is best to omit any filename extensions. Omitting the filename extension lets the system automatically detect high-resolution (@2x) versions of your image files using the standard-resolution image filename. If you include filename extensions, you must specify all image files (including the high-resolution variants) explicitly. The system looks for the icon files in the main resources directory of the bundle. If present, the values in this key take precedence over the value in the “CFBundleIconFile” key.

This key is supported in iOS 3.2 and later only and an app may have differently sized icons to support different types of devices and different screen resolutions. In other words, an app icon is typically 57 x 57 pixels on iPhone or iPod touch but is 72 x 72 pixels on iPad. Icons at other sizes may also be included. The order of the items in this array does not matter. The system automatically chooses the most appropriately sized icon based on the usage and the underlying device type.

For a list of the icons, including their sizes, that you can include in your app bundle, see the section on app icons in “Advanced App Tricks” in iOS App Programming Guide. For information about how to create icons for your apps, see iOS Human Interface Guidelines.

CFBundleIcons

CFBundleIcons (Dictionary - iOS) contains information about all of the icons used by the app. This key allows you to group icons based on their intended usage and specify multiple icon files together with specific keys for modifying the appearance of those icons. This dictionary can contain the following keys:

The CFBundleIcons key is supported in iOS 5.0 and later. You may combine this key with the “CFBundleIconFiles” and “CFBundleIconFile” keys but in iOS 5.0 and later, this key takes precedence.

Contents of the CFBundlePrimaryIcon Dictionary

The value for the CFBundlePrimaryIcon key is a dictionary that identifies the icons associated with the app bundle. The icons in this dictionary are used to represent the app on the device’s Home screen and in the Settings app. Table 4 lists the keys that you can include in this dictionary and their values.

Table 4  Keys for the CFBundlePrimaryIcon dictionary

Key

Value

Description

CFBundleIconFiles

Array of strings

(Required) Each string in the array contains the name of an icon file. You can include multiple icons of different sizes to support iPhone, iPad, and universal apps.

For a list of the icons, including their sizes, that you can include in your app bundle, see the section on app icons in “Advanced App Tricks” in iOS App Programming Guide. For information about how to create icons for your apps, see iOS Human Interface Guidelines.

UIPrerenderedIcon

Boolean

This key specifies whether the icon files already incorporate a shine effect. If your icons already incorporate this effect, include the key and set its value to YES to prevent the system from adding the same effect again. If you do not include this key, or set its value to NO, the system applies a shine effect to the icon files listed in the CFBundleIconFiles key in this dictionary.

When specifying icon filenames, it is best to omit any filename extensions. Omitting the filename extension lets the system automatically detect high-resolution (@2x) versions of your image files using the standard-resolution image filename. If you include filename extensions, you must specify all image files (including the high-resolution variants) explicitly. The system looks for the icon files in the main resources directory of the bundle.

Contents of the UINewsstandIcon Dictionary

The value for the UINewsstandIcon key is a dictionary that identifies the default icons and style options to use for apps displayed in Newsstand. Table 5 lists the keys that you can include in this dictionary and their values.

Table 5  Keys for the UINewsstandIcon dictionary

Key

Value

Description

CFBundleIconFiles

Array of strings

(Required) Each string in the array contains the name of an icon file. You use this key to specify a set of standard icons for your app when presented in the Newsstand. This icon is used when no cover art is available for a downloaded issue.

For a list of the icons, including their sizes, that you can include in your app bundle, see the section on app icons in “App-Related Resources” in iOS App Programming Guide. For information about how to create icons for your apps, see iOS Human Interface Guidelines.

UINewsstandBindingType

String

This key provides information about how to stylize any Newsstand art. The value of this key is one of the following strings:

  • UINewsstandBindingTypeMagazine

  • UINewsstandBindingTypeNewspaper

UINewsstandBindingEdge

String

This key provides information about how to stylize any Newsstand art. The value of this key is one of the following strings:

  • UINewsstandBindingEdgeLeft

  • UINewsstandBindingEdgeRight

  • UINewsstandBindingEdgeBottom

When specifying icon filenames, it is best to omit any filename extensions. Omitting the filename extension lets the system automatically detect high-resolution (@2x) versions of your image files using the standard-resolution image filename. If you include filename extensions, you must specify all image files (including the high-resolution variants) explicitly. The system looks for the icon files in the main resources directory of the bundle.

CFBundleIdentifier

CFBundleIdentifier (String - iOS, OS X) uniquely identifies the bundle. Each distinct app or bundle on the system must have a unique bundle ID. The system uses this string to identify your app in many ways. For example, the preferences system uses this string to identify the app for which a given preference applies; Launch Services uses the bundle identifier to locate an app capable of opening a particular file, using the first app it finds with the given identifier; in iOS, the bundle identifier is used in validating the app’s signature.

The bundle ID string must be a uniform type identifier (UTI) that contains only alphanumeric (A-Z,a-z,0-9), hyphen (-), and period (.) characters. The string should also be in reverse-DNS format. For example, if your company’s domain is Ajax.com and you create an app named Hello, you could assign the string com.Ajax.Hello as your app’s bundle identifier.

CFBundleInfoDictionaryVersion

CFBundleInfoDictionaryVersion (String - iOS, OS X) identifies the current version of the property list structure. This key exists to support future versioning of the information property list file format. Xcode generates this key automatically when you build a bundle and you should not change it manually. The value for this key is currently 6.0.

CFBundleLocalizations

CFBundleLocalizations (Array - iOS, OS X) identifies the localizations handled manually by your app. If your executable is unbundled or does not use the existing bundle localization mechanism, you can include this key to specify the localizations your app does handle.

Each entry in this property’s array is a string identifying the language name or ISO language designator of the supported localization. See ““Language and Locale Designations”” in Internationalization Programming Topics in Internationalization Documentation for information on how to specify language designators.

CFBundleName

CFBundleName (String - iOS, OS X) identifies the short name of the bundle. This name should be less than 16 characters long and be suitable for displaying in the menu bar and the app’s Info window. You can include this key in the InfoPlist.strings file of an appropriate .lproj subdirectory to provide localized values for it. If you localize this key, you should also include the key “CFBundleDisplayName.”

CFBundlePackageType

CFBundlePackageType (String - iOS, OS X) identifies the type of the bundle and is analogous to the Mac OS 9 file type code. The value for this key consists of a four-letter code. The type code for apps is APPL; for frameworks, it is FMWK; for loadable bundles, it is BNDL. For loadable bundles, you can also choose a type code that is more specific than BNDL if you want.

All bundles should provide this key. However, if this key is not specified, the bundle routines use the bundle extension to determine the type, falling back to the BNDL type if the bundle extension is not recognized.

CFBundleShortVersionString

CFBundleShortVersionString (String - iOS, OS X) specifies the release version number of the bundle, which identifies a released iteration of the app. The release version number is a string comprised of three period-separated integers. The first integer represents major revisions to the app, such as revisions that implement new features or major changes. The second integer denotes revisions that implement less prominent features. The third integer represents maintenance releases.

The value for this key differs from the value for “CFBundleVersion,” which identifies an iteration (released or unreleased) of the app. This key can be localized by including it in your InfoPlist.strings files.

CFBundleSignature

CFBundleSignature (String - iOS, OS X) identifies the creator of the bundle and is analogous to the Mac OS 9 file creator code. The value for this key is a string containing a four-letter code that is specific to the bundle. For example, the signature for the TextEdit app is ttxt.

CFBundleURLTypes

CFBundleURLTypes (Array - iOS, OS X) contains an array of dictionaries, each of which describes the URL schemes (http, ftp, and so on) supported by the app. The purpose of this key is similar to that of “CFBundleDocumentTypes,” but it describes URL schemes instead of document types. Each dictionary entry corresponds to a single URL scheme. Table 6 lists the keys to use in each dictionary entry.

Table 6  Keys for CFBundleURLTypes dictionaries

Key

Xcode name

Type

Description

Platforms

CFBundleTypeRole

“Document Role”

String

This key specifies the app’s role with respect to the URL type. The value can be Editor, Viewer, Shell, or None. This key is required.

iOS, OS X

CFBundleURLIconFile

“Document Icon File Name”

String

This key contains the name of the icon image file (minus the extension) to be used for this URL type.

iOS, OS X

CFBundleURLName

“URL identifier”

String

This key contains the abstract name for this URL type. This is the main way to refer to a particular type. To ensure uniqueness, it is recommended that you use a Java-package style identifier. This name is also used as a key in the InfoPlist.strings file to provide the human-readable version of the type name.

iOS, OS X

CFBundleURLSchemes

“URL Schemes”

Array

This key contains an array of strings, each of which identifies a URL scheme handled by this type. For example, specifying the URL scheme feed makes other apps aware that this app is capable of viewing RSS content. Types of URL schemes include http, ftp, mailto, and so on.

iOS, OS X

CFBundleVersion

CFBundleVersion (String - iOS, OS X) specifies the build version number of the bundle, which identifies an iteration (released or unreleased) of the bundle. The build version number should be a string comprised of three non-negative, period-separated integers with the first integer being greater than zero. The string should only contain numeric (0-9) and period (.) characters. Leading zeros are truncated from each integer and will be ignored (that is, 1.02.3 is equivalent to 1.2.3). This key is not localizable.

CFPlugInDynamicRegistration

CFPlugInDynamicRegistration (String - OS X) specifies whether how host loads this plug-in. If the value is YES, the host attempts to load this plug-in using its dynamic registration function. If the value is NO, the host uses the static registration information included in the “CFPlugInFactories,” and “CFPlugInTypes” keys.

For information about registering plugins, see “Plug-in Registration” in Plug-in Programming Topics.

CFPlugInDynamicRegisterFunction

CFPlugInDynamicRegisterFunction (String - OS X) identifies the function to use when dynamically registering a plug-in. Specify this key if you want to specify one of your own functions instead of implement the default CFPlugInDynamicRegister function.

For information about registering plugins, see “Plug-in Registration” in Plug-in Programming Topics.

CFPlugInFactories

CFPlugInFactories (Dictionary - OS X) is used for static plug-in registration. It contains a dictionary identifying the interfaces supported by the plug-in. Each key in the dictionary is a universally unique ID (UUID) representing the supported interface. The value for the key is a string with the name of the plug-in factory function to call.

For information about registering plugins, see “Plug-in Registration” in Plug-in Programming Topics.

CFPlugInTypes

CFPlugInTypes (Dictionary - OS X) is used for static plug-in registration. It contains a dictionary identifying one or more groups of interfaces supported by the plug-in. Each key in the dictionary is a universally unique ID (UUID) representing the group of interfaces. The value for the key is an array of strings, each of which contains the UUID for a specific interface in the group. The UUIDs in the array corresponds to entries in the “CFPlugInFactories” dictionary.

For information about registering plugins, see “Plug-in Registration” in Plug-in Programming Topics.

CFPlugInUnloadFunction

CFPlugInUnloadFunction (String - OS X) specifies the name of the function to call when it is time to unload the plug-in code from memory. This function gives the plug-in an opportunity to clean up any data structures it allocated.

For information about registering plugins, see “Plug-in Registration” in Plug-in Programming Topics.