Could you please identify the version of AIR that addresses this problem? I am encountering this problem when using AIR 17.0.0.105. In my case, the ANE-driven version mismatch is 5.0 versus the 7.0 listed in my application descriptor. Setting the application descriptor minimum to 5.0 is not possible because 64-bit apps require minimum iOS 5.1.1. ... View more

I've tried setting and removing the following manifest settings, to no avail: <uses-feature android:name="android.hardware.touchscreen" android:required="true" /> <uses-feature android:name="android.hardware.touchscreen.multitouch" android:required="true" /> <uses-feature android:name="android.hardware.touchscreen.multitouch.distinct" android:required="true" /> ... View more

Error persists in AIR 16.0.0.222. I have to release an AIR authored iOS app next week. I hope it runs on the devices I can't test against. ... View more

Error occurs in OS X 10.10.1 as well. ... View more

zed0784 Where did you find the AIR 16 release notes? I'm getting a 404 link not found error when trying to access the link http://labsdownload.adobe.com/pub/labs/flashruntimes/shared/air16_flashplayer16_releasenotes.pdf ... View more

Issue is still occurring for me with the latest AIR 16.0.0.214 (pure ActionScript app, IntelliJ IDEA 14.0, OS X 10.10, iOS SDK 8.1). ... View more

To be more specific, I am running a project on an entirely new machine. The first time I ran it, it successfully launched iOS Simulator and ran fine. However, iOS Simulator defaulted to the iPhone layout. I quit iOS Simulator, launched Terminal to change to iPad config: launchctl setenv AIR_IOS_SIMULATOR_DEVICE "iPad Retina” …then quit IntelliJ IDEA (because I've found that's necessary), relaunched IntelliJ IDEA, and the problem reoccurred. Manually uninstalling ipa from iOS Simulator then re-running did not resolve the issue. I suspect it has little to do with what I did, but is probably a second-run issue. ... View more

I'm getting this error as well. The problem exhibits in IDE (IntelliJ IDEA 14) and command line adt -installApp as well. Details: pure ActionScript AIR 15.0.0.349, Xcode 6.1, iOS 8.1 SDK, OS X 10.10. ... View more

Nope, the nasty "S**" work still getting censored by the naughty word filter. There are some words developers must never mention. ... View more

Ok let's see if this copy paste doesn't insert a space : /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator8.1.sdk I found that I needed to point to the specifically numbered alias to make the compiler happy. The exact number will depend upon your SDK install, take a peek inside your Xcode application bundle to make it match. ... View more

I want to chime in to add to the volume. This is a critical update, and developers will need hands on it well before this deadline. Remember that this requirement is only for new apps. If you have a new app that releases just after February 1, you might want to plan on shoehorning a limited version into the App Store ecosystem first just to get it in there and dodge the requirement by posting your planned 1.0 release as an update later. ... View more

Thanks for the answer Romil! In clear speak, the answer is: AIR 15.0.0.328 Beta does not support iOS 64-bit, but a future release will. I want to emphasize what other concerned developers are saying on the post at Re: AIR 64-bit Required By Apple from February 2015. It is absolutely critical that Adobe get a stable AIR GM that supports 64-bit iOS in a timely manner (3 months left). Developers will need this release even earlier, to test their software and update their ANEs (1.5 months left?). I have a big iOS AIR project that is just starting and has a target release window right around the newly imposed requirement date, so a lot is riding on this. A formal updated AIR roadmap post with ETAs would help allay any doubts. Or, just surprise us and publish the new version ... View more

