I'm afraid Thawte gave you some incorrect information, as it certainly is possible to timestamp AIR applications. In fact, timestamping is enabled by default, although you can turn it off. You can check to see if your application was timestamped by looking for a <SignatureTimeStamp> element inside the signatures.xml file.
Assuming your application is not timestamped then yes, you will have to redistribute a new copy signed with your new certificate. If it was timestamped, then we should investigate why that timestamp is not working as expected.
Hope this helps,
Oliver Goldman | Technical Lead, AIR | Adobe Systems | email@example.com
Thanks for your reply Oliver, I'm not a developer but I would like to
check the app to see if it was timestamped. Could you tell me how to
find it? Thanks
First, find the file named "signatures.xml". If you have an installed copy of the app, you'll find it there, inside a directory called META-INF. (It may be a couple of levels down.) If you only have the .air file, change the extension to .zip, open it in a zip tool, and you'll find the same signatures.xml file.
Then, open signatures.xml in a text editor or word processor. You can ignore most of what's in there; just search for the string "SignatureTimeStamp". If it's there, you've got a timestamp. If not, you don't.
hope that helps,
Awesome, thank you so much. Checked the file and there was no
timestamp which explains our problem. Thanks again.
We just ran into the same problem mentioned by the OP. I searched the signature.xml file for SignatureTimeStamp, and it is present. Could you please advise?
Well, if the timestamp is present, then you most likely haven't run into exactly the same problem.
When was your application signed? Published? When did your certificate expire, if it has? Does the failure occur for all installs, or only some? Also, it may be helpful to obtain an installation log file from one of the failing installs.
Thank you for your reply. The Thawte certificate expired June 27,
2010. The failure occurs for all installs (we have released 14
updates). When opening all versions of the app, we receive the same
The application could not be installed because the AIR file is
damaged. Try obtaining a new AIR file from the application author.
We got the certificate 2 years ago. I am attaching a screenshot of the
mac console log. The issue was brought to our attention by a customer.
I am running 10.5.8.
I don't see an attachment.
Which version of AIR is installed on the machines with this behavior?
My machine has version 2.0 of AIR installed. For our clients (who are
new), I'm assuming that they have the latest version installed. The
app was most recently published with version 1.5.2 required.
I believe this is the line you would be looking for in the console:
7/2/10 5:06:49 PM com.apple.launchd
exit code: 7
I am attaching the png again.
Are you accessing the forum via email, or web? I believe email attachments don't work, and need to be uploaded via the web interface.
The log entry you identified is too late in the sequence to pinpoint the problem; there should be quite a few earlier entries as the install is processed.
Sorry. I'm just responding via email. I'll update the forum article now.
That entry is from Flash (Flex) Builder, and also has nothing to do with the AIR application install. Do you see any entries originating from a process called "Adobe AIR Application Installer"?
The application was initially signed and published in June 2008. Since then, we have released numerous updates to the application (Currently at version 1.8.2). Our last update to the application was In October of 2009. Since our initial launch, we have targeted Adobe AIR versions 1.0, 1.1, 1.5, and 1.5.2. The version targeted Adobe AIR 1.5.2.
Going through the archive of past installers, I get the error message mentioned for all versions of the application.
I'm afraid it's still not clear to me where the problem might be.
1) When you packaged your application, did you specify an alternate timestamp server URL?
2) You should see quite a few more log messages in the console if you have AIR 2 installed and open a .air file. Do you see more messages if you try installing an app other than your own?
3) Which version of the AIR SDK are you using to package your application?
4) Can you post a copy of your application? It would likely help a lot if we could take a look at it directly.
1. When we published it from Flex Builder 3 via export release build, I selected the timestamp option on the Digital Signature page
2. I believe I was looking in the wrong place (Console Messages). I went to all messages, and have attached a screenshot of that output.
3. Using version 1.5.2 of the SDK to publish
4. You can download the application here.
Thanks for your assistance,
Thanks for providing a download link. I examined the signature in that file and discovered that it does not contain a timestamp. You mentioned earlier that you were using timestamping. Is it perhaps possible that only some of the .air files you've created had timestamps enabled?
I went back through every air file generated over the past two years, and it is indeed a hodgepodge of some timestamped and others not timestamped. The ones with timestamps do indeed work. Thanks for your time and patience.