All geek questions in one place

Damaged AIR application after signing with renewed certificate

Our code signing certificate has recently completed. It has been updated, but now when I try to pack the application with an updated certificate (whether I try to migrate an outdated certificate or not), after installation I get the following message when I try to start the application:

"This installation of this application is corrupt. Try reinstalling or contact the publisher for help."

Opening the contents of the package, the publisherid file inside the / META -INF / AIR resources is empty. This is apparently a problem because if I manually edit it to hide our previous publisher ID, the application will start.

But, of course, this is not the case, as we can tell all our users "about, install it, and then manually edit this file inside the package."

Has anyone come across this or knew how to fix it?

+3
source share
1 answer

And, after I hit my head a little on my table, I understood.

For everyone who comes for me:

I had to change a couple of things in the application descriptor file.

First I had to change the namespace to indicate in AIR 1.5.3 instead of 1.5

<application xmlns="http://ns.adobe.com/air/application/1.5.3">

And then I had to manually specify our old publisher ID in the descriptor, as well as

<id>OurAppID</id>
<publisherID>OurOldPublisherID</publisherID>

Now it works as expected, and installs a new version instead of the old version, and instead just launches this error.

+1

Source: https://habr.com/ru/post/1770231/

More articles:


All Articles