ADT migrate command

Forum|Forum|13 years ago
September 28, 2012
9 replies
1572 views

This question was posted in response to the following article: http://help.adobe.com/en_US/air/build/WS901d38e593cd1bac1e63e3d128fc240122-7ffd.html

Performance issues

This topic has been closed for replies.

R

reidmweber

Participating Frequently

Is there a way to apply a migration certificate to a native installer on Windows? I can't build to a .air package because my program uses NativeProcess and requires that only extendedDesktop profile be supported. If I just sign the native installer with my new certificate, I get an error when I try to install over the old version saying the installer has been mis-configured. It installs fine after an uninstall of the old version so I think the error is because the certificate has changed.

I've also tried preparing an .airi intermediate file but I can't sign that with the adt -sign command for the same reason (NativeProcess).

A

active_customer16B8

Adobe Employee

You need to add the desktop profile to the supportedProfiles tag. Once you do that, you can package the AIR file. Then migrate the AIR file. and use adt -package -target native out yourApp.air

to convert the AIR file into the native installer.

M

mariahbailey

Participant

I'm having the same issue as reidmweber. We had to renew our code signing cert and are unable to install over the existing application with the newly-created native installer.

I tried the recommendation of adding the desktop profile to the supportedProfiles tag and then migrating the .air app to .exe, but I still get the same error ("This application cannot be installed because this installer has been mis-configured.").

I should mention that I had to include both the desktop profile and the extendedDesktop profile because the migrate command (adt -package -target....) threw an error without the extendedDesktop profile. The error is "Descriptor is invalid for native install....the app must support the profile extendedDesktop".

I keep thinking there must be a way to create the native installer such that end-users won't have to first uninstall and then re-install. If there are any additional ideas, please let us know. Thanks!

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.