AIR SDK 1.1

After several hours of trying to synchronize my Flex SDK 3
environment with my new Air SDK 1.1 environment, I am able to get a
clean compile, install and test -- basically still following the
original "Getting Started" tutorial. When testing with adl, the
window background fails to honor the 85% opacity setting that it
has always had -- it's opaque. When the application comes up
running under the AIR runtime -- same behavior.
I see that some of the changes in 1.1 have something to do
with the handling of 'native window transparency', but I did not
see any FAQ or Release Note item stating that the external controls
through either the api or the xml configuration file require
new/different settings. Is there a document somewhere describing
what the new settings are for achieving transparent windows?

There are no new settings for transparent windows; they work
as before.

Similar Messages

How to install latest AIR SDK (13 or 14) in Flash Pro CS6?

Hi, I'm using Adobe Flash Pro CS6 on Windows 7 64-bit and I wanted to add latest Adobe AIR SDK, either 13 or 14, but non of them is seen as a valid SDK by Flash.
I've tried downloading two possible SDKs (SDK & compiler and SDK without compiler) from here: Download Adobe AIR SDK (version 13) and here http://labs.adobe.com/downloads/air.html (version 14). Each time I copied the extracted SDK folder to my Flash CS6 folder where default 3.2 and 3.4 SDKs are located. After that I open Flash, then Help > Manage Air SDK, click on " + ", browse for the new folder, and all I get is "The selected folder does not contain a valid AIR SDK" warning message. It all looks the same with all four SDKs I downloaded!
Not long ago I added AIR 4.0 without any problems. What am I doing wrong? Is new SDK Flash CC only or what?

What are you naming the folder?
Just as a general tip, since many applications (Flash CS4, 5, 5.5, 6, CC) you can save some space by only putting the AIR SDK in one place. Since CS6 and CC have "Manage AIR SDK" in their settings you no longer need to locate that folder like 5.5 which requires you to overlay the AIR 2.6 folder. So save some space and put it anywhere out of the way, out of the Flash folder. I have multiple drives and I have lots of SDKs installed at root on my E:\ (E:\SDK\AIR, E:\SDK\JDK, E:\SDK\Android, etc). I then just go in the help panel like you do and point CS6 and CC to E:\SDK\AIR and they work perfectly fine with the latest SDK released recently.
Are you updating Flash Player to 13 as well?
Last, do not download the Flex version for Flash. Flex is for Flash Builder if you intend on using Flex (it is different than Flash).
Do not get this:
You want the SDK from the big orange buttons above this warning.

Use AIR sdk in a panel

Hello,
I'd love to be able to access the file system with a panel. I've read that after cs5 panels use the AIR framework, but I'm not entirely sure how to use it. I'm currently using the flex 3.4.0 sdk which was required for CS4. How can I go about upgrading to the AIR sdk?
Thanks,
Cameron

Hi Tom,
Thanks for getting back to me. My project doesn't have a .actionScriptProperties file (which surprises me, as I feel it used to have one). Instead I have a .flexProperties file. I tried adding that bit in there but when I try to do something like `import flash.filesystem.*` it doesn't autofill.
1. Will what you mentioned work in flexProperties?
2. Do I need a lib of some sort to work with AIR?

Local_nostrip.arm-air.txt is missing in AIR SDK 16

I merged Flex SDK 4.6.0 and AIR SDK 16.0.0.272 and use it in the Flash Builder 4.6.
I downloaded AIR SDK 16.0.0.272 in the following :
( Because I use Flash Builder, I downloaded the original AIR SDK without the new compiler. )
http://www.adobe.com/devnet/air/air-sdk-download.html
I added ANE files to my app and entered iOS SDK path in the properties window of project.
* iOS SDK path : /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPh oneOS8.1.sdk/
When I build my app, the following error occurred :
After I read the error message, I check whether local_nostrip.arm-air.txt is in the specified location.
I found local_nostrip.arm-air.txt is missing in the sdk - it does not exist in the {pathtosdk}/lib/aot/lib/.
In the AIR SDK 15, local_nostrip.arm-air.txt file is in the {pathtosdk}/lib/aot/lib/.
Can I use local_nostrip.arm-air.txt of the AIR 15 instead?
Does anybody know?

