One AIR annoyance

This post is more than 2 years old.

So this is a minor nit - I really do love AIR, but I've noticed something funny. I go to install an application - one that I've installed before, and the installer tells me:

Ok, no big deal, I'll just move the old file or pick another file, but nope, you can't do that, because the installer dies right there! Why not let the user go back and correct the install folder? Or move the file? Sure it takes me all of 5 seconds to do this and rerun the installer, but I wish it wouldn't abort the process because of a simple problem like that.

Ok, so this isn't a complaint just about AIR - I've seen other applications do this as well, but I figured that if I complain about it, maybe someone will point out that I simply created my installer wrong.

Raymond Camden's Picture

About Raymond Camden

Raymond is a senior developer evangelist for Adobe. He focuses on document services, JavaScript, and enterprise cat demos. If you like this article, please consider visiting my Amazon Wishlist or donating via PayPal to show your support. You can even buy me a coffee!

Lafayette, LA https://www.raymondcamden.com

Archived Comments

Comment 1 by salvatore fusto posted on 3/27/2008 at 6:13 PM

ray,
may be you have to update the old app.
salvatore

Comment 2 by Raymond Camden posted on 3/27/2008 at 6:16 PM

I don't think it's an update issue - but a name conflict issue.

Comment 3 by Gareth posted on 3/27/2008 at 6:22 PM

I thought I saw the option to uninstall the previous app when I tried to install an AIR app recently (I thought it might have checked the version also, but I'm not positive). I could be completely dreaming though :)

Comment 4 by Sidney de Koning posted on 3/27/2008 at 6:50 PM

I had this box appear a couple of times to my app. What killed it was the inconsistency in version numbering. (in the XML descriptor file). To fix it; just increment the verison number with a point (1.0.1, 1.0.2 etc)

Comment 5 by Sidney de Koning posted on 3/27/2008 at 6:52 PM

<pressed submit to fast>
What you get then is when installing, saying that there is a conflict, since you have version 1.0.1 and it wants to install 1.0.2. Then you get prompted with the choice to either overwrite or keep the file.

Hope this works for you,

Cheers, Sidney

Comment 6 by Raymond Camden posted on 3/27/2008 at 6:53 PM

But that's not my point SIdney - and again - other apps do this as well. Why should the installer just stop? Yes, it can't install there - but it should ask me to provide a _new_ location.

Does that distinction make sense?

Again, I'm being picky - I _love_ AIR.

Comment 7 by David McGuigan posted on 3/27/2008 at 10:03 PM

No, you're right.

I don't think it should even say "an error has occured".

What it should do is DETECT beforehand and just tell you that "an application with that name already exists at the select location", then give you an editable text field pre-populated with a variation that will make the install work (ex: previousAppName_2) as well as cancel, "overwrite the previous installation", and "choose a new installation directory" buttons.

But it's AIR 1, so I'll pretend I never noticed and still tell everyone that AIR is perfect and the solution to all of the world's problems.

Comment 8 by Gareth Edwards posted on 3/28/2008 at 2:11 AM

Something looks wrong here, this is the text that I see when trying to install your application more than once.

"The same version of the application you opened already exists on this system.

Would you like to run the version already installed?"

If you are updating your application, it is advised that the version number in your app.xml changes so that the air runtime can treat it as an update.

Comment 9 by Gary Funk posted on 3/28/2008 at 6:48 AM

Ray, I have had the same error and I can only think that is is because the previos version was installed under one of the AIR betas. On some machines I've had to go into the registry and rip out the guts.