AIR SDK 20.0.0.233 results in ApplicationVerificationFailed error while 20.0.0.204 compiles successfully

Report · Jan 04, 2016

Hello,

We're experiencing ApplicationVerificationFailed error with AIR SDK 20.0.0.233 every time no matter the type of buid we're compiling (debug/test/adhoc/etc) while 20.0.0.204 compiles successfully every time.

Any advice on how to make 20.0.0.233 work since it doesn't appear to be working out of the box?

Thanks.

Report · Jan 04, 2016

Thanks for the heads up. I've asked the team to investigate.

Chris

Report · Jan 04, 2016

Hi,

Thanks for reporting the issue. Are you facing this issue on Windows or MAC? Could you please try the following workarounds mentioned in the release notes

As per the release notes of AIR SDK 20

[iOS ] "This build is invalid" error in iTunesConnect while uploading app

This issue has been fixed on Mac. To package the app correctly, so that it gets uploaded to iTunesConnect without any errors, the developer needs to perform following
Add certificate in the Keychain Access of the Mac and provide necessary permission to it while adt accesses the certificate.

Along with this please make sure that there is no Info.plist present in the assets folder while packaging the ipa.

Thanks,

Adobe Air Team

Report · Jan 05, 2016

Hello,

Thanks for the quick response.

We're using Windows 7 and it's also tested on 2 separate machines but the project never compiles correctly.

The first provided solution is related to IPA submission on Mac but we still haven't tried to submit a build with 20.0.0.233 because we can't compile one that can be installed on a device.

As far as the second suggested solution, we don't have file named Info.plist in the assets folder.

If you find it helpful we can fetch some content from the generated IPA file (it is being created but can't be installed on device) or send you the IPA itself for further investigation to track what's causing the ApplicationVerificationFailed error inside the package.

Thanks.

Report · Jan 05, 2016

Hi,

We tried to reproduce the issue at our end but failed to do so. We can successfully package and install an app with 223 build in a Windows 7 Machine.

Can you kindly share the app(swf and xml) you are testing in a drop box link OR in the following Mail: chhetri (at) adobe (dot) com

-Roshan

Report · Jan 05, 2016

Hello,

Just found out that the error is being caused by one particular ANE we're using which is HeyZap UnityAds and can be found here:

Ane Setup And Requirements Documentation • Heyzap

Select the UnityAds integration and the following URL for download will be provided:

https://s3.amazonaws.com/third-party-sdk/ane_unityads_1.4.5/UnityAds.ane

When we try to compile with only that particular ANE we get these errors in the console:

ld: warning: object file (C:\Users\User\AppData\Local\Temp\acfe9e49-77f7-4724-89e3-dd6

39049d704\libcom.heyzap.sdk.extensions.unityads.a(UnityAdsANE.o)) was built for newer iOS

version (8.1) than being linked (7.0)

ld: warning: object file (C:\Users\User\AppData\Local\Temp\acfe9e49-77f7-4724-89e3-dd6

39049d704\libcom.heyzap.sdk.extensions.unityads.a(UnityAdsANE.o)) was built for newer iOS

version (8.1) than being linked (6.0)

Do you have any tips about the sudden limitation regarding this ANE so we can contact HeyZap and request them to correct it or is just that the ANE supports only iOS 8.1+ and cannot be fixed?

Thanks.

Report · Jan 06, 2016

Hi,

As I see, there was an Info.plist file inside the ANE hence it was not able to install on the device.

We are looking into this issue and come back once we have an update on the same.

-Roshan

Adobe AIR

Report · Jan 06, 2016

Hi,

for now, you can package the application in MAC machine with the AIR SDK 223. Please follow the steps mentioned in the release notes:

http://fpdownload.macromedia.com/pub/labs/flashruntimes/shared/air20_flashplayer20_releasenotes.pdf ...

To package the app correctly, so that it gets uploaded to iTunesConnect without any errors user needs to perform following

1. User has to add certificate in the Keychain Access of the Mac and provide necessary permission to it while adt access es the certificate.

2. If user is doing remote login (ssh) for packaging the app, then it requires extra command. Security unlock /Library/Keychains/login.keychain for successful packaging

In windows we have a known issue for which our team is already working.

-Roshan

Adobe Air

Report · Jan 14, 2016

So currently we cannot use AIR 20, because it generates corrupt packages.

We cannot use AIR 19 because of a linker issue with ANEs that fails even to compile our app.

AIR 18 works but due to a bug you cant connect to the debugger on the device.

Great work, cant wait for AIR 21! Perhaps this time you manage to break the AS3 compiler too!

Report · Feb 22, 2016

Hello, I'm facing the same issue - under windows7 x64 I get the same error while trying to build the app with AIR SDK 20.0.0.260 caused by com.heyzap.sdk.extensions.unityads ANE. I even tried AIR 21 beta, but it gives me another issue, caused by HeyZap's AdMob ANE %)