I am using Flash Builder 4.6.
I can't found where "run configuration" and "custom launch" is.

How to setup Flex SDK with latest AIR SDK?

Now the latest AIRSDK web page has a small link at the bottom for Flex users and it states that Flex users should take the SDK version without the compiler. BUT....
the http://helpx.adobe.com/flash-builder/kb/overlay-air-sdk-flash-builder.html page says to download the SDK from
http://labs.adobe.com/downloads/asc2.html
but this page now redirects to:
http://helpx.adobe.com/air/kb/archived-air-sdk-version.html
which contains a large list of archived SDK's. So that help page never really says which version of the SDK to use - with or without the compiler. But other forum posts have implied its suppose to be the one with the compiler.
Now since we're overlaying the ...plugins\com.adobe.flash.compiler_4.7.0.349722\AIRSDK folder that would make sense.
But now there's a second overlay instructions page at:
http://helpx.adobe.com/x-productkb/multi/how-overlay-air-sdk-flex-sdk.html
with different instructions.
So my questions are:
   Which overlay instructions are we really suppose to use?
   Which version of the AIR SDK (with or with-out compiler) are we suppose to use?
   What does the Flex Library Project properties -> Flex Library Compiler -> 'Include Adobe AIR libraries' checkbox really do?
        If I've followed the (first) overlay instructions above, does this checkbox now mean I'm using the overlaid AIR SDK 3.6
        with the current Flex SDK I've chosen?
        What if I'm using the Apache Flex 4.9.1 SDK? Will the AIR SDK 3.6 overlay that?
            (Doesn't Apache Flex have AIR 3.4 embedded - will this confuse Flash Builder 4.7 ?)
Is it just me, or is this just getting more and more confusing? Can we perhaps get a AIR SDK combo box to go beside the Flex combo box and when we check the 'Include Adobe AIR libraries' then we can select the AIR SDK we want? And get a 'configure AIR SDKs...' link too? Then perhaps we can get completely away from overlays and all this merged SDK nonsense. I've had nothing but problems with it.
The real reason I need all this info is because I'm trying to use Flash Builder 4.7 to build an Android ANE and I'm having a devil of a time just trying to find my resources. When I use context.getResourceID() I'm not getting the correct resources - and after reviewing other posts here I came to the conclusion that it might be due to bugs in older AIR SDK's. So really, at the moment I could care less about the latest Flex SDK, I just need to know I'm working from the latest AIR SDK.
Thanks in advance.

If you are not using Flash Builder go here: http://www.adobe.com/devnet/air/air-sdk-download.html
At the bottom it says:
Note : Flex users will need to download the original AIR SDK without the new compiler. Mac Windows.
Download the proper one for your OS and then extract it over your existing Flex SDK directory.
EDIT: Just read your post again and noticed you mentioned Flash Builder. In that case you want to follow these directions: http://helpx.adobe.com/flash-builder/kb/overlay-air-sdk-flash-builder.html and grab the version with the compiler at http://www.adobe.com/devnet/air/air-sdk-download.html

Installing and using Adobe Air SDK 2.5 with Flash Professional CS4

Hi,
I am trying to install the Air SDK 2.5 with Flash Professional CS4 with the intention of creating a program to use Actionscript 3 to communicate with the UDP interface using datagrams. (The server is the IL2 device link interface) As I am very new to this development environment I was wondering if anyone could answer a few questions.
1) Can I use datagram sockets with Air 2.5 with Actionscript 3 and Flash CS4?
2) Is there special procedure for installing the AIR SDK 2.5 or do I use the instructions layout in "How to Overlay the Adobe Air 2 SDK for Use with Flash Professional - Flash professional CS4"?
3) If I do use those instructions, when I edit the namespace for my application do I set it to 2.0 or 2.5?
4) As a stepping stone to building my program I was trying to try to build the Actionscript 3 DatagramSocketExample program that is published by Adobe. Unfortunately I am getting a '1046: Type was not found or was not a compile-time constant: DatagramSocketDataEvent'.
Is there a step by step tutorial on how to get the example code up and running?
Thankyou for your time and patience with my noob questions
Ian

