Just in case anyone still has trouble with this for hosting your installer other than on the Mac App Store, here is my bash script that creates a .pkg installer for MacOS and it downloads without any warnings from any browser (tested with Safari, Chrome, Firefox and Brave), and it installs without warnings, and the installed app launches without warnings. It also fixes the icons that as of AIR 31 are still wrong for MacOS, and it updates Info.plist with version. This app package contains 10 ANEs as well. # !/bin/bash VERSION=$1 USAGE="Usage: build.sh app_version_string (n.n.n)" if [ "$VERSION" == "" ]; then     echo "app_version_string is required"     echo ${USAGE}     exit 1 fi INFO_PLIST="$APP_DIR/out/your-app.app/Contents/Info.plist" cd $APP_DIR # copy icons file over the one built by AIR which is still packaged incorrectly as of AIR SDK 31 cp -f ./packaging/Icon.icns ./out/your-app.app/Contents/Resources/Icon.icns rm -f "./out/your-app.app/Contents/Frameworks/Adobe AIR.framework/Versions/1.0/Resources/WebKit.dylib" rm -f "./out/your-app.app/Contents/Frameworks/Adobe AIR.framework/Versions/1.0/Resources/Adobe AIR.vch" /usr/libexec/PlistBuddy -c "Set :CFBundleShortVersionString ${VERSION}" "${INFO_PLIST}" /usr/libexec/PlistBuddy -c "Set :CFBundleGetInfoString ${VERSION}, © 2018 Your Company, Inc. All rights reserved." "${INFO_PLIST}" /usr/libexec/PlistBuddy -c "Add :LSApplicationCategoryType string public.app-category.business " "${INFO_PLIST}" codesign -f -v -s "Developer ID Application: Your Company, Inc. (YOUR_TEAM_ID)" "./out/your-app.app/Contents/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR_64" codesign -f -v -s "Developer ID Application: Your Company, Inc. (YOUR_TEAM_ID)" "./out/your-app.app/Contents/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR" codesign -f -v -s "Developer ID Application: Your Company, Inc. (YOUR_TEAM_ID)" "./out/your-app.app/Contents/Frameworks/Adobe AIR.framework" codesign -f -v -s "Developer ID Application: Your Company, Inc. (YOUR_TEAM_ID)" "./out/your-app.app" productbuild --component ./out/your-app.app /Applications "./packaging/mac/your-app.pkg"  --sign "Developer ID Installer: Your Company, Inc. (YOUR_TEAM_ID)" --identifier "your-app" --version "${VERSION}" ... View more

I too am having this issue. Please note that I am an Adobe Certified Expert (ACE) for Flex 4.6 (before Adobe discontinued the ACE program), and I have been developing Flash/Flex/AIR apps since Flex 3.0. I have created quite a few commercial AIR apps and this problem only manifests in AIR 30 (and 29 I might add, but that was due to beta-reports-active entitlement that is no longer being written to the embedded.mobileprovision file). Here is the iOS Console output showing what appears to be a malformed entry: Jul 16 14:26:35 Eriks-iPhone-6 installd(libmis.dylib)[3043] <Notice>: entitlement '<private>' has value not permitted by provisioning profile '<private>' Jul 16 14:26:35 Eriks-iPhone-6 installd(MobileSystemServices)[3043] <Notice>: 0x16ef3f000 +[MICodeSigningVerifier _validateSignatureAndCopyInfoForURL:withOptions:error:]: 147: Failed to verify code signature of /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.FOc3EW/extracted/Payload/keiretsuforum.app : 0xe8008016 (The executable was signed with invalid entitlements.) Thank you for your kind consideration and there's really no need to send me links to pages that teach how to develop or troubleshoot AIR apps. This appears to be a problem introduced in AIR 30. We haven't had a fully functioning AIR release since version 27 due to the public APIs problem, followed by the beta-reports-active entitlement problem, now followed by this new problem. Sure appreciate if you could take this seriously. ... View more

Thank you AIR Team! ... View more

