Air

I created an application using Flash Professional cc (destination: air 14 for iOS), export .ipa file correctly, but when I try to load it with Application Loader found one error and a warning: 1) ERROR ITMS-9000: "Invalid Segment Alignment . The app binary at 'Caseificio Nonno Benito.app/ Caseificio Nonno Benito' does not have proper alignment segment. Try rebuilding the app with the latest Xcode version. "2) ITMS-9000 Warning: Missing 64-bit support. Starting february ....How can I fix these problems, please and very urgent, Thanks

Hi,I currently develop an ANE to use Bluetooth Low Energy on iOS, Android, Windows and Mac OS X.I can successfully use this ANE on iOS, Android and Windows, but when i try to compile final app on OS X, i get some application crash.It seems that we can use only 10.6 SDK (or something like that).Is there a way to use OS X 10.7 (or better 10.10 SDK) when compiling ANE and final Application ?Maybe i'm doing something wrong...Please any help is welcome.Thanks in advance.

I want to know if I've understood this right, and what the implications are.I've come to understand that certain Android devices, specifically those with x86 processors (such as Samsung Tab 3) cannot run apps built with AIR, or at least will run them extremely slowly to the point of being useless.First of all, is this true?Secondly, what are the implications? If a segment of users in Google Play cannot properly run the apps we build for Android, this is almost an argument for not building Android apps at all, since those users will give extremely poor reviews - and in any case, we will end up with a percentage of Android users being extremely dissatisfied with the app and complaining.Can anyone tell me if I understand the situation correctly, and what is the current assessment of the seriousness of the problem?

With AIR 16.0.0.245 app running on Android devices, I'm having a problem getting meaningful touchPointID values for single taps. The value is always reported as 0. This makes it impossible for me to track if a given TouchEvent is actually the same TouchEvent occurring in a different phase.When I run the same code on iOS, subsequent touches increase their ID with each tap, which is as expected. I am getting the exact same positive results on both platforms from Multitouch.supportedGestures, Multitouch.supportsGestureEvents, and Multitouch.supportsTouchEvents. Multitouch.inputMode also reports touchPoint.This is crippling my project right now.

HI , I am getting the following error while publishing app in flash cs6.I am using all latest version of ANE files .Please help meRegards,M.narasimhulu

Replicated using this environment:iPad Version: 8.1 (12B410)Adobe flash Pro: CS6 (12.0.2.529)Adobe Air SDK: 15.0FLA: blank white no AS no stage elementsApplied iOS ad-hoc distribution Cert and provisioning files to publish settings and successfully published:Application installs successfully using:adt -installApp -platform ios -package PATH_TO.ipaclicked installed app on device and only got a black screensame exact setup and steps on iOS 7 gave us a successful test with our test app launch

The whole reason for having SWFs is so that you can use the graphics, usually more than once. If you are writing a game, for example, and you have a SWF to be a enemy character graphic, you are most likely going to have more than one of that character in a level, and it is useless if it breaks your app to do something so basic. There are really countless situations where you would want to use a SWF graphic more than once, just like you would use a PNG or JPG more than once.It now saysError #3764: Reloading a SWF is not supported on this operating system.whenever you try to use a SWF more than once on iOS.The release notes say that this foundational, basic functionality of AIR was dropped because there 'was a problem with it'. What is this 'problem' and why is it worth dropping such a core and basic functionality of the platform? It is strange that the notes simply say this is dropped, but don't say what solution you are supposed to use instead, or give any real explanation as to why it

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?

Hello,I recently purchased a new Lenovo Thinkpad laptop running Windows 7 and when I attempt to install my school review program, I get this error message:"The application could not be installed because the installer file is damaged. Try obtaining a new installer file from the application author."I have uninstalled and reinstalled all adobe software on my computer several times while restarting it between installations and still no luck. I do not know if maybe there is a different version of Adobe air that I need to install? I tried installing the software included on the CD as well as the newest version from the Adobe website. Any help would be greatly appreciated!- Bryan

