1 Reply Latest reply on Aug 31, 2013 2:04 AM by Laurence MacNeill

    Upgrading AIR SDK to 3.8 in Flash Builder 4.7...

    Laurence MacNeill Level 1

      I am running Flash Builder 4.7 on a Mac, using OS X 10.7.5.


      I have downloaded the AIR SDK here: http://airdownload.adobe.com/air/mac/download/latest/AdobeAIRSDK.tbz2

      (The one WITHOUT the compiler, because that is the one that says it's Flex-Compatible.)


      I have followed all the instructions here: http://helpx.adobe.com/x-productkb/multi/how-overlay-air-sdk-flex-sdk.html


      I have changed the Application Descriptor on my ActionScript Mobile Project to this: http://ns.adobe.com/air/application/3.8 and it saves with no errors.


      Yet, every time I try to run the project, I get the following error:


      Error occurred while packaging the application: /Users/my_name/Documents/Adobe Flash Builder 4.7/my_project/bin-debug/my_project-app.xml: error 102: Invalid namespace http://ns.adobe.com/air/application/3.8


      So WTF is going on here?


      Thanks for any help you can give me.

      Laurence MacNeill

      Mableton, Georgia, USA

        • 1. Re: Upgrading AIR SDK to 3.8 in Flash Builder 4.7...
          Laurence MacNeill Level 1

          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...