chaky​, You're the one reading it wrong. Anything listed under known issues remain to be issues, the date refers to when the issue was initially added to the list of known issues. But I get how you can get confused. Only when the certificate issue is listed under the list of fixed issues, you'll know it is resolved. ... View more

What do you mean there is nothing under known issues in the release notes? The issue has been know for a few weeks and I've seen it listed in the last 2 release notes of AIR 30 Beta. The below is taken from the known issues in the release notes AIR ETC2 with Alpha content having LZMA/JPEG-XR compressions have black dots/lines when renderd on Android Certificate related warning appear on submitting Apps to Apple AppStore. Link to the full release notes: https://fpdownload.macromedia.com/pub/labs/flashruntimes/shared/air30_flashplayer30_releasenotes.pdf ... View more

Flipline​ I think you're not completely understanding the Apple Technical Q&A you're referencing. Creating a 64 bit only update to your app could violate the App Store guidelines. However, that can be avoided by, as explained in the Technical Q&A, "Target[ing] a newer version of iOS that requires a newer device". As you know, iOS 11 completely dropped 32 bit support, so it runs exclusively on devices with 64-bit processors. When you create your update with AIR 30, if your target iOS 11 setting the MinimumOSVersion key your 64 bit only app should not be rejected. It might be that when AIR 30 is released the target iOS version is set to 11 by default, so you won't have to do anything. Now, that being said, I do think it would have been good to keep 32 bit support apps for a bit longer as the market share for those devices is about 20% - 23% (App Store - Support - Apple Developer) but you can for now continue to support those devices using AIR 29. chris.campbell​ pravishtis​ Also, it would be good to hear Adobe's justification for dropping support for the universal 32+64 bit IPA. I hope it meas they're optimizing the runtime or the code generation. That's me being positive but who knows. ... View more

No, it doesn't override the value you specify but setting beta-reports-active to false won't fix the issue because the entitlement itself (regardless of being true or false) is not supported in Ad Hoc provisioning profiles, so you will get an error when trying to install the app. ... View more

I was able to workaround the Ad Hoc issue by resigning the IPA using codesign. Here's my solution but keep in mind that my app doesn't use any dynamic Frameworks, so the signing the app is very straight forward. I understand the process of signing is more complex when you have dynamic Frameworks but I don't know for sure. Anyways, I simply used the commands below to resign the IPA on a MAC (sorry, no windows solution). # Note: The command are executed in the directory where the IPA is stored. That's why there are no path references. Also, make sure # you change references to MyApp.ipa, MyApp.app and "My iPhone Distribution Identity" to the correct values for you app. # "My iPhone Distribution Identity" is usually something like "iPhone Distribution: My Company Name" #Unzip the IPA Payload unzip -q  MyApp.ipa #Extract the current entitlements codesign -d --entitlements :entitlements.plist "Payload/MyApp.app" #Delete the unsupported beta-reports-active entitlement for Ad Hoc builds /usr/libexec/PlistBuddy -c "Delete :beta-reports-active" entitlements.plist #Remove the current signature rm -rf "Payload/MyApp.app/_CodeSignature" #Signs the app using the updated entitlements. Make sure that your distribution certificate is in your keychain codesign -f -s "My iPhone Distribution Identity" --entitlements entitlements.plist Payload/MyApp.app # Zips the resigned IPA. The new Ad Hoc app that you'll be able to install is MyApp-resigned.ipa zip -qr MyApp-resigned.ipa Payload/ ... View more

The solutions you suggested didn't work for me. I've made sure to generate a new ad hoc provisioning profile and directly inspected it to ensure that there are not unwanted entitlements. Also, in my application descriptor XML there are no <key>keychain-access-groups</key> tags. After packaging the application, I keep getting the installation issue and the installation fails warning about an entitlements problem. When I use codesign to check the entitlements  in my application I found that the entitlement below was added: <key>beta-reports-active</key> <true /> Of course that entitlement is not in my provisioning profile with 100% certainty because as I stated above, I directly inspected the new provisioning profile I generated. This makes because Apple doesn't allow beta-reports-active for Ad Hoc or development provisioning profiles: Technical Q&A QA1830: The beta-reports-active Entitlement beta-reports-active is being added by ADT when it packages and signs the Ad Hoc app. That is the issue you need to address. ADT is arbitrarily adding an entitlement without verifying what's in the provisioning profile. ... View more

I'm experiencing the exact same issue that prevents ad hoc builds created with AIR 29.0.0.122 to be installed  and as you correctly pointed out, it is caused by the beta-reports-active, which is not supported for ad hoc provisioning profiles. ... View more

Do you know if there is a way to provide localized strings for NSLocationAlwaysUsageDescription and NSLocationWhenInUseUsageDescription? If not, I created a feature requests on Adobe's bugbase that you can vote Feature#3954108 - Ability to localize strings inside the iOS info plist ... View more

Hi sshk5, I replaced ALL files in the lib\android\bin folder of the AIR SDK. Here's the list: adb.exe AdbWinApi.dll AdbWinUsbApi.dll aapt.exe dx.jar The first 3 files are part of the Android SDK platform tools and the other 2 are part of the build tools. ... View more

Hi sshk5, I had a similar issue where the com/google/android/gms/common/api/GoogleApiClient$ConnectionCallbacks was not found. Doing some Googling around I found this post: https://github.com/playgameservices/play-games-plugin-for-unity/issues/193 I downloaded Rev. 20 of the Android SDK platform tools and build tools. From those tools I copied all the files I needed to replace what's in the lib\android\bin folder of the AIR SDK. Then I rebuilt my app and that solved the issue for me. I hope that helps. ... View more