Thanks JonArnold, these are some excellent detailed steps! For other struggling through this, here is some additional vital information about certificates I've discovered through exhaustive reading on Apple's developer site. Changes in OS X 10.9.5 mandate some measures that aren't reflected in most guidelines for packaging and codesigning, including Adobe's post linked above, and all the other links. It turns out that there is a different type of certificate for signing apps for submission to Apple for Mac App Store distribution than the certificate needed for independent distribution. Despite the fact that some of Apple's documents say that certificates issued by legitimate third parties can be used for codesign, despite the fact that a certificate can pass internal certification and be marked OK for codesign in Keychain Access, it seems that only a proper certificate issued from Apple's developer program will do the trick. For submission to Apple for distribution to the Mac App Store, you will need to manually codesign your AIR app properly using a Mac App Distribution certificate. In Keychain Access, this certificate will have a "3rd Party Mac Developer Application:" prefix. For independent distribution, you will need to manually codesign your AIR app using a Developer ID Distribution certificate. In Keychain Access, this certificate will have a "DeveloperID Application:" prefix. Tip: Because of very inconsistent labeling of certificates (differing names in the online portal, filename when downloaded, name in Xcode, name in Keychain Access), I recommend clearly renaming downloaded .cer certificates by appending a clear description as well as the date of expiry to match that in the development portal. When performing a manual codesign on an app destined for Mac App Store distribution, spctl and Gatekeeper will reject the resulting app! It is only after Apple approves your submission and publishes the app on the Mac App Store that it will pass spctl and Gatekeeper test. I’m still getting our development team setup for the Developer ID provision and will report back with details when I go through this process. ... View more

I would suggest that those interested take a look at thread Tutorial on publishing Flex/Air app for Mac App Store or just using Developer ID for general distribution However, since that thread is marked as answered, I want to leave this thread open until I find an answer to my particular question: What are the exact steps to properly package and codesign an OS X AIR app for independent distribution to OS X 10.9.5? ... View more

This is the best post on this issue I could find in the Adobe Forums, kudos DMcQ! That being said, I concur with the other commenters. There are still way too many loose and outdated suggestions. Adobe sorely needs to step up and produce something comprehensive, something far better and more up-to-date than the Post Adobe AIR app to Mac app store page. AIR developers need two detailed documents with explicit environment/SDK version details: 1) Packaging an OS X Adobe AIR app for independent distribution 2) Packaging an OS X Adobe AIR app for Mac App Store distribution I am struggling to properly codesign my OS X AIR app for independent distribution and have not yet succeeded in creating an app bundle that passes a clean circa OS X 10.9.5 v2 certificate Gatekeeper test: spctl -a -t exec -vv Foo.app. This returns one of the following, depending one what approach I take: - rejected - nested code is modified or invalid - a sealed resource is missing or invalid Just some of the many questions and concerns I have regarding some provided suggestions in this manual re-packaging and codesign process: - Doesn't removing contents of the bundle after it is built invalidate the included resources and jeopardize subsequent codesigning? - Performing a brute force chmod -R 777 MyApp.app  seems to set the executable bit on enclosed items willy-nilly which seems counterproductive. - What exact enclosed items need to be codesigned (directories, plugins, binaries), and in what order? - What about non-App Store distributed applications that need to rely on WebKit? - What about sandboxing entitlements? - If entitlements need to be created, provide examples on typical AIR application entitlements and how to craft the file. - Should the codesign --preserve-metadata option be used, and if so, with what parameters? - Doesn't AIR 15 [latest beta] support the large icon sizes in the application descriptor and obviate the need to manually edit the icns file? ... View more

Thanks Grahamsmith for verifying this. The command line approach works, so the problem does not lie in the AIR or iOS SDKs, so I'm marking this issue as fixed. Unfortunately using the command line approach removes any debugging advantage I get from using my IDE of choice (IntelliJ IDEA). There is some severe problem with the build configuration process of IntelliJ IDEA 14 which continues to apply a bogus keystore value during the packaging process. This is outside the scope of Adobe though. ... View more

Adding the additional -platformsdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator.sdk option does remove this error, but it is followed by another: Signing options required to package IPA Unfortunately I think something is broken in my IDE (IntelliJ IDEA 14) and the keystore settings from the build configuration are not being reflected in the ADT command. It is pointing to -keystore /Applications/IntelliJ IDEA 14.app/Contents/plugins/flex/lib/temp_keystore.p12 instead, and can't be overridden. ... View more

This is what I'm trying to avoid: ... View more

Hi Anton, no this pinging behavior is coming from a captive runtime bundle for desktop OS X and Windows. Both app and exe exhibit this behavior. ... View more