Upgrading AIR app to Flashbuilder 4

I have an AIR 1.5 project that I'm trying to upgrade to Flash Builder 4. I import the project with the FB 4 IDE, but the menu option "Convert to Desktop/Adobe AIR project" is disabled. What am I missing?

Never mind -- I figured it out myself...
You have to download the version of the SDK *WITH* the compiler (here:http://www.adobe.com/devnet/air/air-sdk-download-mac.html ) and then delete the contents of the /Applications/Adobe Flash Builder 4.7/eclipse/plugins/com.adobe.flash.compiler_4.7.0.349722/AIRSDK folder and replace them with the contents of the AIRSDK_Compiler.tbz2 file you downloaded.
So -- to be clear you have to do BOTH of those things -- the thing I did in my first post with the Overlay, AND the thing I did in this post with the replacing the contents of the AIRSDK folder to make it work correctly...
I wish that when you Googled "How to upgrade AIR SDK in Flash Builder 4.7" it would return a single page with BOTH those sets of instructions on them.
Anyway, the problem is solved now...
L.

Similar Messages

  • Debugging iOS AIR app from FlashBuilder running under Windows/Paralells on a Mac

    On my Windows 7 workstation at work, I use FlashBuilder 4.6 to debug iPad apps all the time. The process is simple and reliable -- start the debugger which begins waiting for the app to notify it, move the app into iTunes, move it onto the iPad, launch the app, the app notifies the debugger that it is running, debugging works!
    At home I am running Windows 7 under the latest version of Parallels on my iMac running the latest version of Lion. I go through the same process: I connect my iPad (the same one from work) to the Windows VM, and Windows iTunes recognizes it and syncs files just fine. I can move a non-debugger version of the app onto the iPad and it runs just fine. However, when I start the debugger in FlashBuilder and then move the app onto the iPad and launch it, the app is not able to find the Flash Debugger. When it launches I just get a black screen for about 2 minutes, then I get a message asking me to enter the IP address of the Flash Debugger.
    There is an old help document indicating that this is due to the iPad and then debugger host computer not running on the same wifi, but I don't think it's relevant. My workstation at work isn't even connected to wifi.
    I will consider any advice. It's pretty important for me to get this up and running at home. I tried running directly under bootcamp, but both Microsoft and Adobe consider the bootcamp install to be a unique install of their products.
    Thanks!

    It turns out that the "help document indicating that this is due to the iPad and the debugger host computer not running on the same wifi" was spot on.  At my work environment, the wifi and the ethernet lan are on the same network.  I was mistakenly assuming that the iPad and the debugger were communicating via the USB cable, but this is not the case.  I think what happens is that FB embeds the ip address of its computer in the debuggable app.  The app then connects to FB at that IP address.
    My problem was that I had the Network Settings of my VM set to "Shared" under the Parallels hardware config set up.  My VM then had a 10.211.55.x ip address instead of a 196.196.0.x ip address, which is the range of addresses on my LAN.  Changing the setting to "Shared" fixed the problem.

  • Air apps won't work after upgrade to version 3

    After i updated air to its current 3 all my apps (air apps) will open but i get a pesky error message and after confirming they shut down. i tried downgrading, restoring from time machine and reseting preferences files, I know this is mostly Adobe issue, but can anyone give me a hint?

    I get the exact same thing. The status just keeps showing "Connecting..." and it never seems to connect. Oddly enough, I just updated to the new OS on my iMac at home and immediately after, I couldn't connect to mail from the computer. I had to manually download a component of the update and once I did that, mail worked just fine. Probably just an odd coincidence having nothing to do with the mail issues on the iPhone but I thought I'd mention it.

  • Adobe AIR app installation issue due to certificate problem on mac 10.9.5

    Im trying to upgrade and then reinstall an Adobe Air application but get the error message failing to install due to a certificate issue.
    The developer says the fix is to uninstall the app and install again but this also fails.
    Checked my machine clock - saved but that didnt work
    The adobe AIR uninstaller simply says I have the latest version? Cant seem to delete and reinstall although other adobe air apps work so I dont think this is the issue
    I have gone through the troubleshooting guide: Troubleshoot AIR installation | Mac OS but still have the issue?
    Any ideas would be great.

    I suspect your Mac OS install was an in place upgrade from an earlier version. This is something I would never even consider with a production machine.

  • Flash Builder 4.7 won't debug air app on Android devices  anymore

    Hi there,
    A strange thing happened today to my Flash Builer 4.7 installation on OS 10.8.5 : it suddenly refused installing and debugging AIR apps.
    At -the famous- 57% of compilation completion I can see the "installing app on device" message, but nothing happens then, and the one minute connection to app timeout is finally triggered.
    I had a look at other threads dealing with this problem here http://forums.adobe.com/thread/1154269 and here http://www.androidpolice.com/2013/02/12/new-android-4-2-2-feature-usb-debug-whitelist-prev ents-adb-savvy-thieves-from-stealing-your-data-in-some-situations/ and I downloaded the latets Android SDK and replaced a bunch of files into the /Applications/Adobe Flash Builder 4.6/sdks/4.6.0/lib/android/bin folder but nothing worked.
    The fun side of the issue is that yesterday it worked, and this morning it did not worked anymore, but I swear I did not ugraded Android on my phone nor I upgraded AIR SDK in FLash Builder or OS X. The Android phone is the same as usual, a Nexus 4 with Android 4.3, that I upgraded 1 month ago.
    I can't debug my Android app anymore, this drives me crazy, and I spent the day trying to find a solution.
    Do you guys had a similar problem ?

    My mistake...
    There was a typo into the XML application descriptor, that prevented the app to install properly on the device.
    Precisely, it wasn't a typo but raher a malformed <intent-filter> node. I launched adb tool from the console with adb install MyApp.apk command, and I saw this : Failure [INSTALL_PARSE_FAILED_MANIFEST_MALFORMED] in the terminal. From here it was easy to find the culprit.
    What would be cool is to have this feature inside the Flash Builder's Console panel.

  • Example working Flex AIR app for Android?

    I'm having trouble getting even the most basic AIR app working on Android. Here is the code:
    <?xml version="1.0" encoding="utf-8"?>
    <s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009"
                            xmlns:s="library://ns.adobe.com/flex/spark"
                            xmlns:mx="library://ns.adobe.com/flex/mx" xmlns:local="*"
                            width="600" height="600">
         <fx:Declarations>
             <!-- Place non-visual elements (e.g., services, value objects) here -->
         </fx:Declarations>
         <mx:Label text="Hello World"/>
    </s:WindowedApplication>
    It works fine running on  Windows in Flash Builder, obviously it's pretty simple. Here are the  commands I use to put it on a Samsung Galaxy Tab with Android 2.2.
    C:\Users\Ryan\Adobe  Flash Builder 4\Test2\bin-release>adt -package -storetype pkcs12  -keystore C:\Users\Ryan\STG-Android.pfx Test2.air Test2-app.xml  Test2.swf
    password:
    C:\Users\Ryan\Adobe Flash Builder 4\Test2\bin-release>adt -package  -target apk -storetype pkcs12 -keystore C:\Users\Ryan\STG-Android.pfx  Test2.apk Test2-app.xml Test2.swf
    password:
    test
    C:\Users\Ryan\Adobe Flash Builder 4\Test2\bin-release>adb install -r Test2.apk
    2286 KB/s (419172 bytes in 0.179s)
             pkg: /data/local/tmp/Test2.apk
    Success
    A Test2 app icon shows up on my Galaxy Tab  under Applications but when I run the app I just see a plain white  screen, I don't see the words "Hello World". Any ideas? Does anyone have  an example Flex AIR app that works on Android and can post the code so I  can try it on my Galaxy Tab? I know AIR is installed correctly on my  Galaxy because I installed an AIR app called South Park Avatar Creator  that I got from the market and it works fine.
    Thanks,
    Ryan
    P.S.  Here is the Test2-app.xml from my non-working project above in case it  helps. This is the default generated with a new Flex app in Flash  Builder 4 using the Flex 4.1.0 AIR 2.5 SDK but I uncommented the andoid  tags and set the visible tag to true.
    <?xml version="1.0" encoding="utf-8" standalone="no"?>
    <application xmlns="http://ns.adobe.com/air/application/2.5">
    <!-- 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.5
                 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>Test2</id>
        <!-- Used as the filename for the application. Required. -->
         <filename>Test2</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>Test2</name>
         <!-- A string value of the format  <0-999>.<0-999>.<0-999> that represents application  version which can be used to check for application upgrade.
         Values can also be 1-part or 2-part. It is not necessary to have a 3-part value.
         An updated version of application must have a versionNumber value  higher than the previous version. Required for namespace >= 2.5 .  -->
         <versionNumber>1.0.0</versionNumber>
         <!-- A string value (such as "v1", "2.5", or "Alpha 1") that  represents the version of the application, as it should be shown to  users. Optional. -->
         <!-- <versionLabel></versionLabel> -->
        <!-- 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></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></systemChrome> -->
            <!-- Whether the window is transparent. Only applicable when systemChrome is none. Optional. Default false. -->
             <!-- <transparent></transparent> -->
            <!-- Whether the window is initially visible. Optional. Default false. -->
             <visible>true</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> -->
        <!-- 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>
             <image36x36></image36x36>
             <image48x48></image48x48>
             <image72x72></image72x72>
             <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></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> -->
        <!-- Specify Android specific tags that get passed to AndroidManifest.xml file. -->
         <android>
             <manifestAdditions>
             <![CDATA[
                 <manifest android:installLocation="auto">
                     <uses-permission android:name="android.permission.INTERNET"/>
                     <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
                     <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
                     <uses-configuration android:reqFiveWayNav="true"/>
                     <supports-screens android:normalScreens="true"/>
                     <uses-feature android:required="true" android:name="android.hardware.touchscreen.multitouch"/>
                     <application android:enabled="true">
                         <activity android:excludeFromRecents="false">
                             <intent-filter>
                                 <action android:name="android.intent.action.MAIN"/>
                                 <category android:name="android.intent.category.LAUNCHER"/>
                             </intent-filter>
                         </activity>
                     </application>
                 </manifest>
             ]]>
             </manifestAdditions>
         </android>
         <!-- End of the schema for adding the android specific tags in AndroidManifest.xml file -->
    </application>

    <?xml version="1.0" encoding="utf-8"?>
    <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
                            xmlns:s="library://ns.adobe.com/flex/spark"
                            xmlns:mx="library://ns.adobe.com/flex/mx" xmlns:local="*"
                            width="600" height="600">
         <fx:Declarations>
             <!-- Place non-visual elements (e.g., services, value objects) here -->
         </fx:Declarations>
         <mx:Label text="Hello World"/>
    </s:Application>

  • AIR app won't debug or compile in FB 4.7

    So I have an AIR app that's been around quite awhile, going back to Flex Builder 3 and AIR 2.x...
    I've recently upgraded to Flash Builder 4.7 and I had no troubles with this app until today when I tried to run it in Debug mode -- I got some errors about namespace, did a Google search, found out that I needed to overlay the AIR SDK onto the Flex SDK (http://helpx.adobe.com/x-productkb/multi/how-overlay-air-sdk-flex-sdk.html) and I followed those instructions...
    Then when I re-loaded Flash Builder 4.7, I started getting stuff like "Could not resolve <mx:Module> to a component implementation."  So more Google searches, and I found out I needed to change the name-space from xmlns:mx="http://www.adobe.com/2006/mxml" to xmlns:mx="library://ns.adobe.com/flex/mx".  So fine, I did that...
    Now I'm getting "Unable to resolve MXML language version. Please specify the language namespace on the root document tag."  Can't find anything on this on Google -- well, nothing that works at any rate...  Found someone suggesting I add the fx: namespace, so I did: xmlns:fx="http://ns.adobe.com/mxml/2009"
    But when I add that namespace, I get "Cannot resolve <mx:Script> to a component implementation."
    WHAT IS GOING ON HERE?!  I just want to debug my AIR app like I used to be able to in Flash Builder 4.6.  HELP!
    Thanks,
    L.

    I changed <mx:Script> to <fx:Script> and now it seems to work fine...

  • HELP! - Can't update Adobe Air Apps - Application Install Error

    I have several Adobe Air Apps on my Mac OSX (10.9.4) MackBook Pro. They won't update due to the following Install Error.
    "The application cannot be installed due to a certificate problem. The certificate does not match the installed application certificate, does not support application upgrades, or is invalid. Please contact the application author."
    Following the above instructions, I've been contacting the authors of my Adobe Air Apps and they are telling me that it is not their problem. The Apps should simply update without difficulty.
    I searched the "Google" and found no fix other than uninstall and reinstall Adobe Air. Did this and the problem persists.
    If you can help me get beyond this issue and back to productivity, I'd be very appreciative.
    Thanks!
    David

    I had a similar problem when trying to install Zinio.air. I have made it all work out. What i did was remove Adobe Air 15 entirely from the Utiliites and Library/ accounts and preferences. I then downloaded Adobe Air 13 and installed and then clicked on Zinio .air and it all installed ok. I also had to temporarily change security settings from Apple approved to Anywhere. All functioning now.

  • No Adobe air app will run Only Flash Web browser....

    So I have re-installed Flash Builder So when I try and run a Adobe air app from the Flash Builder It brings up a prompt everytime saying - If the program is already running, close it before attempting to run. When I kill the Adobe Air debugger in the Task manager it pops up again saying If the program is already running, close it before attempting to run.
    After waiting a few moments from trying again I get a message: Unable to connect to the Application to fetch profile data. Please try profiling the application again.
    With Flash based - web browser apps - they run fine with no issue. How ever its only adobe air - desktop apps that run this way. This is the third time I have installed FB 4.5 on Windows 7 64 bit. last night it was all woprking fine I was able to debug my Flash Application and everything was working  - it has been doing this all day.

    I had the same issue suddenly today
    After hours of scratching my head - and just before re-installing FlashBuilder 4.5 - I found this suggestion
    I had an entry in the "mm.cfg" file:
    PreloadSWF=C:\Users\<USERNAME>\AppData\Roaming\Mozilla\Firefox\Profiles\9us94hs0.default\e xtensions\[email protected]\chrome\content\flashfirebug\flashfirebug.swf
    - I deleted the line and it now works
    ---- aaarrrrggghhh - wasted time
    thanks

  • AIR app seems to become unresponsive after sitting idle

    I built a straight forward info kiosk using Flash AS3 and used AIR to distribute it.
    The main items of the file:
    Straight ahead navigation with buttons that jump to frame markers.
    It has a 3 minute timer which returns it to the start page if it is not touched within that time limit.
    It has several screens that display web pages in a component web browser window.
    The problems I have hit: I have had the kiosk react as if the timer were set to 5 seconds and return to the home page too quickly. I have had buttons not work while others were working.
    But a restart of the AIR app corrects these issues and it works fine. It worked fine in my office however I did not test it in auto mode over several days of turning on and off and running all day.
    The system it is on is Windows 7. The system auto starts each morning, launches the app, then shuts down at days end.
    Could there be an issue with the app being up for 8 hours a day? Does it need to refresh itself?
    Any input is appreciated.
    Thanks

    Hello Chris,
    It is AIR 3.2. If I download 3.3 will Flash Pro recognize that and update to 3.3 or do I need to do something in Flash to utilize the upgrade when publishing as AIR?
    When you say "some sort of leak"? What would a leak be? I am not familiar with the term or what it implies?
    Thank you for the quick response. I will reply with the result in the next few days. I will have to load it up and let it run to see what happens.
    Thank you.

  • Bogus "Upgrade AIR Runtime" messages

    I am developing using Flash Builder 4.5.1 on Mac, debugging via USB on a Motorola Xoom.  Every time I run or debug my app on the device, I get the following dialog box:
    Upgrade AIR Runtime
    Your device has an older version of Adobe AIR installed. Would you like to upgrade it to Adobe AIR 3.1.0.4880?
    However, according to the Xoom application settings screen for AIR, version "3.1.0.488" is already installed.  Answering "yes" to the dialog has the same effect as answering "no" -- the app runs, but the next time I run it I get the same prompt.  Is there anyway to get Flash Builder to recognize that the attached device is really running the latest version?  I've tried uninstalling and reinstalling AIR, but the dialog persists.
    Thanks!

    There is a way, I did it before, but I am not sure how I did it
    Edit: Found the fix for me, close HTC sync

  • Dmg/exe vs adobe air app

    Happy Holidays everyone,
    I tried publishing a dmg and I assume the exe behavior would be the same.  I couldn't find a way to include files that were linked via the Loader() method.  If I were to publish this as an adobe AIR app the settings give me an option to add a list of files either one by one or by adding a folder.
    So the question becomes how can I get loaded swf's to be included in my published dmg (Macintosh) / exe (Windows) application file?
    Sorry to disturb the forumists on Christmas eve.
    Thanks for any help.
    -markerline

    Thanks kglad.  I'll take that answer as official.  But it's not inexpensive software on top of what I paid for my CS upgrade.  Don't know why this functionality isn't included in Flash to begin with.  I guess Adobe wants you to use AIR.  We'll see if I can raise the cash out of  =air=  to purchase mProjector.

  • Trouble installing .air app on mac

    For the sake of people searching, or if the image gets removed on day, here is the error message as text:
    "Sorry, an error has occured.  The application cannot be installed due to a certificate problem.  The certificate does not match the installed application certificate, does not support application upgrades, or is invalid.  Please contact the application author."
    I keep getting the above error when trying to install a new .air desktop file on a third-party Mac over which I have limited control.  The .air app does work on Windows 8.1.
    -Do you think it could be the AIR runtime (currently version 14, and am getting admin to update it to version 16)?  I built the app in AIR 16.
    -There is a previous version of the app, with a different certificate that is already installed.  Would this possibly cause the error?
    -Finally, I signed the app with a self-created certificate for development reasons.  Is that likely to be a problem, it didn't seem to be an issue last time I did this?
    Thank you.

    This was covered a couple of times just in the last week.
    Search for "runtime redistribute" or similar.

  • Can't open browser window from RoboHelp AIR app??!

    We've got a RoboHelp course that we're exporting as an AIR app using the  Packager and it works great. We've got an embedded flash file that  needs to open a website in a browser window, but, currently it will only  load the site in a new AIR window...any ideas??

    I'm having this same problem also, although you gave me one option in your reply.  I can't get the "Allow" button to work either. I upgraded to Adobe Reader 9.2, and then is when I noticed I couldn't bring up the websites that I usually could before.  I don't really know what you mean about "Stand Alone Option," but I will try to find out.  I also upgraded to Internet Explorer 8, but I'm not sure if this is when the problem started or when I went to Adobe Reader 9.2.
    I used to be able to get "Allow" to work if I opened the document in IE8 and not in AR 9.2, but now that won't even work. I did email the author of a PDF document I was in today in the hopes he would have the answer, but I'm not sure if I got his email address right, so time will tell on that issue.
    I have a "library" of PDF documents, so I would really like to get this problem fixed.  However, I've spent at least two hours on this issue, and I really don't think it has anything to do with Windows Vista incompatibility; I'm pretty sure it has something to do with Adobe Reader, but that doesn't help much given I have emailed support and, of course, have never received an answer.
    I do know there are a lot of people that are having this exact same problem, but no one has an answer to it.  I've tried to do research on this, but I have a lot of "to do" tasks I need to get done every day, so it's not like I have all the time in the world to try and fix this problem.
    I would appreciate hearing from you if you do ever figure this out. My email address is [email address deleted by host] should you find an answer to this very frustrating problem. Warmly, Corinne Larimore [signature deleted by host]

  • Air app misconfigured

    I have taken over an app project. it has a publisherID in the descriptor xml to maintain updates and the current Air version is 1.5.3. so obviously was originally built on previous version.
    The certificate expired, the tech team purchased a new re-issued certificate.
    Current setup Flash Builder 4 on Max OS 10.6.5.
    A) I have signed the application with the new certificate.
    Upon installation of the .air file I get:
    The message I get is:
    "Sorry, an error has occurred.
    The Application cannot be installed because the installer has been mis-
    configured.  Please contact the application author for assistance."
    B) I used the java ADT -migrate to apply the old certificate.
    This goes through seemingly ok.
    Upon installation of the new migrated .air file, I get:
    "Sorry, an error has occurred.
    The Application cannot be installed because the installer has been mis-
    configured.  Please contact the application author for assistance."
    I am told the exact same App worked perfectly (for upgrades) on the old certificate before its expiration.
    I have tried changing the version no to eliminate that.
    Any suggestions please?

    The Solution:
    A recent Flash Builder Update has been forced through by Adobe.  Which means you cannot publish to air versions prior to 2.0.
    The Flex 4.1 + this 'adobe update' implies that we must be using at least Adobe 2.0.
    I had:
    <application xmlns="http://ns.adobe.com/air/application/1.5.3">
    Solution is:
    Replace <application xmlns="http://ns.adobe.com/air/application/1.5.3">
    with <application xmlns="http://ns.adobe.com/air/application/2.0">
    Also just in case you need to know where the adt tool is on a mac:
    I found the java version most reliable:
    Assuming the air app is on the mac desktop and the old certificate has been added to the mac keystore (jus opening the certificate should be enough to add it to the keystore if you select the appropriate oprtion when asked)
    cd directory to:
    /Applications/Adobe Flash Builder 4/sdks/4.1.0/lib/
    Then run
    java -jar adt.jar -migrate -storetype pkcs12 -keystore <old certificate name>.p12
    "/Users/<username>/desktop/MyAirApp.air" "/Users/<username>/desktop/MyAirApp_migrated.air"
    You will be asked for the old certificate password, enter this and you are done
    P.S. Strike through text on this does not work properly
    P.P.S Marking my own question as answered when adding this reply does not work

Maybe you are looking for