Have you solved the issue somehow?

Report · Feb 22, 2016

Hi,

Kindly package the application in MAC to get rid of the issue.

-Roshan

Report · Mar 10, 2016

@roshan chhetri How could you seriously suggest to a windows user to build on a mac... This bug has been known since 4th January, it's about as critical as a bug can get and there is still no fix. AIR 21 beta has exactly the same flaw. Is there at least any progress on this issue? Is there an ETA for fixing it?

Report · Mar 10, 2016

Hi,

Yes, we certainly understand the inconvenience you might be facing because of this. However, I am sorry to inform that we're still investigating this issue, and there hasn't been any significant progress on it. The problems that we're facing is that things have changed from Apple verification side, and it isn't looking straight forward to port these new changes on signing process for a Windows system. I would want to re-iterate that the issue comes into picture only while uploading the final IPA, and it shouldn't hinder any development or testing phases. So, you may still continue all your development on a Windows system, the final IPA build however should be packaged on a Mac for a successful upload to iTunes store.

-Thanks

Pahup

Adobe AIR Team

Report · Mar 11, 2016

" I would want to re-iterate that the issue comes into picture only while uploading the final IPA, and it shouldn't hinder any development or testing phases. So, you may still continue all your development on a Windows system, the final IPA build however should be packaged on a Mac for a successful upload to iTunes store."

This is incorrect. The ApplicationVerificationFailed stops the build and prevents the ipa from being installed on the device (Using Flashdevelop & AIR 20).

Futhermore, it's not that simple to port your whole dev environment to a mac just for building.

Report · Mar 11, 2016

Maybe you're having some other error. I can verify I'm able to build an IPA on windows 10 with Flash builder 4.7 using AIR 20. I can deploy and debug successfully on the device.

Report · Apr 07, 2016

Hi All,

This has been fixed on both Win and Mac AIR SDK's.

Please find the fix here: Download Adobe AIR 22 Beta - Adobe Labs

Thanks for your patience. Kindly let us know if you have any queries.

-Roshan

Adobe Air

Report · Apr 07, 2016

Hooray!

Report · Apr 08, 2016

Thank you, this is great news!

Please Adobe focus on bugs and performance instead of features. Most of us use AIR for games with Starling, so while things like AGAL 3 and fancy texture improvements are nice to hear about 95% of the people will never use it. But 95% of the people will be banging their heads because of bugs that increase dev time significantly (I personally spent like 1 week+ on trying to circumvent and fix AIR bugs during the last 6 months).

The current pain points (besides this bug):

- Still unable to compile when ANEs include .plist files.

- Bug#4052562 - Cannot write files on iOS device - We had to write an ANE for this

- Bug#3961778 - ATF artifacts (not usual compression related artifacts) on some android devices - The most popular high end devices from Samsung and Sony are affected. We get bad reviews users complaning that our game looks bad. Nothing we can do

- Bug#3364803 - [Platform_Android]Samsung Galaxy S III relaunches to a black screen after receiving a ... Again nothing we can do. 1 star reviews because with users complaining that our game is buggy.

Report · Apr 21, 2016

Hi,

Regarding "Still unable to compile when ANEs include .plist files."

The latest Beta Download Adobe AIR 22 Beta - Adobe Labs should fix your issue.

We will look into the rest of your bugs you have posted here and reply on the bug itself.

-Roshan

Report · May 03, 2016

We use the AIR 22 Beta wich you linked... but still have "ApplicationVerificationFailed" Message.

We use a "Developer" Account from Apple (not Enterprise) and have an iPad with IOS 9.3.1.

We are on a Windows 8 Machine.

On Our other Enterprise Account we also have customer projects and there we don't have this problems. Only on the Developer Account.