Urgent - Updates no longer working after certificate renewal (production app)

Report · Oct 11, 2010

Hi,

Updates pushed for our production AIR application are failing after a renewal of our expired code signing certificate, and performing the certificate migration procedure as outlined here:

http://help.adobe.com/en_US/AIR/1.5/devappsflex/WS13ACB483-1711-43c0-9049-0A7251630A7D.html

The error message appears as: "This application cannot be installed because this installer has been mis-configured. "

The AIR app installer log indicates the source of the problem:

"The certificate of the installed app fails to match either the signature or migration signature of the AIR file"

However, the migration procedure has been executed exactly as described, using the correct certificates. The Adobe AIR 2.0.2 runtime (and adt) has been used.

We need to push an important update asap, and advising our end users to reinstall is not feasible.

I am willing to provide anything necessary to resolve this as quickly as possible. Please advise.

Report · Oct 11, 2010

Happy to report that we found the source of the issue ourselves:

There is apparently a problem with ADT (at least in the AIR 2.0 SDK) where it will appear to perform a certificate migration succesfully, but in actual fact will silently fail and not update the .AIR file at all. This happens when the output filename is equal to the input filename, so this problem arises if you follow the example in the documentation:

http://help.adobe.com/en_US/AIR/1.5/devappsflex/WS13ACB483-1711-43c0-9049-0A7251630A7D.html

A simple workaround is to choose a different output filename. In any case, be wary that ADT does not provide feedback whether a migration actually was performed. Check the file timestamp and size to be sure.

Report · Oct 11, 2010

Hi Chris,

Thanks for the update and I'm glad you found a work around. I'm going to forward this along to the engineer that tested ADT to give them a heads on on your findings.

Thanks,

Chris

Report · Oct 12, 2010

Hi Chris,

I could not reproduce your problem. ADT 2.0 is able to overwrite the original AIR file when it does migration.

Could you still reproduce the problem?

-ted

Report · Oct 13, 2010

Hi Ted,

The issue is real and is consistently reproduced.

When I use this line:

adt -migrate -storetype pkcs12 -keystore "[OurKeyStore.p12]" OurApp.air OurApp.air

It will appear to proceed normally, but simply fail to update OurApp.air in any way.

If I simply change this to (ie. change the output filename):

adt -migrate -storetype pkcs12 -keystore "[OurKeyStore.p12]" OurApp.air OurApp2.air

It will work perfectly.

We are using Windows 7 64-bit, JRE 6.0.200.2. The ADT.jar is the one included in the AIR 2 SDK (2.02). MD5 checksum feea4d90723d3315ee66e3c97c5d49c1. Do you need any other information?

Chris

Report · Oct 13, 2010

Just wanted to add that the same happens when I attempt the migration procedure inside Aptana Studio (and since the parameters cannot be changed here, it is not easily possible to do the migration in Aptana - which is a bit frustrating).

Report · Oct 13, 2010

Hi Chris,

Thanks for the info.

I have verified the problem exists and have filed a bug about this.

Thanks,

-ted

Report · Jan 29, 2011

Hi Ted,

Is there any update on this? Thanks!

Chris

Report · Feb 02, 2011

Hi Chris,

This bug has been fixed. If you have access to Prerelease, you should be able to see the problem is gone.

If you don't have prerelease access, please wait for the new release.

-ted

Report · Feb 03, 2011

Great, thanks Ted!