We are having the same problem. Did you ever figure out how to fix it?
1 person found this helpful
This usually indicates that the certificate used to sign the AIR install has expired. Based on an archived discussion on this topic, you can search for SignatureTimeStamp in the signatures.xml file in the META-INF folder and, if it is not found, then the install has no signature time stamp and will not install after the certificate expires.
I'm having the same problem, but searching for SignatureTimeStamp is found. The search returns the following:
So, it would appear that there is a Time Stamp for the Signature in my case so the install should not fail. I would first check the above. Since you cannot install the app, you can try to open up the installation file with the .air extension as a zip file and drill down until you find META-INF and then drill down to find signatures.xml. Search for SignatureTimeStamp and see if it is found.
In the meantime, I was wondering if anyone else in this forum can explain why the install fails for me even though I can locate <xades: SignatureTimeStamp> in the signatures.xml file in the AIR install file.
Found the problem. The AIR package was installed using the "-tsa none" option which meant that no time stamp was applied to the signature. Once removing this option from the ADT installer the AIR package could be installed even past the certificate expiration date.
Would you mind to give a bit more detail how to remove "-tsa none" option from the air package? The one I tried to install jump right into installation after I click it. No place to conduct any setup. Same time I might be look into the wrong place. So, just want to make sure. Thanks a lot in advance.
6 people found this helpful
One option that worked for me, was to set the system clock to a date on which the code certificate was valid, install, then reset the clock to the current date.
5 people found this helpful
Timestamps that were issued before 08 / 2015 were issued by Thawte. The period of validity of these timestamps ended with 30.10.2017.
So all installations of older packages will fail.
This is really a big issue.
@Adobe: Workaround? (Of course you can set the system clock to 29.10.2017 - but that is no solution for our thousands of customers!)
I am having the same issue with our adobe air installers. Is there a way to resign the installers to change the timestamp without doing a whole new build?
We have around 100 applications having this problem and looking forward @Adobe for help!
Similar problem here. We have stopped all delivery, work on new productions, but some hundred thousand applications are still around with customers.
@Adobe: It is a bad idea to check the "end date" of a timestamp! The timestamp's function is to keep the certificate valid. btw: There is no documentation saying that a timestamp itself will lose its validity - in many cases almost at the same time when the certificate period ends. Adobe must have seen the problem because current timestamps are issued until 2031 - out of reach for warranty claims.
Yes, this works, but can not be a solution to all of our customers who have installers and don't know about this workaround.
I think it's not difficult to build a new installer with exactly the previous content, signed with a new certificate.
Since an air installer file is just a zip archive, you can unzip it and rebuild with the same version of the SDK that you have used for the original installer. Preferably you should have access to the original *app.xml that you had used for the original build, but you can also create a new *app.xml from the application.xml file in the archive.
All that's left to do then is run the correct version of adt, telling it to create an installer from the content you have just unzipped, using your new certificate to sign the code. I did this, it's not a big task and new customers are installing from the new air file.
As an aside I'll add that I've given up on air installers; I find their main merit to be the job security they provide for support personnel. The new version of our software is distributed as msi and dmg files.
For several clients we produced e-learning applications based on Adobe AIR. Many of them are distributed on DVD and stil available in the market.
Many of the apps where produced 2013/2014 with a self-made production Tool and with Adobe Flex/ Flash and Flashbuilder.
1.) Adobe Flashbuilder has a bug with timestamp, so you even can't compile any more, well there are workarounds...
2.) All these old projects are archived anywhere and wie had to get them out of the archiv and rebuild and reactivate our tool chain to recompile them.
3.) As i said: Apps where distributed on DVD, so this is a real big problem, it is not only a change of a linked file anywhere....
So it is not that easy!
Please Adobe do not leave us alone with this!
No one told us or warned, that i could be possible that AIR Apps older than 2 1/2 years from now will expire and can't be installed any more in the future.
** Just read Adobe AIR applications installation issue **
So this helps of course (we had this idea too) , but does not solve the problem, that apps are distributed on DVD.
Will Adobe release updated versions of the AIR installers that came with Creative Suite 6? I can't install AdobeHelp.air or WidgetBrowser.air using the files that were created by AAMEE 3.1 without changing the date of the computer.
I'm having the same problem as the OP. I've tried the steps you provided, ridhijain.
Here's how that went:
1. Attempted "Issue Confirmation" and cannot locate the statement “Package signature validation failed” in the log. This is what it says though after attempting to install my app: com.apple.xpc.launchd (com.apple.xpc.launchd.oneshot.0x10000008.Adobe AIR Application Installer): Service exited with abnormal code: 7
2. I went ahead and tried the "Solution" steps just in case, but couldn't get past extracting the .zip file after renaming. It just creates a new zipped folder every time I unzip it. So, stuck on that step.
You can see the app that I'm trying to install via this link and the file is named see.air: Sibelius - the leading music composition and notation software http://www.sibelius.com/download/sse/main.html
I've actually already contacted the author (Avid) first, as the error message suggested, and they seem to think it's an issue with Adobe and have directed me to this forum.
Here are my system specs in the event it makes any difference:
MacBook Pro 9,1 (15-inch, Mid 2012)
Processor: 2.6 GHz Intel Core i7
Memory: 16 GB 1600 MHz DDR3
OS Sierra 10.12.6
Latest version of Adobe Air: 22.214.171.124
Please offer a solution and/or confirm whether the issue lies with Avid and not Adobe. They are basically putting it up to me to find a solution unless you all are saying there is no issue.
I installed Adobe Air version 126.96.36.199.
I downloaded settingsmanager.air on the adobe site but when I want to install it I get a "Package signature validation failed".
How can I install it?
How exactly do you see the timestamp? I'm trying to install a Jigazo application (.exe) I copied this from a flash drive on an old computer with Windows XP. Then when I added it to my current computer (windows 10). I checked my adobe flash and reinstalled it.
Can you tell me how to check the timestamp please?
Please download the latest version of Adobe AIR from get.adobe.com/air. Workaround is available for the above mentioned issue without changing the system date or repackaging the .air app. . Steps to use the workaround can be found on Adobe AIR applications installation issue
this was it!
interesting this was a non-Adobe software.
You were able to install the application by resetting your system date as the application's certificate is no more valid. We recommend you to contact the application developer to re-package the application with a new certificate.
I needed to re-install an older Adobe AIR application to check whether it delivered the function I remembered, and ran into the "... installer file is damaged". Repackaging of Adobe AIR applications is not an option for the end-user. The second Workaround to manually launch "Adobe AIR Application Installer.exe” with the "ignoreExpiredCertificateTimestamp" option worked.
Having to launch the installer with Admin privileges seems to go against best security practices. I may elect to install an Adobe AIR application to a personal folder, which would not require any Admin privileges. A better solution would be to add an option to the Adobe AIR Installer so that the user can select whether to enforce or ignore expired certificate timestamps.