When I search for ADOBE AIR I find 'Adobe AIR Application Installer.app', 'Adobe AIR Uninstaller.app', and 'Adobe Flash Player Install Manager.app' in the Utilities folder. I don't find anything. Adobe is changing the world through digital experiences. We help our customers create, deliver and optimize content and applications. Work better together. Work better together. Adobe Creative Cloud has the apps and services you need to.
After double clicking the installer app, the window (Applications UtilitiesSelect an Installation Package) where the app was installed opened. The app (Adobe AIR. About Adobe AIR: The Adobe AIR runtime enables developers to package the same code into native applications and games for Windows and Mac OS desktops as well as iOS and Android devices, reaching over a billion desktop systems and mobile app stores for over 500 million devices.
As of AIR 2, you can use ADT to create native application installers for distributing AIR applications. For example, you can build an EXE installer file for distribution of an AIR application on Windows. You can build a DMG installer file for distribution of an AIR application on Mac OS. In AIR 2.5 and AIR 2.6, you can build a DEB or RPM installer file for distribution of an AIR application on Linux.
Applications installed with a native application installer are known as extended desktop profile applications. You cannot use ADT to package a native installer for an AIR application if the application descriptor file does not support the desktop extended profile. You can restrict this profile using the supportedProfiles element in the application descriptor file. See Device profiles and supportedProfiles.
You can build a native installer version of the AIR application in two basic ways:
- You can build the native installer based on the application descriptor file and other source files. (Other source files may include SWF files, HTML files, and other assets.)
- You can build the native installer based on an AIR file or based on an AIRI file.
You must use ADT on the same operating system as that of the native installer file you want to generate. So, to create an EXE file for Windows, run ADT on Windows. To create a DMG file for Mac OS, run ADT on Mac OS. To create a DEB or RPG file for Linux, run ADT from the AIR 2.6 SDK on Linux.
When you create a native installer to distribute an AIR application, the application gains these capabilities:
- It can launch and interact with native processes, using the NativeProcess class. For details, see one of the following:
- Communicating with native processes in AIR (for ActionScript developers)
- Communicating with native processes in AIR (for HTML developers)
- It can use native extensions.
- It can use the File.openWithDefaultApplication() method to open any file with the default system application defined to open it, regardless of its file type. (There are restrictions on applications that are not installed with a native installer. For details, see the entry for the File.openWithDefaultApplication() entry in the language reference.)
However, when packaged as a native installer, the application loses some of the benefits of the AIR file format. A single file can no longer be distributed to all desktop computers. The built-in update function (as well as the updater framework) does not work.
When the user double-clicks the native installer file, it installs the AIR application. If the required version of Adobe AIR is not already installed on the machine, the installer downloads it from the network and installs it first. If there is no network connection from which to obtain the correct version of Adobe AIR (if necessary), installation fails. Also, the installation fails if the operating system is not supported in Adobe AIR 2.
Note: If you want a file to be executable in your installed application, make sure that it's executable on the filesystem when you package your application. (On Mac and Linux, you can use chmod to set the executable flag, if needed.)
Creating a native installer from the application source files
To build a native installer out of the source files for the application, use the -package command with the following syntax (on a single command line):
This syntax is similar to the syntax for packaging an AIR file (without a native installer). However there are a few differences:
- You add the -target native option to the command. (If you specify -target air, then ADT generates an AIR file instead of a native installer file.)
- You specify the target DMG or EXE file as the installer_file.
- Optionally, on Windows you can add a second set of signing options, indicated as [WINDOWS_INSTALLER_SIGNING_OPTIONS] in the syntax listing. On Windows, in addition to signing the AIR file, you can sign the Windows Installer file. Use the same type of certificate and signing option syntax as you would for signing the AIR file (see ADT code signing options). You can use the same certificate to sign the AIR file and the installer file, or you can specify different certificates. When a user downloads a signed Windows Installer file from the web, Windows identifies the source of the file, based on the certificate.
For details on ADT options other than the -target option, see AIR Developer Tool (ADT).
The following example creates a DMG file (a native installer file for Mac OS):
The following example creates an EXE file (a native installer file for Windows):
The following example creates an EXE file and signs it:
Creating a native installer for an application that uses native extensions
You can build a native installer out of the source files for the application and the native extension packages that the application requires. Use the -package command with the following syntax (on a single command line):
This syntax is the same syntax used for packaging an a native installer, with two additional options. Use the -extdir extension-directory option to specify the directory that contains the ANE files (native extensions) that the application uses. Use the optional -migrate flag and MIGRATION_SIGNING_OPTIONS parameters to sign an update to an application with a migration signature, when the primary code-signing certificate is different certificate than the one used by the previous version. For more information see Signing an updated version of an AIR application.
For details on ADT options, see AIR Developer Tool (ADT).
The following example creates a DMG file (a native installer file for Mac OS) for an application that uses native extensions:
Creating a native installer from an AIR file or an AIRI file
You can use ADT to generate a native installer file based on an AIR file or an AIRI file. To build a native installer based on an AIR file, use the ADT -package command with the following syntax (on a single command line):
This syntax is similar to the syntax for creating a native installer based on the source files for the AIR application. However, there are a few differences:
- As the source, you specify an AIR file, rather than an application descriptor file and other source files for the AIR application.
- Do not specify signing options for the AIR file, as it is already signed
To build a native installer based on an AIRI file, use the ADT -package command with the following syntax (on a single command line):
This syntax is similar to the syntax for creating a native installer based on an AIR file. However there are a few of differences:
- As the source, you specify an AIRI file.
- You specify signing options for the target AIR application.
The following example creates a DMG file (a native installer file for Mac OS) based on an AIR file:
The following example creates an EXE file (a native installer file for Windows) based on an AIR file:
The following example creates an EXE file (based on an AIR file) and signs it:
The following example creates a DMG file (a native installer file for Mac OS) based on an AIRI file:
The following example creates an EXE file (a native installer file for Windows) based on an AIRI file:
The following example creates an EXE file (based on an AIRI file) and signs it with both an AIR and a native Windows signature:
Apple has changed Apple Mac App Store requirements and methodologies and that resulted in changes to the AIR runtime itself. This document explains how to post updated AIR applications to the Mac App store.
Steps to Post an AIR Application to the Mac App Store
Adobe Air Application Installer Mac
Note:
Posting an application to the Mac App Store requires manual steps. Make sure that you have a Mac developer account with Apple.
![Air Air](/uploads/1/1/8/5/118505571/349056204.png)
- Package your app with a captive runtime. The Mac App Store only accepts self-contained apps, and doesn't allow apps that use the shared AIR runtime. After packaging your .app bundle, manually open your Info.plist file in your favorite XML editor. Add an LSApplicationCategoryType entry.
- Also add a 512x512 icon to your Icon.icns file. (Currently the adt tool does not support icons of this size on Mac.) You can use Icon Composer (available with the xcode tools) to resize.
- Apple places several restrictions to post on the Mac App Store, including:
- The locations an app can write to
- The APIs an app can use (non-public APIs are not allowed)
- And the resources an app is allowed to use.
- WebKit uses a few non-public APIs that are not allowed on the Mac App Store, so you cannot use HTMLLoader or any class in the flash.html package in your app. Manually remove WebKit.dylib and Flash Player.plugin from the Adobe AIR.framework/Resources subtree inside your app bundle. You can use the StageWebView class but only when created with useNative=true.
- Additionally, if you are interested in decreasing the size of your app and you are not using any DRM functionality, you can manually remove Adobe AIR.vch, adobecp.plugin, adobecp.vch, and AdobeCP15.plugin from the Adobe AIR.framework/Resources subtree inside your app bundle.
- It is recommended that you use Mac OS 10.7 or higher to upload your app. There is a bug in Mac OS 10.6 that prevents Apple’s Application Loader from successfully uploading your app with the AIR runtime. To upload from Mac OS 10.6, there is a workaround:
- Delete the “Resources” symbolic link in the AIR framework folder and create a true folder called “Resources”.
- Copy the AIR Info.plist file (from Versions/1.0/Resources) into this new folder. Modify the original Info.plist file (inside Versions/1.0/Resources) by renaming the bundle id to com.adobe.AIR1.
Once your app package is ready, launch Terminal, and do the following:
Adobe Free For Mac
- Install your Developer Application and Developer Installer certificates on the Keychain. Use Apple's Developer Certificate Utility to create and install the certificates. The developer certificates refer to the 'WWDR Intermediate Certificate' and to the 'Apple Inc. Root Certificate'. These certificates are not required to be in the Keychain to sign an app. If needed, they can be obtained from Apple Root Certification Authority.
- Sign your app with your Mac Application account certificate.textcodesign -f -s '3rd Party Mac Developer Application: XXX' --entitlements ZZZ.entitlements YYY.appwhere XXX is the name on your cert, YYY is the name of your app, and ZZZ is an entitlements file. The entitlements file provides the list or resources and features the app is allowed to access.
- Build a .pkg installer for your app that is signed with your Mac Installer account certificate.productbuild --component YYY.app /Applications --sign '3rd Party Mac Developer Installer: XXX' YYY.pkgIf you are missing the productbuild tool, make sure that you have xcode 3.2.6 or above installed.
- Delete or zip the .app file after productbuild has created the .pkg (otherwise the installer test doesn't work).
- Install your app as if it came from the store.sudo installer -store -pkg YYY.pkg -target /
- Verify that your app is installed in Applications and is launchable.You are now ready to upload your app. Before doing so, you must create meta-data for your app on iTunes Connect.
- Log in using your Apple ID.
- Follow the Manage Your Applications link.
- And click the Add New App button to create the meta-data.
Then, use Application Loader to upload the app for review. (Application Loader is part of Xcode tools, versions 3.2.6 and above. Application Loader is also available as a stand-alone download). You find out right away if your application bundle is well-formed. But it takes a few days to find out if Apple approved it or not.In particular, if you are using a self-signed certificate you could get the following warning from iTunes Connect:Adobe has discovered one or more issues with your recent binary submission for 'YYY'. Your app has proceeded to review, but the following issues should be corrected in your next submission:
Invalid Signature - the nested app bundle (YYY.app/Contents/Frameworks/Adobe AIR.framework) is not signed, the signature is invalid, or it is not signed with an Apple submission certificate. Refer to the Code Signing and Application Sandboxing Guide for more information.