ADT  native installation

hey,
i try tu rin this example from adobe developer resource
http://www.adobe.com/devnet/air/flex/quickstart/interacting_with_native_process.html
about the native porcess
but i can't make a native installer (.exe) with ADT
i have try with this command
C:\Flex4AIR2\bin\adt -package -storetype pkcs12 -keystore Cert.p12 -storepass XXXX -target native NativeProcessTest.exe NativeProcessTest-app.xml NativeProcessTest.swf NativeApps/Windows/bin/echoTestWindows icons
after opening the command pompt with cd pointing to my src folder of my flex project
rem : i have put NativeProcessTest.swf in the src poject with the certificat
i have tried a lot of combinaison but no succes,...
have you an issue
rem: run on 7 64 bits

On Windows 7, make sure you are running as Administrator:
Download and install Adobe AIR from this page
Download YNAB3_Live_3.5.3.4.air to a folder on your computer.
Navigate to the folder on your computer where you saved the YNAB3_Live_3.5.3.4.air. If you are on Windows Vista or Windows 7, right-click on the file and choose “Run as Administrator.” For Mac, Linux, and all other versions of Windows, simply double-click on it to install YNAB 3.
Thanks,
Lisa Chao
Adobe Flash Runtime Team

Similar Messages

  • Can an ADT-packaged native installer install the AIR runtime in silent mode?

    Silent installation of my app works fine when the runtime is installed, as follows:
    <path>\MyApp.exe -silent -location "\"C:\Program Files\MyApp\"" -desktopShortcut -programMenu
    However, if the runtime is not installed, the invocation does nothing. I've also tried -eulaAccepted.
    Is it possible to silently install the app, yet if the runtime is not installed, initiate the runtime install automatically from adobe, preferably with a eula prompt for the user?
    Worst case, if the runtime must be bundled in the package, is a sidecar install supported for native installers?
    I should note, I cannot package the app as .air. The app uses NativeProcess and bundles an exe.
    Thanks.

    chris.campbell wrote:
    Dmitry Svetlakov wrote:
    I try use silent mode under Mac OS - doesn't work in this situation: Adobe AIR not installed on system.
    Because isntaller needs in access from administrator.
    Log:
    Jul 18 15:36:01 user-macbook-pro /var/folders/f+/f+YgX8A8EzyL0WM6aZ2rT++++TI/-Tmp-/airNEZFRK/Adobe AIR Installer.app/Contents/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[8694]: Could not create directory at /Applications/Adobe/Flash Player/AddIns/airappinstaller
    Jul 18 15:36:01 user-macbook-pro /var/folders/f+/f+YgX8A8EzyL0WM6aZ2rT++++TI/-Tmp-/airNEZFRK/Adobe AIR Installer.app/Contents/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[8694]: Error occurred during copy and set resource fork operation; beginning rollback: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="Unhandled exception Error: Could not create directory /Applications/Adobe/Flash Player/AddIns/airappinstaller" errorID=3001]
    Jul 18 15:36:09 user-macbook-pro /var/folders/f+/f+YgX8A8EzyL0WM6aZ2rT++++TI/-Tmp-/airNEZFRK/Adobe AIR Installer.app/Contents/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[8694]: Rollback complete
    Jul 18 15:36:09 user-macbook-pro /var/folders/f+/f+YgX8A8EzyL0WM6aZ2rT++++TI/-Tmp-/airNEZFRK/Adobe AIR Installer.app/Contents/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[8694]: Got an unexpected fatal error while in stateInstalling: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="Unhandled exception Error: Could not create directory /Applications/Adobe/Flash Player/AddIns/airappinstaller" errorID=3001]
    Jul 18 15:36:09 user-macbook-pro /var/folders/f+/f+YgX8A8EzyL0WM6aZ2rT++++TI/-Tmp-/airNEZFRK/Adobe AIR Installer.app/Contents/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[8694]: Application Installer end with exit code 7
    Hi Dmitry,
    Are you trying to sub launch AIR silently through your installer?  If so, and you haven't already, please fill out the AIR distribution agreement form and you'll receive documentation that discusses silent installs and uninstall's.
    If you are just trying this out, you are correct that the runtime needs admin access.  You can achieve this by prefixing your command line with sudo.
    Thanks,
    Chris
    Yes, but that not decide our task: create custom installer from air app native installer. I hope you understand that i mean. This installer should work for anyone user - and have to install Adobe AIR Runtime.

  • Show progress bar and percents when packaging a native installer with adt packager

    Hello,
    Below is a simple example using the AIR's NativeProcess for compiling an air application into a native installer... Everything works fine, so at the end of the NativeProcess, the native installer (*.exe) is created... In this case, the application which I'm trying to compile is small (approx. 600KB)... However, if I have to package into native installer a bigger file (several MBs), I would like also to monitor the progress by using a progress bar and percents... How?
    private var file:File
    private var nativeProcessStartupInfo:NativeProcessStartupInfo;
    private var nativeProcess:NativeProcess;
    private function compile():void{
      file = new File("C:\\Program Files\\Java\\jre7\\bin\\java.exe");
      nativeProcessStartupInfo = new NativeProcessStartupInfo();
      var args:Vector.<String> = new Vector.<String>();
      args.push("-jar");
      args.push(adtPath);
      args.push("-package");
      args.push("-storetype");
      args.push("pkcs12");
      args.push("-keystore");
      args.push(certPath);
      args.push("-storepass");
      args.push("mypass");
      args.push("-target");
      args.push("native");
      args.push(exePath);
      args.push(xmlPath);
      args.push("-C");
      args.push(swfPath);
      args.push("testApp.swf");
      args.push("icons");
      nativeProcessStartupInfo.arguments = args;
      nativeProcessStartupInfo.executable = file;
      nativeProcess = new NativeProcess();
      nativeProcess.addEventListener(ProgressEvent.STANDARD_OUTPUT_DATA, onOutputData);
      nativeProcess.addEventListener(ProgressEvent.STANDARD_ERROR_DATA, onErrorData);
      nativeProcess.start(nativeProcessStartupInfo);
    private function onOutputData(event:ProgressEvent):void{
       var op:String =  nativeProcess.standardOutput.readUTFBytes(nativeProcess.standardOutput.bytesAvailable);
       trace("output = " + op);
    private function onErrorData(event:ProgressEvent):void{
       var er:String = nativeProcess.standardError.readUTFBytes(nativeProcess.standardError.bytesAvailable);
       trace("error = " + er);
    Thanks in advance,
    Nikola

    Someone to offer a solution to this problem (if exists)?

  • Packaging an AIR application in a native installer

    Hi! I'm trying to create a native installer of my AIR Application,  because (I think) it's the only way make the native processes working.  But I have a problem: I used the following command to pack: "adt  -package -storetype pkcs12 -keystore myCert.pfx -target native  -storetype pkcs12 -keystore myCert.pfx myApp.exe myApp-app.xml", but I get  the error: "File myApp-app.xml is not a valid AIRI or AIR file". In the  Flash Builder I use as additional compiler arguments:  "-locale=pt_PT,en_UK,fr_FR,de_DE,ro_RO,es_ES  -allow-source-path-overlap=true -source-path=assets" and I add the  source path "src/locale/{locale}/". What is the sintax for packing my  AIR application in a native installer? Thanks in advance.

    Hi again! Thanks for the reply. I based myself on the link to see what command syntax I should use to pack my Air Windowed Application and it was the command that I presented in the previous post.
    adt version "2.0.1.12090"
                                                  My Descriptor File
    <?xml version="1.0" encoding="utf-8" standalone="no"?>
    <application xmlns="http://ns.adobe.com/air/application/2.0">
    <!-- Adobe AIR Application Descriptor File Template.
        Specifies parameters for identifying, installing, and launching AIR applications.
        xmlns - The Adobe AIR namespace: http://ns.adobe.com/air/application/2.0
                The last segment of the namespace specifies the version
                of the AIR runtime required for this application to run.
        minimumPatchLevel - The minimum patch level of the AIR runtime required to run
                the application. Optional.
    -->
        <!-- A universally unique application identifier. Must be unique across all AIR applications.
             Using a reverse DNS-style name as the id is recommended. (Eg. com.example.ExampleApplication.) Required. -->
        <id>com.MyCompany.Application</id>
        <!-- Used as the filename for the application. Required. -->
        <filename>Production Control System</filename>
        <!-- The name that is displayed in the AIR application installer.
             May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <name>Production Control System</name>
        <!-- An application version designator (such as "v1", "2.5", or "Alpha 1"). Required. -->
        <version>2.1.3</version>
        <!-- Description, displayed in the AIR application installer.
             May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <!-- <description></description> -->
        <!-- Copyright information. Optional -->
        <!-- <copyright></copyright> -->
        <!-- Publisher ID. Used if you're updating an application created prior to 1.5.3 -->
        <!-- <publisherID>My Company</publisherID> -->
        <!-- Settings for the application's initial window. Required. -->
        <initialWindow>
            <!-- The main SWF or HTML file of the application. Required. -->
            <!-- Note: In Flash Builder, the SWF reference is set automatically. -->
            <content>[This value will be overwritten by Flash Builder in the output app.xml]</content>
            <!-- The title of the main window. Optional. -->
            <!-- <title></title> -->
            <!-- The type of system chrome to use (either "standard" or "none"). Optional. Default standard. -->
            <systemChrome>none</systemChrome>
            <!-- Whether the window is transparent. Only applicable when systemChrome is none. Optional. Default false. -->
            <transparent>true</transparent>
            <!-- Whether the window is initially visible. Optional. Default false. -->
            <!-- <visible></visible> -->
            <!-- Whether the user can minimize the window. Optional. Default true. -->
            <!-- <minimizable></minimizable> -->
            <!-- Whether the user can maximize the window. Optional. Default true. -->
            <!-- <maximizable></maximizable> -->
            <!-- Whether the user can resize the window. Optional. Default true. -->
            <!-- <resizable></resizable> -->
            <!-- The window's initial width in pixels. Optional. -->
            <!-- <width></width> -->
            <!-- The window's initial height in pixels. Optional. -->
            <!-- <height></height> -->
            <!-- The window's initial x position. Optional. -->
            <!-- <x></x> -->
            <!-- The window's initial y position. Optional. -->
            <!-- <y></y> -->
            <!-- The window's minimum size, specified as a width/height pair in pixels, such as "400 200". Optional. -->
            <!-- <minSize></minSize> -->
            <!-- The window's initial maximum size, specified as a width/height pair in pixels, such as "1600 1200". Optional. -->
            <!-- <maxSize></maxSize> -->
        </initialWindow>
        <!-- We recommend omitting the supportedProfiles element, -->
        <!-- which in turn permits your application to be deployed to all -->
        <!-- devices supported by AIR. If you wish to restrict deployment -->
        <!-- (i.e., to only mobile devices) then add this element and list -->
        <!-- only the profiles which your application does support. -->
        <!-- <supportedProfiles>desktop extendedDesktop mobileDevice extendedMobileDevice</supportedProfiles> -->
        <supportedProfiles>extendedDesktop</supportedProfiles>
        <!-- The subpath of the standard default installation location to use. Optional. -->
        <!-- <installFolder></installFolder> -->
        <!-- The subpath of the Programs menu to use. (Ignored on operating systems without a Programs menu.) Optional. -->
        <!-- <programMenuFolder></programMenuFolder> -->
        <!-- The icon the system uses for the application. For at least one resolution,
             specify the path to a PNG file included in the AIR package. Optional. -->
        <!-- <icon>
            <image16x16></image16x16>
            <image32x32></image32x32>
            <image48x48></image48x48>
            <image128x128></image128x128>
        </icon> -->
        <!-- Whether the application handles the update when a user double-clicks an update version
        of the AIR file (true), or the default AIR application installer handles the update (false).
        Optional. Default false. -->
        <customUpdateUI>true</customUpdateUI>
        <!-- Whether the application can be launched when the user clicks a link in a web browser.
        Optional. Default false. -->
        <!-- <allowBrowserInvocation></allowBrowserInvocation> -->
        <!-- Listing of file types for which the application can register. Optional. -->
        <!-- <fileTypes> -->
            <!-- Defines one file type. Optional. -->
            <!-- <fileType> -->
                <!-- The name that the system displays for the registered file type. Required. -->
                <!-- <name></name> -->
                <!-- The extension to register. Required. -->
                <!-- <extension></extension> -->
                <!-- The description of the file type. Optional. -->
                <!-- <description></description> -->
                <!-- The MIME content type. -->
                <!-- <contentType></contentType> -->
                <!-- The icon to display for the file type. Optional. -->
                <!-- <icon>
                    <image16x16></image16x16>
                    <image32x32></image32x32>
                    <image48x48></image48x48>
                    <image128x128></image128x128>
                </icon> -->
            <!-- </fileType> -->
        <!-- </fileTypes> -->
        <!-- iPhone/iPad -specific capabilities -->
        <!-- <iPhone> -->
            <!-- A list of plist key/value pairs to be added to the application Info.plist -->
            <!-- <InfoAdditions>
                <![CDATA[
                    <key>UIDeviceFamily</key>
                    <array>
                        <string>1</string>
                        <string>2</string>
                    </array>
                    <key>UIStatusBarStyle</key>
                    <string>UIStatusBarStyleBlackOpaque</string>
                    <key>UIRequiresPersistentWiFi</key>
                    <string>YES</string>
                ]]>
            </InfoAdditions> -->
        <!-- </iPhone> -->
    </application>

  • Air 2.6 Ubuntu Native Installer Problem

    Hi, i have a problem creating and native deb installer with Adobe 2.6 with Ubuntu 10.10, when i run this code on terminal:
    /home/victor/Flex_SDK/Flex_SDK_4.5.0/bin/adt -package -storetype pkcs12 -keystore /home/victor/Certificado.p12 -storepass secret -target native /home/victor/Desktop/TestNativeApp.deb TestNativeApp-app.xml TestNativeApp.swf
    This code creates an deb native installer without any errors or warnings, but when i try to execute this file, the Ubuntu Software Center says "Internal Error the file /home/victor/Desktop/TestNativeApp.deb could not be openned", but when i try to run with dpkg -i /home/victor/Desktop/TestNativeApp.deb the file installs well.
    What am i doing wrong?.
    Thanks for yours responses.

    I've got the same issue.  Ubuntu Software Center won't open it.
    When I run it with dpkg like you do, I get a version number error, though:
    parsing file '/var/lib/dpkg/tmp.ci/control' near line 2 package 'mypackage':
    error in Version string 'v1': version number does not start with digit
    Errors were encountered while processing:
    I assume this version is pulled from the air XML file, so I'm going to change that and make it only numbers and see if that fixes it.

  • Can't package native installer on Linux with Flex SDK 4.5 : Invalid AIR file

    Hi,
    We've moved our application to compile against the 4.5 SDK.
    We're compiling it with Flash Builder (on mac) into an air file and as our application is using NativeProcess API, we're packaging it on each platform into a native installer with the following command (linux example) : adt -package -target native app.deb app.air
    We think we fall into the same issue as http://forums.adobe.com/message/3271944#3271944 but for the 4.5 DSK.
    On Linux it used to work with the following environment (env1):
    - Ubuntu 10.10
    - Java Sun 1.6.0_24
    - Flex SDK 4.1.0.16076 + Adobe Air SDK 2.5.0
    It stops to work when we upgrade to the new Flex SDK (env2):
    - Ubuntu 10.10
    - Java Sun 1.6.0_24
    - Flex SDK 4.5.0.20967 (with the default embeded Adobe Air SDK 2.6)
    The faut message is "Invalid AIR file" and nothing is logged in the log file (/home/<username>/.appdata/Adobe/AIR/Logs/Install.log).
    1) The .air file is installing correctly on env2 (without the support of the NativeProcess as expected)
    2) We also tried to compile the project directly on env2 :
    amxml app.mxml
    adt -package -storetype pkcs12 -keystore cert.p12 app.air app-app.xml air.swf
    The .air file is installing fine but the packaging into a native process fails in the same way...
    3) We tried to package a native installer of our .air file on env1 and it works!!! (the installed application seems to work fine also on env2!!!)
    Are we missing something or does it seems to be a bug of the Flex SDK 4.5?
    Are there some restrictions to package a native installer with the Flex SDK 4.1 a air app build with the Flex SDK 4.5 ?
    Thanks in advance,
    Mich

    Hi,
    Finally we figure out how to solve the issue.
    The packaging into native .deb installer fails as explain above because with the hole Flex SDK 4.5 (adt -version told 2.6.0.1920).
    The packaging is successfull if only Air SDK 2.6 is install.
    What is strange that both adt seems to be the same "2.6.0.1920" (found with "adt -version").
    Can someone from the Adobe dev team explain it?
    I suppose as the Flex SDK is not available for the Linux platform, the download only contains the Air SDK for Windows and Mac OS as opposed to the specific download of the Air SDK for te Linux platform...
    Thanks,
    Mich

  • Package into a native installer fails on Linux (Flex SDK 4.5) : "Invalid AIR file"

    Hi,
    We've moved our application to compile against the 4.5 SDK.
    We're compiling it with Flash Builder (on mac) into an air file and as our application is using NativeProcess API, we're packaging it on each platform into a native installer with the following command (linux example) : adt -package -target native app.deb app.air
    We think we fall into the same issue ashttp://forums.adobe.com/message/3271944#3271944 but for the 4.5 DSK.
    On Linux it used to work with the following environment (env1):
    - Ubuntu 10.10
    - Java Sun 1.6.0_24
    - Flex SDK 4.1.0.16076 + Adobe Air SDK 2.5.0
    It stops to work when we upgrade to the new Flex SDK (env2):
    - Ubuntu 10.10
    - Java Sun 1.6.0_24
    - Flex SDK 4.5.0.20967 (with the default embeded Adobe Air SDK 2.6)
    The faut message is "Invalid AIR file" and nothing is logged in the log file (/home/<username>/.appdata/Adobe/AIR/Logs/Install.log).
    1) The .air file is installing correctly on env2 (without the support of the NativeProcess as expected)
    2) We also tried to compile the project directly on env2 :
    amxml app.mxml
    adt -package -storetype pkcs12 -keystore cert.p12 app.air app-app.xml air.swf
    The .air file is installing fine but the packaging into a native process fails in the same way...
    3) We tried to package a native installer of our .air file on env1 and it works!!! (the installed application seems to work fine also on env2!!!)
    Are we missing something or does it seems to be a bug of the Flex SDK 4.5?
    Are there some restrictions to package a native installer with the Flex SDK 4.1 a air app build with the Flex SDK 4.5 ?
    Thanks in advance,
    Mich

    Hi,
    Finally we figure out how to solve the issue.
    The packaging into native .deb installer fails as explain above because with the hole Flex SDK 4.5 (adt -version told 2.6.0.1920).
    The packaging is successfull if only Air SDK 2.6 is install.
    What is strange that both adt seems to be the same "2.6.0.1920" (found with "adt -version").
    Can someone from the Adobe dev team explain it?
    I suppose as the Flex SDK is not available for the Linux platform, the download only contains the Air SDK for Windows and Mac OS as opposed to the specific download of the Air SDK for te Linux platform...
    Thanks,
    Mich

  • Can't install native installer for Mac OS

    I can't install any dmg that compiled with adt native api.
    For example at this article
    http://www.adobe.com/devnet/air/flex/quickstart/interacting_with_native_process.html
    Installer says:
    "This application requires an update to Adobe AIR that is not available  for your system.
    Please view the system requirements for  Adobe AIR and update your system accordingly."
    I have last  stable air runtime: 2.0.2
    Mac OS 10.5.8

    I had the same problem, i find out the following solution, that worked out:
    this may happen if you are using a custom keyboard layout. delete the file /Users/username/Library/Preferences/ByHost/com.apple.HIToolbox.* and log out/in. try software update again.

  • How to migrate certificate for a native installer

    Hello,
    We have a native AIR app that uses some native files, so it needs to be packaged using "adt -package -target native [files...]" command and cannot be created as an AIRI file.
    We include the SWF file, the app description XML and the required native files into the installer, and we also include our code signing certificate into this command line, and everything worked great.
    Recently our code signing certificate expired, and we released an update with a new certificate.
    However on the machines where our application had been installed previously, installation fails with the following error.
    The certificate of the installed app fails to match either the signature or migration signature of the AIR file
    It turns out that AIR framework expects a migration signature for applications that had been installed before and changed certificate.
    The problem is that "adt -migrate" command expects an .AIR file, and fails to migrate a native installer (such as .EXE or .APP).
    How should we migrate a native installer? is there any option in adt to do this?
    Thank you in advance,
    Anatoly

    I know this is an older post, but it helped me find out how to make the migration procedure for native installer. I tried it with self signed certificate created by ADT tool and everything went fine.
    But now, we obtained a commercial AIR signing certificate from Thawte and the process failes in step 3) ADT saying
    'Certificate in PATH_TO_P12 could not be used to sign setup.msi' on Windows.
    On mac, it says that signing native installer on OSX is not supported, so I skipped the signing option in step 3) and it worked fine.
    I can skip the signing option on Windows as well and the process succeeds, but running the installer on machines with previous versions of application results in "Installer mis-configured' error message - the same error as if the migration process was not applied.
    I already contacted Thawte if it is a certificate issue, reply from them was 'AIR certificate can only sign .air applications'. But when I build a native application directly from FlashBuilder and sign it with the Thawte certificate the whole process seem to succeed. The application can be installed on machines without previous version of the application. Those who already have the older version get the 'Installer mis-configured' error message.
    I want to mark out again, that the same process but with a self signed certificate created with ADT, is successfull and the application can be installer as an update on machines with older version of the app. So I assume the workflow is correct.
    Any ideas? Or somebody having the same issue?
    Thanks

  • Native Installer on Mac - not for App Store

    I am trying to get an Air 3.1 native installer application to work for Mac under Mountain Lion's security model.  The app is not for distribution from the App store but it is downloaded from the web so it triggers Gatekeepers security on both the Installer and the App.
    I am signing the Air app with a standard (Not Apple Developer) certificate.  I then copy the contents of the Dmg (the installer) into a new directory and use my Apple Id to codesign the Installer.  This allows the installer to run but when it attempts to actually launch the app, Gatekeeper stops it saying that "the App is not from the App Store or an Authroized Developer"
    I tried to use the Apple Developer Cert in  Flash Builder but I get an error stating to check my cert or system time (see this: http://forums.adobe.com/message/4576223#4576223)
    I know I can use adt to create the base App (use the bundle option).  I can then sign the base app with the Developer Cert.  But how can I take that app and produce a native installer from it?
    Also, this app DOES NEED webkit resources - ifthat helps.
    Any insight would be greatly appreciated.

    Hi Barbara I´ve done what you suggested and I´m having the same problem. Its freezed. Is there any way I can download the update? I´m
    stuck with a Photoshop that doesnt work. Adobe says that they cant help without a serial number and apple doesnt let me update. This is the most bizarre I have lived in terms of software.

  • Adobe AIR Runtime Redistribution and Native Installer

    Will there be new instructions for Adobe AIR 2.0 Runtime Redistribution? In particular, I'm looking for instructions on how to use the runtime redistribution installer to perform a "side-car installation" of AIR 2 alongside an application that uses the NativeProcess API (and so must be built into a native installer instead of a .air file).
    Thanks!

    Thirded!
    On a test deployment using SCCM and the supplied Adobe AIR Runtime Installer files, we have managed to install our application with the 1.5.3 Air Framework with no major issues other than having to disable the Auto Update feature that doesnt really work in a corporate environment.  Everything was absolutely fine until the release of AIR 2.  Now, the test machines are prompted to install the updated Adobe Air 2 framework once a week, see an excerpt from an Adobe blog post below:
    "In addition, once a week AIR apps check to see if an AIR update is available, and if so, users are presented with the option to update to the most up‐to‐date version, helping to ensure that end users get the benefits of improved security and performance."
    That sounds great right?  Except my users (like many other corporate users) don't have Admin permissions on their machines (hence the use of SCCM), with the result being resultant error messages when a user attemptes to install the AIR framework update without the necessary permissions.
    All of the above would be fine if the Adobe AIR Runtime Installer files were updated to include the latest version of the runtime.  This of course hasn't been done yet - does anyone know when this may happen?  Can anyone help me with this or offer any advice?
    I hope the above makes sense and I would really appreciate any help or advice!
    Thanks!

  • AIR to auto upgrade to (native installer)

    Hello,
    The first application (released) was created in AIR now we want our exsting customer to auto upgrade to (native installer) to support few native process.
    The AIR check for the new upgrade avaiable and downloads the new (native installer) from the server but fails to run the installer.
    We have used NativeProcess to run the newly downloaded native installer. The logs shows that the nativeprocess is not supported.
    The supportedProfiles is set to <supportedProfiles>extendedDesktop desktop</supportedProfiles>.
    We had also tried using openWithDefaultApplication() function to run the nativeinstaller but with no success.
    Thanks

    Hello,
    The first application (released) was created in AIR now we want our exsting customer to auto upgrade to (native installer) to support few native process.
    The AIR check for the new upgrade avaiable and downloads the new (native installer) from the server but fails to run the installer.
    We have used NativeProcess to run the newly downloaded native installer. The logs shows that the nativeprocess is not supported.
    The supportedProfiles is set to <supportedProfiles>extendedDesktop desktop</supportedProfiles>.
    We had also tried using openWithDefaultApplication() function to run the nativeinstaller but with no success.
    Thanks

  • Adobe AIR Native installation + DRM issues.

    Hello Friends,
    We are looking at creating an application for a client whom is very concerned about piracy. They have a third party application which essentially injects DRM code into an windows exe. We created a demo air app which in turn was converted into an exe thanks to the native installer feature in Flash Builder for AIR and the third party worked fine by injecting after the DRM code.
    However we realized that in the installation directory we can find the swf for the app, so essentially if we install another Air app and swap the SWF's we can actually get the content and circumvent the DRM.
    I am wondering if there is anything we can do to prevent that (prevent the swf working within another AIR installation) and make it a little harder to crack.
    Any comments would be greatly appreciated.
    +LA
    www.lordalexworks.com

    I actually wanted to clarify a few things on this question in hope of still gettign an answer.
    Apparently MDM Zinc does a good of creating a exe that can then later be succesfuly injected with DRM requiring an activation code to be able to install the software. It seems the swf gets converted to something else therefore injecting the DRM is more effective.
    However I still want to do thid via AIR, the problem being is that the swf can be found in the installation and can be placed in another AIR app to circunvent the instalation code.
    Any thoughts are apreacited.
    +LA

  • Adobe AIR HTML/JS application and Windows Native Installer

    Hi,
    I am building an Adobe AIR application with HTML and Javascript and I would like to know how to make an Windows Native Installer.
    I am trying to build it with Flash Pro but it keeps returning the error 'Invalid SWF file'. At the application.xml file the <content> points to my index.html file. I don't use any SWF file. When I change this to point to the SWF it does build tha installer but the application loads the SWF.
    Is there any way to build a Windows Native Installer and the initial content be an HTML file?
    p.s. I tried to extract the files from the installer file and edit the application.xml there to point to the index.html. But I can't repackage the files to a valid air native installer.
    Thank you.

    Hi,
    Thank you for reporting this. The internal bug number for the issue is #2740755. The issue is currently under review and will be investigated by one of AIR team members.
    Regards,
    Catalin

  • AIR File Icon (For Native Installer)

    Hi,
    I am generating AIR application as native installer (.exe). I want to have a custom icon for my .exe file.
    I have specified the icons in application descriptor file as
    <icon>
                        <image16x16>icon...</image16x16>
                        <image32x32>icon...</image32x32>
                        <image48x48>icon...</image48x48>
                        <image57x57>icon...</image57x57>
                        <image72x72>icon...</image72x72>
                        <image114x114>icon...</image114x114>
                        <image128x128>icon...</image128x128>
              </icon>
    But this icon does not appear to be .exe file icon, It appears as application installed file icon. I want to have different icons for application installed icon (Application Icon) and separate icon for application installer (.air or .exe file custom icon)
    Kindly suggest any solution

    In this case you need to update installer icon manually via third-party app like freeware "ResourceHacker" http://www.angusj.com/resourcehacker/

Maybe you are looking for

  • Offset customer and vendor open items from different company codes

    Dear all, I would appreciate if you could help me with below issue: We have 2 company codes, these 2 company codes are under one company, i.e one group. When one company code (company code A) make vendor payment, the other company code (company code

  • Mvt type 103 and 105

    Dear all, I am doing GRN through 103 mvt type of 100 Qty. But at the time of 105 Mvt type qty found 90 that means 10 Qty still pending in block stock. How to process with 10 Qty in block stock which is due to vendor mistake. Please suggest exact proc

  • Problem in sending CSV as attachment in email

    Hi All, I'm working on ECC 5.0. I have an internal table with the data. I have to send this data as an attachment in an email. I sending a sample code which i used. When i try to open the attachment it is giving as warning popup 'File type is not rec

  • Iphone 5 sound

    The sound on my iphone dies when listening to music had to restart it twice within an hour can anybody help?

  • Mime attachments / forwarded messages

    It seems when I receive a forwarded message on any of my mail accounts using my iPhone, all I see is a mime icon that is unable to be clicked. I have checked to see if the message as been downloaded (they are). It appears to happen with aol messages