import flash.filesystem.*;import flash.desktop.NativeProcess;import flash.desktop.NativeProcessStartupInfo;var file:File = new File("C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe");var nativeProcessStartupInfo:NativeProcessStartupInfo = new NativeProcessStartupInfo();nativeProcessStartupInfo.executable = file;var args:Vector.<String> = new Vector.<String>();args.push("c:\\test\\sendTest.ps1");nativeProcessStartupInfo.arguments = args;var process:NativeProcess = new NativeProcess();process.start(nativeProcessStartupInfo);Trying to get Powershell to run sendTest.ps1 in the c:\test folder. I get no error, or anything for that matter.If I issue this at the command prompt:powershell c:\test\sendTest.ps1It works fine. But I just can't get the syntax correct to run it from AIR. Anyone tell me what I'm doing wrong?

Geolocation services not works at all on iOS devices if application compile using AIR SDK 16.0.0.250 for Windows.

Hi, Since iOS update 8.1.1 our Air Applications stopped working. (also the ones installed on the ipads)I tried making a rly simple Hello World Air App , in Flash Editor it all Works, i upload to our site, (adhoc deployment).. it downloads and istalls fine, but when it opens it just shows black screen.I'm on Windows.

Hi guys!I just switched to AIR SDK 16.0.0.250. Everything was fine except one very strange problem with Default images on iOS devices.My app runs in landscape mode. In my app I have default images that are shown during application loading phase.When app start, first I see Default image properly, that for a very short period of time I see Default image rotated 90 degree and scaled to fill the screen and then it disappears and application is get loaded.Here is a video that illustrates the problem: http://youtu.be/Ry1l1v7dQssThat is very strange, so I want to know if anybody else knows how to handle this issue and what could the source of it? Some info that might help: Application descriptor:<initialWindow>    <content>SWF file name is set automatically at compile time</content>    <visible>true</visible>    <aspectRatio>landscape</aspectRatio>    <autoOrients>true</autoOrients&g

Hi, since migrating to the "AIR 16.0.0.250" beta I've noticed that my iPhone 5s displays the "Default-568h@2x.png" launch image properly in landscape but then briefly displays a garbled version of "Default@2x.png" in the wrong orientation (which is obviously a bad first impression for users). I have no such issues with a prior version of AIR 16 which I've reverted to.Can anybody explain what may be happening there and whether it will be addressed in future? I can only hold out so long before I'll need this new version for 64-bit support (which I trust will be available on Windows by Feb).