This was part of the AIR 2.0 beta release note, but I used this for 2.5 and it works nice.
You can try it too an make sure you use 2.5 wherever the not says 2.0beta2.
Goodluck.
How to Update Flash CS4 to Use the AIR 2 Beta SDK
If you use Flash CS4 Professional to build Adobe AIR applications, please follow the instructions below to manually update the version of the AIR SDK to use version 2.0.
Update Flash CS4 Professional to version 10.0.2 at http://www.adobe.com/support/flash/downloads.html or select "Help > Updates... " from within Flash CS4.
Quit Flash CS4 Professional if it is open.
Navigate to the Flash CS4 installation folder. The default location on Windows is "C:\Program Files\Adobe\Adobe Flash CS4\" and on Mac OS "/Applications/Adobe Flash CS4/"
Within the "Adobe Flash CS4" folder you should see a folder called "AIK1.5". If this folder is not present repeat step #1.
Rename the folder "AIK1.5" to "AIK1.5 OLD" or delete it if you do not need to save a copy of it.
Make a new folder called "AIK1.5"
Download the Adobe AIR 2 SDK from the labs website and uncompress the contents of the folder to the new "AIK1.5" folder you just created.
Copy the "airglobal.swc" file located within the "Adobe Flash CS4/AIK1.5/frameworks/libs/air/" folder into the "Adobe Flash CS4/Common/Configuration/ActionScript 3.0/AIR1.5/" folder.
Flash CS4 is now configured to use the AIR 2 beta 2 SDK.
In order to take advantage of the new AIR 2 beta 2 features, you will need to update your application descriptor file to use the "2.0beta2" namespace.

AIR SDK 17 (BETA) is not working with Flash CS6

Hi,
The latest AIR SDK 17 is not working with Flash CS6.
I tried to publish and install an iOS app to my connected device via USB but I always get an error "Check if iTunes is installed".
The latest stable AIR SDK 16 is working fine, and yes, iTunes is installed on my PC.
DETAILS:
- Flash CS6
- AIR SDK 17
- System: Windows 8,1
- iPodTouch with iOS 8.1
REPRODUCE:
Open new AIR iOS template and publish/install it to a USB connected iOS 8.1 device.
Anyone else got that error?

I was getting this intermittently. Not a super problem. A remove and install in iTunes gets it loaded (after you tell ITunes where it is).

How to install AIR SDK 15 on my iMac

Hi everyone... I built my iOS app on Flash cs6 (with the latest AIR SDK 15) on my windows computer, but now have access to a Mac. The problem though is that the Flash cs6 on the mac is running AIR 3.2 and I have downloaded the latest AIR SDK 15 for Mac but I don't know how to install it. Can anyone help me?

I assume its the same as installing any other AIR SDK's. you go to Help >>> Managed Air SDK >>> click on the + sign on the top right >>> navigate to the AIR SDK 15 folder and then done!
I'm in the same situation as you are but I haven't received my imac YET. so I will let you know once I have done this myself or you can share your experience with us?

How to Update Adobe Air sdk in Flex sdk ?

Hi Guys,
I am currently using Flex sdk 3.0 to develop Air application and right now there is a need to use new Air 2.0 features in my application. I have downloaded the Air sdk from adobe site but couldn’t figure out how to update that sdk in my Flex sdk.
Please tell me procedure to update the air sdk.
Thanks,
Mahesh

Does this help?
http://kb2.adobe.com/cps/495/cpsid_49532.html

Error Upgrading to AIR SDK 3.5 in FlashBuilder 4.7

