- Bluish-green Bundle Mac Os Catalina
- Bluish-green Bundle Mac Os Catalina
- Bluish-green Bundle Mac Os Download
- Mac Os Mojave
Apple Mac OS X Package File Files with the extension.BUNDLE are package files associated with MAC OS X.BUNDLE files are special folders used to group multiple resources together but they are displayed within 'Finder' as a single file. Mac OS X & macOS names. As you can see from the list above, with the exception of the first OS X beta, all versions of the Mac operating system from 2001 to 2012 were all named after big cats. Mac OS X v10.5 (Leopard) introduced the concept of sparse-bundle disk images, where the data is stored as a collection of small, fixed-size band-files instead of as a single monolithic file. This allows for more efficient backups of the disk image, as only the changed bands need to be stored. Intel processor; Mac OS 10.7 or newer (Catalina and Big Sur are both supported) VST / VST3 / Audio Unit / AAX compatible DAW (32-bit or 64-bit) Windows. Windows 7 / 8 / 10; VST / VST3 / AAX compatible DAW (32 or 64 bit). Mar 04, 2021 THE NEW MACOS POWER BUNDLE FROM BUNDLEHUNT – STARTING AT $3.5. Bundlehunt just presented its latest bundle for MAC only. The so called 2021 macOS Power Bundle let's you choose among 45 apps and lets you add as many adds you want for prices between $1 to $10 per app.
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.
Key | Xcode name | Summary | Platforms |
|---|---|---|---|
CFAppleHelpAnchor | 'Help file' | The bundle's initial HTML help file. See CFAppleHelpAnchor for details. | macOS |
CFBundleAllowMixedLocalizations | 'Localized resources can be mixed' | Used by Foundation tools to retrieve localized resources from frameworks. See CFBundleAllowMixedLocalizations for details. | iOS, macOS |
CFBundleDevelopmentRegion | 'Localization native development region' | (Recommended) The default language and region for the bundle, as a language ID. See CFBundleDevelopmentRegion for details. | iOS, macOS |
CFBundleDisplayName | 'Bundle display name' | (Required, Localizable) The user-visible name of the bundle; used by Siri and visible on the Home screen in iOS. See CFBundleDisplayName for details. | iOS, macOS |
CFBundleDocumentTypes | 'Document types' | An array of dictionaries describing the document types supported by the bundle. See CFBundleDocumentTypes for details. | iOS, macOS |
CFBundleExecutable | 'Executable file' | (Recommended) Name of the bundle's executable file. See CFBundleExecutable for details. | iOS, macOS |
CFBundleHelpBookFolder | 'Help Book directory name' | The name of the folder containing the bundle's help files. See CFBundleHelpBookFolder for details. | macOS |
CFBundleHelpBookName | 'Help Book identifier' | The name of the help file to display when Help Viewer is launched for the bundle. See CFBundleHelpBookName for details. | macOS |
CFBundleIconFile | 'Icon file' | A legacy way to specify the app's icon. Use the CFBundleIcons or CFBundleIconFiles keys instead. See CFBundleIconFile for details. | iOS, macOS |
CFBundleIconName | 'Icon Name' | The name of the asset, from the bundle's Asset Catalog, that represents the icon for the bundle. If you do not specify this key, CFBundleIconFile is used to identify the file containing the icon. | macOS 10.13 and later |
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 CFBundleIcons for details. | iOS 5.0 and later, tvOS 9 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, macOS |
CFBundleInfoDictionaryVersion | 'InfoDictionary version' | (Recommended) Version information for the | iOS, macOS |
CFBundleLocalizations | 'Localizations' | Contains localization information for an app that handles its own localized resources. See CFBundleLocalizations for details. | iOS, macOS |
CFBundleName | 'Bundle name' | (Recommended, Localizable) The short name of the bundle. See CFBundleName for details. | iOS, macOS |
CFBundlePackageType | 'Bundle OS Type code' | The four-letter code identifying the bundle type. See CFBundlePackageType for details. | iOS, macOS |
CFBundleShortVersionString | 'Bundle versions string, short' | (Localizable) The release-version-number string for the bundle. See CFBundleShortVersionString for details. | iOS, macOS |
CFBundleSpokenName | 'Accessibility bundle name' | The spoken name of the app. See CFBundleSpokenName for details. | iOS, macOS |
CFBundleURLTypes | 'URL types' | An array of dictionaries describing the URL schemes supported by the bundle. See CFBundleURLTypes for details. | iOS, macOS |
CFBundleVersion | 'Bundle version' | (Recommended) The build-version-number string for the bundle. See CFBundleVersion for details. | iOS, macOS |
CFPlugInDynamicRegistration | 'Plug-in should be registered dynamically' | If YES, register the plug-in dynamically; otherwise, register it statically. See CFPlugInDynamicRegistration for details. | macOS |
CFPlugInDynamicRegistrationFunction | Plug-in dynamic registration function name' | The name of the custom, dynamic registration function. See CFPlugInDynamicRegisterFunction for details. | macOS |
CFPlugInFactories | 'Plug-in factory interfaces' | For static registration, this dictionary contains a list of UUIDs with matching function names. See CFPlugInFactories for details. | macOS |
CFPlugInTypes | 'Plug-in types' | For static registration, the list of UUIDs CFPlugInTypes for details. | macOS |
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. | macOS |
CFAppleHelpAnchor
CFAppleHelpAnchor (String - macOS) 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, macOS) 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, macOS) specifies the default language and region for the bundle, as a language ID. For example, English for Australia has the language ID en-AU. The system uses this value if it cannot locate a resource for the user's preferred language.
For more information, see Language IDs in Internationalization and Localization Guide. For details on how a bundle finds localized resources, see The Bundle Search Pattern in Bundle Programming Guide.
CFBundleDisplayName
CFBundleDisplayName (String - iOS, macOS) specifies the display name of the bundle, visible to users and used by Siri. If you support localized names for your bundle, include this key in your app's Info.plist file and in the InfoPlist.strings files of your app's language subdirectories. If you localize this key, include a localized version of the CFBundleName key as well.
Because Siri uses the value of this key, always provide a value, whether or not you localize your app.
In macOS, 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 macOS, see File System Programming Guide.
CFBundleDocumentTypes
CFBundleDocumentTypes (Array - iOS, macOS) 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.
Key | Xcode name | Type | Description | Platforms |
|---|---|---|---|---|
CFBundleTypeExtensions | 'Document Extensions' |
| 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 ' | macOS |
CFBundleTypeIconFile | 'Icon File Name' |
| This key contains a string with the name of the icon file ( | macOS |
CFBundleTypeIconFiles | None |
| 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' |
| 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 | macOS |
CFBundleTypeName | 'Document Type Name' |
| 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 | iOS, macOS |
CFBundleTypeOSTypes | 'Document OS Types' |
| 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 ( | macOS |
CFBundleTypeRole | 'Role' |
| This key specifies the app's role with respect to the type. The value can be | macOS |
LSItemContentTypes | 'Document Content Type UTIs' |
| 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 ' | iOS, macOS |
LSHandlerRank | 'Handler rank' |
| 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: | iOS, macOS |
LSTypeIsPackage | 'Document is a package or bundle' |
| Specifies whether the document is distributed as a bundle. If set to true, the bundle directory is treated as a file. (In macOS 10.4 and later, this key is ignored if the | macOS |
NSDocumentClass | 'Cocoa NSDocument Class' |
| This key specifies the name of the | macOS |
NSUbiquitousDocumentUserActivityType | None |
| This key specifies the activity type of the | iOS, macOS |
NSExportableAs | 'Exportable As Document Type Names' |
| This key specifies an array of strings. Each string contains the name of another document type, that is, the value of a | macOS |
NSExportableTypes | None |
| 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 ' | macOS |
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 all versions of macOS. 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.
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 macOS, 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:
CFBundleTypeIconFileCFBundleTypeNameCFBundleTypeRole
In addition to these keys, it must contain at least one of the following keys:
LSItemContentTypesCFBundleTypeExtensionsCFBundleTypeMIMETypesCFBundleTypeOSTypes
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 macOS 10.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, macOS) 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.
Important: You must include a valid CFBundleExecutable key in your bundle's information property list file. macOS uses this key to locate the bundle's executable or shared library in cases where the user renames the app or bundle directory.
CFBundleHelpBookFolder
CFBundleHelpBookFolder (String - macOS) 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 - macOS) 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, macOS) 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 and the asset name for the icon isn't set in CFBundleIconName, you must specify the CFBundleIconFile property. If you do not specify this property, the system (and other apps) display your bundle with a default icon.
Note: If you are writing an iOS, tvOS, or watchOS app, use of the CFBundleIcons key instead of this one.
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.
The CFBundleIcons key takes precedence over this key in iOS 5.0 and later. This key takes precedence over 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 information about how to create icons for your apps, including the size information for each one, see iOS Human Interface Guidelines.
CFBundleIcons
CFBundleIcons (Dictionary - iOS, tvOS) 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:
CFBundlePrimaryIcon—This key identifies the primary icon for the Home screen and Settings app among others. The value for this key is described in Contents of the CFBundlePrimaryIcon Dictionary Entry.
CFBundleAlternateIcons—This key identifies alternate icons for the Home screen and Settings app among others. The value for this key is described in Contents of the CFBundleAlternateIcons Dictionary Entry.
UINewsstandIcon—This key identifies default icons to use for apps presented from Newsstand. The value for this key is a dictionary whose contents are described in Contents of the UINewsstandIcon Dictionary.
The CFBundleIcons key is supported in iOS 5.0 and later and in tvOS 9.0 and later. In iOS, you can 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 Entry
The value of the CFBundlePrimaryIcon key is different in iOS and tvOS:
In tvOS, the value of this key is a string. The value of the string is the name of an icon file in your app. For information about the icon file for your tvOS app, see 'Icons and Images' in Apple TV Human Interface Guidelines
In iOS, the value of the key is a dictionary. Table 4 lists the keys and values that you include in this dictionary.
Key | Value | Description |
|---|---|---|
CFBundleIconName | String | (Recommended for iOS 11 and later.) The name of the asset, from the bundle's Asset Catalog, that represents the app icon. If you use this key, you should also include at least one item in |
CFBundleIconFiles | Array of strings | (Required if targeting iOS 10 or earlier.) 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 Providing the Required Resources in App Programming Guide for iOS. 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 |
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 CFBundleAlternateIcons Dictionary Entry
The value of the CFBundleAlternateIcons key is different in iOS and tvOS:
In tvOS, the value of the key is an array of strings. The value of each string is the name of an icon file in your app. For information about the icon file for your tvOS app, see 'Icons and Images' in Apple TV Human Interface Guidelines
In iOS, the value of the key is a dictionary. The key for each dictionary entry is the name of the alternate icon, which is also the string you pass to the
setAlternateIconName:completionHandler:method ofUIApplicationwhen changing icons. The value for each key is a dictionary containing the keys in Table 5.
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 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 |
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.
Important: If your app contains iPad-specific versions of its icons, the system does not fall back to the alternate icons declared in the platform-agnostic version of CFBundleIcons key. Therefore, if you include any alternate icons in the CFBundleIcons key, you must include them again in your CFBundleIcons~ipad variant.
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 6 lists the keys that you can include in this dictionary and their values.
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 App Programming Guide for iOS. 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:
|
UINewsstandBindingEdge | String | This key provides information about how to stylize any Newsstand art. The value of this key is one of the following strings:
|
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, macOS) 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.
Note: Although formatted similarly to a UTI, the character set for a bundle identifier is more restrictive.
CFBundleInfoDictionaryVersion
CFBundleInfoDictionaryVersion (String - iOS, macOS) 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, macOS) 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 and Localization Guide in Internationalization Documentation for information on how to specify language designators.
CFBundleName
CFBundleName (String - iOS, macOS) specifies the short name of the bundle, which may be displayed to users in situations such as the absence of a value for CFBundleDisplayName. This name should be less than 16 characters long.
See also CFBundleDisplayName.
CFBundlePackageType
CFBundlePackageType (String - iOS, macOS) 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, macOS) specifies the release version number of the bundle, which identifies a released iteration of the app.
The release version number is a string composed of three period-separated integers. The first integer represents major revision to the app, such as a revision that implements new features or major changes. The second integer denotes a revision that implements less prominent features. The third integer represents a maintenance release revision.
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.
See also NSHumanReadableCopyright. Get in, get out mac os.
CFBundleSpokenName
CFBundleSpokenName (String - iOS, macOS) contains a suitable replacement for the app name when performing text-to-speech operations. Include this key in your app bundle when the spelling of your app might be mispronounced by the speech system. For example, if the name of your app is 'MyApp123', you might set the value of this key to 'My app one two three'.
This key is supported in iOS 8 and later and in macOS 10.10 and later.
CFBundleURLTypes
CFBundleURLTypes (Array - iOS, macOS) 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 7 lists the keys to use in each dictionary entry.
Key | Xcode name | Type | Description | Platforms |
|---|---|---|---|---|
CFBundleTypeRole | 'Document Role' |
| This key specifies the app's role with respect to the URL type. The value can be | iOS, macOS |
CFBundleURLIconFile | 'Document Icon File Name' |
| This key contains the name of the icon image file (minus the extension) to be used for this URL type. | iOS, macOS |
CFBundleURLName | 'URL identifier' |
| 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 | iOS, macOS |
CFBundleURLSchemes | 'URL Schemes' |
| This key contains an array of strings, each of which identifies a URL scheme handled by this type. For example, specifying the URL scheme | iOS, macOS |
To learn about the converse operation in iOS of declaring the URL schemes an app can open, read the description of the LSApplicationQueriesSchemes key.
CFBundleVersion
CFBundleVersion (String - iOS, macOS) 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—for example, 3.1.2. 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). The meaning of each element is as follows:
The first number represents the most recent major release and is limited to a maximum length of four digits.
The second number represents the most recent significant revision and is limited to a maximum length of two digits.
The third number represents the most recent minor bug fix and is limited to a maximum length of two digits.
If the value of the third number is 0, you can omit it and the second period.
While developing a new version of your app, you can include a suffix after the number that is being updated; for example 3.1.3a1. The character in the suffix represents the stage of development for the new version. For example, you can represent development, alpha, beta, and final candidate, by d, a, b, and fc. The final number in the suffix is the build version, which cannot be 0 and cannot exceed 255. When you release the new version of your app, remove the suffix.
CFPlugInDynamicRegistration
CFPlugInDynamicRegistration (String - macOS) 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 - macOS) 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 - macOS) 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.
Bluish-green Bundle Mac Os Catalina
For information about registering plugins, see 'Plug-in Registration' in Plug-in Programming Topics.
CFPlugInTypes
CFPlugInTypes (Dictionary - macOS) 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 - macOS) 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.
Copyright © 2018 Apple Inc. All Rights Reserved. Terms of Use | Privacy Policy | Updated: 2018-06-04
Basic Information about Corrupt app bundle app:
CFBundleName (String - iOS, macOS) specifies the short name of the bundle, which may be displayed to users in situations such as the absence of a value for CFBundleDisplayName. This name should be less than 16 characters long.
See also CFBundleDisplayName.
CFBundlePackageType
CFBundlePackageType (String - iOS, macOS) 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, macOS) specifies the release version number of the bundle, which identifies a released iteration of the app.
The release version number is a string composed of three period-separated integers. The first integer represents major revision to the app, such as a revision that implements new features or major changes. The second integer denotes a revision that implements less prominent features. The third integer represents a maintenance release revision.
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.
See also NSHumanReadableCopyright. Get in, get out mac os.
CFBundleSpokenName
CFBundleSpokenName (String - iOS, macOS) contains a suitable replacement for the app name when performing text-to-speech operations. Include this key in your app bundle when the spelling of your app might be mispronounced by the speech system. For example, if the name of your app is 'MyApp123', you might set the value of this key to 'My app one two three'.
This key is supported in iOS 8 and later and in macOS 10.10 and later.
CFBundleURLTypes
CFBundleURLTypes (Array - iOS, macOS) 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 7 lists the keys to use in each dictionary entry.
Key | Xcode name | Type | Description | Platforms |
|---|---|---|---|---|
CFBundleTypeRole | 'Document Role' |
| This key specifies the app's role with respect to the URL type. The value can be | iOS, macOS |
CFBundleURLIconFile | 'Document Icon File Name' |
| This key contains the name of the icon image file (minus the extension) to be used for this URL type. | iOS, macOS |
CFBundleURLName | 'URL identifier' |
| 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 | iOS, macOS |
CFBundleURLSchemes | 'URL Schemes' |
| This key contains an array of strings, each of which identifies a URL scheme handled by this type. For example, specifying the URL scheme | iOS, macOS |
To learn about the converse operation in iOS of declaring the URL schemes an app can open, read the description of the LSApplicationQueriesSchemes key.
CFBundleVersion
CFBundleVersion (String - iOS, macOS) 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—for example, 3.1.2. 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). The meaning of each element is as follows:
The first number represents the most recent major release and is limited to a maximum length of four digits.
The second number represents the most recent significant revision and is limited to a maximum length of two digits.
The third number represents the most recent minor bug fix and is limited to a maximum length of two digits.
If the value of the third number is 0, you can omit it and the second period.
While developing a new version of your app, you can include a suffix after the number that is being updated; for example 3.1.3a1. The character in the suffix represents the stage of development for the new version. For example, you can represent development, alpha, beta, and final candidate, by d, a, b, and fc. The final number in the suffix is the build version, which cannot be 0 and cannot exceed 255. When you release the new version of your app, remove the suffix.
CFPlugInDynamicRegistration
CFPlugInDynamicRegistration (String - macOS) 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 - macOS) 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 - macOS) 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.
Bluish-green Bundle Mac Os Catalina
For information about registering plugins, see 'Plug-in Registration' in Plug-in Programming Topics.
CFPlugInTypes
CFPlugInTypes (Dictionary - macOS) 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 - macOS) 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.
Copyright © 2018 Apple Inc. All Rights Reserved. Terms of Use | Privacy Policy | Updated: 2018-06-04
Basic Information about Corrupt app bundle app:
Corrupt app bundle app is a dangerous adware application that annoys many computer users recently. It silently penetrates into computers without the knowledge of users. After getting into the targeted Windows system, it creates a lot of trouble for users and starts generating frustrating pop-up ads, deals, coupons, discounts, fake message, sponsored links and other online savings in the web browsers. Usually, Corrupt app bundle app affects the most used browsers including Google Chrome, Internet Explorer and Mozilla Firefox.
There are some common symptoms of this malicious threat:
1) There are lots of random ads and pop-up windows suddenly appears on your web browsers;
2) When you browser on the Internet, it doesn't open the your homepage rather points your to some strange websites;
3) All your browsers will starting working strangely that you haven't experienced before;
4) Your DNS settings and other system settings will be changed;
5) Corrupt app bundle app installs other malicious add-ons and applications to your system automatically;
6) Your system will freeze frequently and it is difficult to work on the computer.
Once Corrupt app bundle app is installed on your computer, all things will be changed. It can mess up your browsers seriously. When you click or visit the certain page, you can be redirected to some unknown sites that may contain various computer threats. What's worse, it is not easy to remove Corrupt app bundle app because it can change its files all the time and hide itself secretly in your system. Each time you try to uninstall it from Control Panel, it keeps coming back again and again.
How to Remove Malware from Mac?
If you have virus problem on Windows OS, please read this Win OS Guide – Manually Remove Virus or malware from Windows OS
(NOTE: Bookmark this page first because some steps may close your web browser or restart computer)
STEP 1
– Select Finder on dock:
Select Applications >> Right-lick on unwanted or suspicious apps that may be related with Corrupt app bundle app >> Click Move to Trash
Go to Dock >> Right-click on Trash icon and click Empty Trash.
Tips– In case you are unable to find or remove suspicious apps that may be related with threat, we recommend downloading Combo Clneaer to scan your mac and find out malware:
(Note – To understand Combo Cleaner's policies and practices, please review its EULA, and Privacy Policy. Learn more about Combo Cleaner and its key features. Combo Cleaner's scanner is free. Once it detects a virus or malware, you'll need to purchase its full version to remove the threat.)
STEP 2
Uninstall Unwanted or Suspicious Extension that May Be Related with Threat:
On Safari:
Launch Safari and Click Preferences
Select Extensions tab >> Find unwanted or suspicious extension that may be related with Corrupt app bundle app >> Click Uninstall
On Chrome:
Launch Chrome >> Select More Tools >> Click Extensions:
Bluish-green Bundle Mac Os Catalina
Find unwanted or suspicious extension that may be related with Corrupt app bundle app >> Click Trash icon to uninstall it.
On Firefox:
Launch Firefox >> Click Add-ons:
Select Extensions tab >> Find unwanted or suspicious extension that may be related with Corrupt app bundle app >> Click Remove
Tips– In case you are unable to find or remove suspicious extension that may be related with threat, we recommend downloading Combo Cleaner Antivirus and see if it will find and clean up the threats for you.
(Note – To understand Combo Cleaner's policies and practices, please review its EULA, and Privacy Policy. Learn more about Combo Cleaner and its key features. Combo Cleaner's scanner is free. Once it detects a virus or malware, you'll need to purchase its full version to remove the threat.)
Combo Cleaner Antivirus – The most comprehensive and complete utilities application that you will ever need to keep your Mac clutter and virus free. It is a one-stop Mac and protection maintenance tool to remove Mac malware, clean up junks, and boost Mac performance. With greatly expanded virus and malware database, Combo Cleaner Antivirus is a reliable anti-malware to keep your Mac away from virus, phishing attacks, spyware, malware, and all kinds of online threats while feeling safe about your personal data. Furthermore, it is able to speed up your Mac maximally and make your machine run as a new one.
Award Winning Scanners of Combo Cleaner
Diagnose Your Mac with Combo Cleaner Antivirus Now:
1. Download Combo Cleaner Antivirus with the given button below:,
(Note – To understand Combo Cleaner's policies and practices, please review its EULA, and Privacy Policy. Learn more about Combo Cleaner and its key features. Combo Cleaner's scanner is free. Once it detects a virus or malware, you'll need to purchase its full version to remove the threat.)
2. Then install it and start a Scan to check the conditions of your Mac OS. If you want to use it to solve the detected issues, you need to register its full version to continue.
3. Re-check your Mac with Uninstaller function Anti-virus function of Combo Cleaner.
– First, use Uninstaller tool to check if any unwanted apps are still in the Apps list. If there is unwanted apps in the list, please select them and click 'Remove Selected Items'.
Bluish-green Bundle Mac Os Download
– Second, use Antivirus tool to run a Quick Scan and determine if there unsafe items hiding on your Mac.
Tips for Threat Prevention
– Always running professional Antivirus or Antimalware and keep Firewall ON;
Mac Os Mojave
– Create System Restore Point regularly and back up important personal files;
– Avoid downloading free programs from unknown third party shared sites;
– Regularly update system via automatic system update;
– Don't access porn sites or similar sites which are potentially harmful;
– Avoid opening any attachments of unknown emails.