Hi Adobe AIR community,I've been having this problem for a while now. Basically I have been using AIR for iOS 15.0, Flash CC (2014) and Milkman Games Ad Mob ANE v.4.4.0.I can test my apps perfectly on both iPhone and iPad devices. The Ad Mob banner and full screen ads work very well while testing in a development environment.When I try to upload my app to the App Store using Application Loader v3.0 I get an error stating "error ITMS-9000: Invalid Bundle. The bundle my_app.app does not support the minimum OS Version specified in the Info.plist"Now funny thing is when I remove the ANE the app uploads to the App Store just fine.I have been forced to stop using ads in my AIR for iOS apps since the release of iOS 8.I have also contacted Milkman Games support but they tell me that I am the only one with the problem and that support tech can't recreate the problem.Also I am using OSX 10.10.1 and I believe that xCode has been updated to version 6.1.1 (not sure if updating xCode makes any diffe

Hello,Regarding the latest release notes for AIR 16, it says "The legacy compiler is not (and will not be) compatible with iOS 64-bit.[...] it will be removed with version 16 of the AIR SDK"I am a bit lost with what it means for Flex Mobile (4.6 or Apache Flex SDK). Will we still be able to compile once AIR 16 is out or will this new compiler have issue with Flex projects compiled for iOS? Will it need us to make some changes on existing Flex applications?Thanks for your clarifications,Fabien

I have been using the same ANE for about 18 months now for native alerts in AIR on Windows desktop. Just recently AIR has started throwing the following error when trying to call any of the functions in the extension (in this example confirm is the function being called in the NativeDialog ANE):ArgumentError: Error #3500: The extension context does not have a method with the name confirm.  at flash.external::ExtensionContext/_call()  at flash.external::ExtensionContext/call()  at com.nemenvisual::NativeDialog/confirm()  at application.ui::NativeAlert$/confirm()  at application.control::CommandCentre$/execute()When the app is published and installed it seems to work fine - the error only occurs when debugging in Flash CC. Has a recent update to Flash introduced this or is there some way around it? I tried going back to AIR 14 and the issue still occurs so I don't think an AIR update has caused it.

Will it ever happen?

It seems that regardless of the renderMode settings in application.xml, AIR is always forced to CPU when displaying our game. This happened quite recently when we decided to test a newer version of the Android 5.0 developer release.Note that performance is correct on one of our other apps using Stage3D, so this must purely be a GPU/CPU mode thing, with Direct not being affected when applicable.Test device: Nexus 7 (2013, Razor)OS: Android 5.0 (build LPX13D, August 16th)AIR SDK: 15.0.0.302 (as available as official download) as well as latest AIR 15 Beta (Oct 22, 2014)Fix: reverting back to AIR SDK 14 solves all performance problems and seems to run in GPU mode correctly. Also, older Android versions seem unaffected, it's strictly Lollipop.Is anyone else running into this?

iOS ane in gaming 1.4 is not support AIR16 beta, when gaming will updata and fix this error?

The AIR SDK we used is 1/14/2014 Release - AIR 4.The device we have tested on is Samsung Galaxy Note 3/Android 4.4.We found that it's quite similar with Bug 3681788 which has been fixed in Beta version 4.0.0.1619.We checked the issue again with this beta version, and the result is Chinese characters are shown correctly, but Korean's are still not.Bug 3681788: The CCJ languages characters are displayed as blank box on the TextField.Hope it can be fixed as soon as possible.

Hi Adobe Staff,I've encountered an issue of my APP for iOS, that AIR 16 will crash in some circustance, but when i rebuild the App with AIR 4.0, it does not crash at the same circustance.I thought it was AIR 16 's issue. when i try to debug the app in standard package mode which said to be has the same behavior of release build, but it does not crash in the same cirsustance.It would be the bug of release package engine of AIR 16. would it?My using AIR 16 is<name>AIR 16.0.0</name><version>16.0.0</version><build>250</build>I try to analysis the crash log, but i can not understand the log text. The call stack is not human friendly.

Hi,We have developed a windows application "DsNetHTML5Player" in Adobe Air which shows HTML pages in sequence using <mx:HTML> control. When I run application in "Flash Builder" all plays fine.After creating its build and installing on system (Windows 7) application crashes with following error.Faulting application name: DsNetHTML5Player.exe, version: 0.0.0.0, time stamp: 0x4d7a7dd2Faulting module name: WebKit.dll, version: 6531.9.0.0, time stamp: 0x50fcd627Exception code: 0xc0000005Fault offset: 0x000a99acFaulting process id: 0x19c0Faulting application start time: 0x01d00ae266bc2b46Faulting application path: C:\Program Files\DsNetHTML5Player\DsNetHTML5Player.exeFaulting module path: c:\Program Files\Common Files\Adobe AIR\Versions\1.0\Resources\WebKit.dllReport Id: 99882a24-76d6-11e4-a3ad-005056c00008If anyone has any idea what the problem could be here, please let me know.ThanksUmair

Hi,I am aware that this is not an Air question, but Flash forums seem to be pretty useless by now.. So in our cross-platform game we are using FULLSCREEN_INTERACTIVE to allow user keyboard input while in fullscreen. In Air this works fine but in the browser it's borderline unusable.Right now the user is asked once at the beginning of the fullscreen if he wants to allow interactive fullscreen. It starts that there is no "remember my decision" option for the current webpage here. What's worse though is, that EVERYTIME the user moves the mouse to the top, the ugly overlay is triggered once again. There is not even a minimum time til the next trigger. It's super annoying and we have (like most games) UI in the top of the screen which triggers the Flash overlay almost the whole time. We have lots of user requests to "reduce the interval" in which the overlay is shown. Last but not least, when the user clicks "Allow" on fullscreen activation, this is even carried as a MouseEvent into the Fla

Number 1 - Memory consumption before frame 5. No escalation, everything is perfect. I can switch content of frames 5 and 4 and it will give me same result - no grow in memory consumption.Number 2 - My hell. From 5th frame (EVEN IN EMPTY FRAME WITH NO CODE) memory consumption escalates, goes down to minimum and grows again and goes down... And doesn't stop until I close my app (same behavior on my android device).Tried to compile in CS6 and CC - no difference. It doesn't slow my app, it does nothing to performance, but it irritates me and as far as my app is for study - I am afraid, that this will lead to battery discharge faster than without this leak. Please help!