Whenever I try to upgrade to AIR SDK 3.5 distribution (by overlying it over AIRSDK) using the following instructions I get an exception (below) when I try to start up FlashBuilder 4.7.
Am I missing a step? A SDK upgrade tool would be a nice feature.
Installation Instructions
Flash Builder 4.7
Note:
Flash Builder 4.7 Beta 2 includes AIR 3.4 SDK with ASC 2.0 Preview 3.
All Flash Builder 4.7 ActionScript projects now use ASC 2.0 by default.
To manually apply a later preview of AIR SDK with ASC 2.0 to a Flash Builder 4.7 Beta 2 release, unzip the AIR SDK with ASC 2.0 distribution
over the captive version of the AIR SDK in Flash Builder 4.7.
The default locations of the AIR SDK in FB 4.7 Beta 2 are outlined below:
Mac OSX: /Applications/Adobe Flash Builder 4.7/eclipse/plugins/com.adobe.flash.compiler_4.7.0.348297/AIRSDK
Windows 7 (64-Bit): C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64
Bit)\eclipse\plugins\com.adobe.flash.compiler_4.7.0.348297\AIRSDK
Note: The distribution of the AIR SDK with ASC 2.0 is for pure-ActionScript development only. It should not be combined with an existing Flex
SDK. To update a Flex SDK with a later version of the AIR SDK, use a standard distribution that does not include ASC 2.0. See
http://www.adobe.com/devnet/air/air-sdk-download.html.
On Mac OSX, be mindful that copy operations clobber the contents of the destination - you can merge folders using the ditto command o
org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundExcep tion: An error occurred while automatically activating bundle com.adobe.flexbuilder.as.editor (24).
          at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLa zyStarter.java:122)
          at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java :462)
          at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoade r.java:216)
          at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400)
          at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:476)
          at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
          at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
          at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.jav a:107)
          at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
          at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:345)
          at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:229)
          at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:120 7)
          at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(Re gistryStrategyOSGI.java:174)
          at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionR egistry.java:905)
          at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(Configu rationElement.java:243)
          at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(C onfigurationElementHandle.java:55)

Now that there are pre-combined distributions of AIR 3.5 SDK with ASC 2.0 Preview 4,
http://labs.adobe.com/technologies/asc2/
...you could avoid attempting an overlay. Try:
1. Closing FB 4.7.
2. Backing up FB 4.7's old AIRSDK folder by renaming it to something else.
3. Unzipping the pre-combined AIR 3.5 SDK with ASC 2.0 Preview 4 and putting it in place of the old AIRSDK folder with the exact name.
4. Starting FB 4.7.
FB 4.7 does plan to offer in-tool upgrades to official AIR SDK with ASC 2.0 distributions.

AIR SDK 3.6 Could not resolve component

I have Flash Builder 4.6 and the AIR SDK version is 3.5, Today i update the AIR SDK version to 3.6, However when i debug the appliction, the Flash Builder popup a error for "Could not resolve <s:ViewNavigatorApplication> to a component implementation." .
I have downloaded AIR SDK3.6 from here: http://www.adobe.com/devnet/air/air-sdk-download.html

Hi Jack,
Please download AIR SDK from a small note below on http://www.adobe.com/devnet/air/air-sdk-download.html
for flex users.
Note : Flex users will need to download the original AIR SDK without the new compiler.
Please let us know if this fixes your issue.
Thanks,
Krati

Error "Could not resolve s:ViewNavigatorApplication to a component implementation...", after overlaying with AIR SDK 13.0

Just installed FB 4.7, overlayed with AIR SDK 13.0, started FlexMobileProject and I get this error "Could not resolve <s:ViewNavigatorApplication> to a component implementation...", which I can't get rid of. Tried 3-4 times, error stays.
I overwrote the Flex sdk 4.6.0 with Air SDK 13.0.
Is this a bug? Please help.

Thanks for the reply. I tried changing to the airmobile-config.xml but then I got the same error with a different componenet.
Error: Could not resolve <r:QContainer> to a component implementation. <r:QContainer id="d">
Could this related to a missing SWC from my build path do you think?

Why reloading pure asset SWF with AIR sdk 3.6+ doesn't work?