My concern about this decision is only in the timing. When Adobe open-sourced Flex and when they sunsetted Flash they gave us timelines so we could plan and adjust. This decision is every bit as impactful to our business, and I sincerely hope that Adobe will reconsider their decision and support 32/64 for a little while longer and give us a time to adjust. Perhaps keep it the next two AIR releases and make an announcement that, for example, AIR 32 or 33 will be 64-bit only. We just need a little time is all. This sort of change is inevitable and we don't oppose the 64-bit only decision per se, but please give us a little time to plan this transition. Others have also shared that it may be a bit too early to alienate iPhone 5 and iPad 4G users. We do indeed have users on those devices. Perhaps another year would be a better decision, but we'll take what we can get. Thanks for your consideration, Adobe. ... View more

Hey Chris, thanks for letting us know about the upcoming fix for Ad Hoc. However, the workaround is really not of any practical value in an iterative edit, build, debug cycle using an IDE like IntelliJ or Fb. Scripting the fix for the beta-reports-active entitlement and re-signing and re-packaging the IPA is but one small part of a larger developer workflow, a workflow we depend on IDEs to take care of. We already script adt.jar to find device handles and deploy to multiple devices, that's the easy stuff, but getting the IDE to attach to the running app on the device isn't something we've ever needed to tackle. That's why we paid so much for Fb back in the day and IntelliJ IDEA now. Looking forward to getting your fix. Our apps all use ANEs that do stuff you cannot fake on an emulator, so we have no choice but to develop on devices. But it's working out fine to use Android for now. Just that packaging iOS is so much faster we look forward to getting back to our standard developer workflow. But Kudos for getting the non-public API fix out there so quickly! And despite the fact we will always have some issues with AIR, the AIR team really does rock! We just wish they had a bigger budget and could eliminate the need for so many ANEs that do such basic stuff that ought to be in the AIR runtime. ... View more

On April 19th, 8 days ago, Amrita Gangwani said this about the Ad Hoc local development build problem:   "Thank you for the valuable information. The issue with the ad-hoc provisioning is known to us and we are working on it." This Ad hoc issue should be a priority unless you plan to sunset AIR too (I hope I'm wrong). You guys jumped on the non-public APIs really fast, and it was great, but roughly two weeks later and nothing has yet been done on the Ad Hoc issue. If it's as simple as removing the Info.plist.beta-reports-active entry, this should take 10 minutes to fix, plus running your automated regression test suite--if you got one. What's going on with that? Any news? This is hurting us every bit as much as the non-public APIs issue, just in a different way. Thanks muchly, Erik ... View more

Yes, not being able to do local Ad Hoc testing is a pain that should go away with the next AIR build, but for now, if you also do Android development, just use that for your local testing. If not, you can upload to iTC and use TestFlight to test. Not convenient, but works around the problem of Apple rejection for now. I'm still waiting on Adobe for the fix. Actually surprised they haven't released it already. ... View more

No need bothering with overlaying the SDK, the latest Flex SDK installer includes the AIR 29.0.0.122 build that will get you past Apple reviewers, so just use the installer and select AIR 29 from the install menu and place it in a new directory. Configure your project to use the new SDK and you should be good to go. Apache Flex® - SDK Installer ... View more

Yes, would it be possible to canvas the borg to let apps slide on this issue for a few weeks until the AIR release is official? We just ran into this issue today and it's a showstopper of profound impact on our business. ... View more

OK, you've convinced me this is NOT an AIR issue. But it's still a Flex issue since ActionBar is a child component of View classes and it doesn't do the right thing on iOS7 without applying these manual workarounds, and even if you do these workarounds, it still looks bad because you're just stretching the action bar and placing content below where the indicators show through. Yuk! I'll go take this to the Apache Flex site. We can end this thread. ... View more

Doesn't work. If you read my post, I said: >> "I've tried using CSS to fix this, but can't add space above the Action Bar for the indicators to show correctly." The CSS was exactly what you suggested. Doesn't work because padding just adds space to the INSIDE of the action bar and pushes down the content (text), but the indicators still show through. No, been there done that. But I'm using INTERACTIVE_FULL_SCREEN now and it gets rid of the indicators in my app, so problem solved for now. I think the Flex SDK needs to consider this issue as a bug since out-of-box "Hello World" apps all have this problem. ... View more