How do I migrate certificates for my AIR application that uses a native installer? - air

I have an Adobe AIR application that I package in a native installer for Windows. I just got a new certificate to sign it with and signing it with the new certificate works fine. However if I try to install it on a computer that has a previous version I get an error that the installer has been misconfigured.
If I uninstall the previous version, the installation works fine.
I've looked at the ADT tool and there is a -migrate (Adobe docs) option where you first package and sign an air file with the new certificate and then use the adt -migrate command to sign the air file with the migration (old) certificate. But this won't work because I'm not able to package my app to a .air file since it uses NativeProcess.


I was finally able to use the adt -migrate command. I had to remove the tag from my program-app.xml file. After I did that, I was able to package to an air file without getting an error about the supported profiles. I followed the Adobe docs for the rest of the packaging process and this time installing over the old version didn't result in any errors.

Related

OS X - app can't be opened because the identity of the developer cannot be confirmed when bundle includes new version of third-party executable

I have an app which has a third-party executable in its bundle resources. I used to sign the app during release phase and distribute outside of Mac App Store. All is fine. After I have updated the third-party executable, once app is signed as usual and downloaded from website to mac, OS X shows alert "app can't be opened because the identity of the developer cannot be confirmed".
I tried signing third-party executable before signing an app: didn't make a difference.
If I replace new third-party executable with an old version (resign and redownload) - app warning is not showing and everything is fine.
"codesign -dv app" shows reasonable identical output for signed app bundle with old or new version of a third-party executable.
App is signed with a valid Mac Developer Id.

Check if all the binaries in your bundle are not referring to libs outside of /usr/bin or /System.
In our case we had one with an absolute path and GateKeeper would not allow it to be run. codesign --verify was useless.
You can use the following command:
otool -L path_to_binary
If you see any dependency outside of /System or /usr/bin - get rid of them

Installing .air Application Silently

I am trying to install Adobe AIR along with a .air file as one package in ManageEngine Desktop Central 10 silently. I have gotten as far as silently installing Adobe Air using the command/switch: AdobeAIRInstaller.exe -silent.
Then, I created a post-deployment script (filename.air -eulaAccepted -silent) in ManageEngine. Adobe AIR installs silently and flawlessly, but the .air file simply opens up with the installation prompt. I have also tried various silent install switches tailed to the .air file within the command prompt, but to no avail.
Anyone have any ideas?

Try something like:
"%ProgramFiles(x86)%\Common Files\Adobe AIR\Versions\1.0\Adobe AIR Application Installer.exe" -silent -eulaAccepted "filepath\filename.air"
Good Luck!

Cannot uninstall a plugin Eclipse Luna or reinstall it

Using the marketplace I installed a plugin (additional axis 2 tools) on a new Luna EE install.
I uninstalled it via the market place, and after a reboot it was still there. Tried this many times.
So I deleted the file manually from the plugins folder and the option was gone.
However, I want to reinstall it (I originally uninstalled it because the dialog kept containing the wrong information and stopping me from building aar file), but when I go to the marketplace it only gives me an option to 'uninstall'.
Ignoring how this is a bit crap, how do I remove this plugin so I can install it again?
I tried downloading the 1.6.2 jar direct from apache but it just gives me an error saying invalid jar repository.
(I know I can generate the service file/aar manually, but I want to do it this way).
thanks.

Go to Help, Instillation Details and try to remove it from installed software and then try to install it again.This works for me whenever I've to uninstall any software.

Metro App Certification hangs on performance test because of byte code generation

I try to build a metro-style-app with Javascript and when I run the Windows App Cert Kit (WACK) Certification tool the test always fails on the performance test with the following message:
Following errors were detected when tested the byte code generation:
This package was made available for the development or Authoringmodus. Uninstall the package and reinstall it in the normal way.
I’m using jquery and some jquery-mobile libraries inside my app. Is that the problem? The error doesn’t make sense for me, because it doesn’t say which package I should reinstall. I also try to uninstall the App itself (by right click onto the app) and build it again in the Release-Modus of VS2012, but the WACK tool always prompts this error :(

Find out that the WACK Tool allways shows this error if you don't run Store -> Create App Package and select "No" and press the next button. After that the WACK-Tool is started automatically and it passes the bytecode generation.

First save the all javascript files with encoding utf 8 format with signature
then create the app package
http://msdn.microsoft.com/en-us/library/windows/apps/hh975357.aspx
then if u already install the latest windows app certification kit then u will be able to see run with windows app certification kit button after creating app package .

Installing of Adobe Air file fails with "file damaged"

Adobe Air brings following exception:
The application could not be installed because the AIR file is
damaged. Try obtaining a new AIR file from the application author.
Please add the different reasons which may lead to this error.

We had the same error as this guy:
The file ~/.airappinstall contains the following error:
failed while unpackaging: [ErrorEvent type="error" bubbles=false
cancelable=false eventPhase=2 text="invalid package signature"
errorID=5022]
The actual reason was not a damaged file or something like this, but our machine had a date from the past, which was not valid for the given certificate. After correcting the date/time on the computer, the installation worked just fine.

Even I faced the same error=5022, after thinking a lot on this issue, I finally got the
solution for this problem. It is simple, before installing the air app set the correct Date & Time for the system, WALLA it installs smoothly.
No need of changing the png name or anything else.

I faced this problem yesterday because my antivirus (avast pro/silent mode) was blocking access to file until finishing scanning, looks like installer don't like to wait, so when I switched off silent mode I made antivirus ignore scanning the file and installation completed successfully.

I have a virtual drive mapped to S: so that paths are the same between my home computer and work computer. I was trying to install the AIR app from an S: path. I guess it did it like it. Moving app to my desktop and launching there, worked.

Make sure you are signing the Application distributable and distributing the certificate along with the .air file.
I ran into same problems and solved it this way.

I had this issue when using Flash Builder 4, but building a Flex 3 application.
Basically, the installed AIR SDK in the Flex 3 SDK folder was AIR 1.5.3 (if I remember correctly), but the Flex 4 SDK folder had the AIR 2.0 SDK files (I'm not completely what the problem was).
My solution was to download the AIR 2.0 SDK, and unzip it over the Flex 3 SDK folder. Once I did that, the installation file worked fine. There is actually an article on Adobe about overwriting the AIR SDK files this way, although it didn't mention anything about installations or Flash Builder 4.

Mine was failing because I had another app on my system with the same name. Not a version of the app, a completely different app--native, not AIR.
Once I removed that app it worked fine.

For odd installation errors, keep in mind that Chrome uses a version of Flash that does not support AIR badge installation.

I encountered this error when trying to install an AIR file from an external / network drive. Copied the file locally, and installation proceeded normally.