Hi, I posted this in the AIR beta channel, but I think it suits better here... I'm sorry for double posting.
Hi,
I have a game targeting iOS using AIR sdk that needs to load many swf assets from the disk (packaged with the game). When using AIR sdk 3.5, everything runs just fine. When upgrading the sdk to 3.6 or later (-swf-version=19, 20, 21), we ran into the following problems:
1) The packaging time (making the ipa file for iOS) passes from 15 minutes to 40+ minutes.
2) The game can't load any swf twice (ie. reload a swf).
The first problem is not a big deal. We only have to wait a little bit more. Our guess is that is has to do with new feature introduced by the sdk 3.6, which will go through all packaged secondary swfs and remove the code from it, and since we have lot of swf assets, it takes more time.
The second problem is way more serious, as I have to be able to reload assets according to player's action. Since we have a ton of assets, I can't keep them all in the memory as we could quickly run out of memory.
I know that there's a documented limitation of sdk 3.6 which states:
In AIR apps on iOS running in AOT mode there is a problem when a SWF is reloaded. Therefore reloading a SWF will not be allowed for AIR apps for iOS in AOT mode and attempting to do so will result in following error:
Error 3764: Reloading a SWF is not supported on this operating system
It also says that "Reloading of pure asset SWFs will work with AIR 3.7". However, that's not true, since all my assets are pure asset SWF without any code inside. It won't work, even with AIR 3.8.
While searching on the internet, I came across a forum post that says that the only way to know if a swf is a pure asset swf, is by using swfdump.exe, and searching for the DoABC2 tag. I did it, and effectively, DoABC2 tag was there, but empty.
So my first observation is that:
- Pure asset SWF file containing empty DoABC2 tag can be reloaded using AIR SDK 3.5
- Pure asset SWF file containing empty DoABC2 tag can't be reloaded using AIR SDK 3.6+
It seems to me that AIR SDK 3.6+ doesn't care if the tag is empty or not. If it is there, then it's not ok.
Then I wanted to know why my SWFs have this empty tag. After lot of tests, it turns out that it is because I am using jsfl to automate the export of assets from a FLA file. And there comes my second observation:
- When exporting a swf without code from Flash IDE (Ctrl+Alt+Shift+S), there's no empty DoABC2 tag.
- When exporting a swf from the Flash IDE's library (right click on the library Movieclip -> Export Flash movie...), empty DoABC2 tag is automatically inserted.
Unfortunately, my jsfl script uses thee same Library export functionality, and it produces the same "contaminated" swf. Why doesn't it produce the same SWF from both ways of export? I have no idea.
In the perfect world, the AIR SDK would not only look for the DoABC2 tag, but it should check whether if there's code inside. Also, Flash should use the same export process disregarding if it is being called from the IDE or the Library, and not inserting empty DoABC2 tag when there's no code.
As for now, I can't find any workaround to solve my problem. That means that I'm stuck with swf-version=18, and I can't benefit from all the cool features such as rectangle textures, new Context3DTextureFormat etc.
If anyone has a solution, or simply pointing out what I'm doing wrong here, please share it.
Thanks for reading.
Iojeirg

Hi makc3d,
Thanks for the response. After all that time I started losing hope.
I would not say that the abvious solution is to remove the tag. I think it should not be put there in the first place if there's no code at all. Moreover, this only happens when exporting a MC from the Library, and it works just fine when exporting normally (publish). It seems more like a bug than an expected behaviour.
Also, AIR should check for actual code in this tag instead of relying only on the tag itself.
Your solution is a nice workaround, and I will certainly try that out. But as I said, it will not fix the original bug, it will only patch it later on in the process.

Problem with the AIR SDK (OSX 10.6.8)

Hi (sorry for my poor english),
I would like to install the AIR SDK in order to do development of a little application.
The problem is when I want to use the "adl" command in order to try the installation, this is the result :
MJR-2:~ Woodgate$ adl
dyld: Library not loaded: /usr/lib/libxml2.2.dylib
Referenced from: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
Reason: Incompatible library version: AppKit requires version 10.0.0 or later, but libxml2.2.dylib provides version 9.0.0
Trace/BPT trap
MJR-2:~ Woodgate$
I don't why does it want to use the version 9...
MJR-2:~ Woodgate$ otool -L /usr/lib/libxml2.2.dylib
/usr/lib/libxml2.2.dylib:
    /usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current version 10.3.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.1)
    /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3)
    /usr/lib/libicucore.A.dylib (compatibility version 1.0.0, current version 40.0.0)
MJR-2:~ Woodgate$
I can't find any solution on the web about that and all my friends with the same configuration haven't any problem...
So I can't work today... does someone have an idea ?
Thank you very much.

This is an issue with the 1.0 version of the update. Apple pushed out a newer release this morning called 1.1:
http://support.apple.com/kb/DL1489

ANT build produces not working package with 3.5 AIR SDK

I used AIR SDK 3.1 and have ANT script to compile and package iPad(AdHoc for testing) application. I tried to switch to 3.5 SDK today but when I install *.ipa and launch on iPad it hangs at the spalsh screen.
I tried to make release build using Flash Builder UI and it worked. So the question is has anything changed in terms of packaging/compilation options?
Just in case attached my current ANT script:
<target name="Compilation" depends="Initialization">
     <mxmlc file="${main_class}" output="${swf_file}" locale="${LOCALE}" static-rsls="false" accessible="false" configname="airmobile"
                optimize="true" actionscript-file-encoding="UTF-8" keep-generated-actionscript="false" static-link-runtime-shared-libraries="true"
               debug="${debug_mode}" failonerror="true" fork="true" maxmemory="1024m">
          <source-path path-element="${class_path}"/>
          <load-config filename="${FLEX_HOME}/frameworks/airmobile-config.xml"/>
          <load-config filename="${config_file}"></load-config>
          <library-path dir="${lib_path}" includes="*.swc" append="true"/>
     </mxmlc>
</target>
<target name="Packaging" depends="Compilation">
      <java jar="${ADT}" fork="true" failonerror="true">
          <arg value="-package"/>
          <arg value="-target"/>
          <arg value="ipa-test"/>
          <arg value="-provisioning-profile"/>
          <arg value="${ios_provisioning}"/>
          <arg value="-storetype"/>
          <arg value="pkcs12"/>
          <arg value="-keystore"/>
          <arg value="${ios_keystore}"/>
          <arg value="-storepass"/>
          <arg value="${ios_pass}"/>
          <arg value="${ipa_file}"/>
          <arg value="${app_descriptor}"/>
          <arg value="${swf_file}"/>
          <arg value="-C" />
          <arg value="${class_path}"/>
          <arg value="assets/icons"/>
          <arg value="-C" />
          <arg value="${release_path}"/>
          <arg value="Default-Portrait.png"/>
     </java>
</target>
Thanks

You may want to try using the settings used by Flash Builder to package the application, more details of which can be found at:http://helpx.adobe.com/x-productkb/multi/compilation-results-flex-builder-flex.html
Update your ANT script with these, and try again.
Please get back and tell if it resolved the issue and what change you had to made in your ANT script.
Thanks,
Neha

Does the new AIR SDK support iOS 64-bit for Flex Developers?

I saw that the new AIR SDK(December 18, 2014) has supported iOS 64-bit, but it was only supported in the new compiler. See this:
Please note that support for creating universal IPA binaries will only be available in the new compiler. The legacy compiler is not (and will not be)
compatible with iOS 64-bit. Because of this, it will be removed with version 16 of the AIR SDK. To ensure that Adobe as well as third party tools
are able to work with this AIR SDK, the -useLegacyAOT option will continue to exist, but will be internally mapped to the new compiler.
AFAIK, the Flex uses the old compiler and AIR SDK for Flex Developers doesn't include ActionScript 2.0 Compiler. As a Flex developer, what shall I do?

Hi,
I guess, you might be packaging IPA on windows machine. Please try latest beta at http://labs.adobe.com/downloads/air.html which has iOS64 support on Windows machine as well.
Thanks
Govinda Gupta

AIR SDK 1.1

Similar Messages

Maybe you are looking for