Adobe Updates AIR, for Flash CS3, “The application requires a version of the Adobe Integrated Runtime which is no longer supported” December 14, 2007
Tried publishing in the Flash IDE to AIR this morning and it output...blank space. Left me scratching me head for a bit, tried another air app, and got this.
Turns out that AIR had been updated like yesterday. But this requires a few steps to fix Flash CS3's publish for AIR. Instructions are spread across here.
- http://www.adobe.com/support/flash/downloads.html#flashCS3
- http://labs.adobe.com/wiki/index.php/AIR:Flash_CS3_Professional_Update#Download_and_Install
Which was far more involved than I was expecting, you have to uninstalled some things manually, and then to execute a jsfl script to cleanup afterward. To compound things, the updates want Firefox to be closed down, which have the instructions on it.
After all that....my file still didn't publish as AIR. Weird as it is, renaming the file allowed it to publish again *scratches head*
Gripe.
I realize AIR is beta, and it offers some really amazingly cool features. But it bums me out a little that the few AIR apps I've got installed are now all broken, and it's unknown if they will be updated in a timely fashion, being mostly in the widget, experimental category. Uninstalling isn't hard but it is annoying.
I find it also a bad user experience, if I can't get to the help/about to of an oddball named AIR app, to remember where I downloaded the widget in the first place, due to the above dialog, which isn't particularly helpful either in the user resolving the situation (like where to download the latest version). It makes me less gung-ho about delivering AIR products, if whatever I release can break in the wild at any time at Adobe's discretion.
1 responses to 'Adobe Updates AIR, for Flash CS3, “The application requires a version of the Adobe Integrated Runtime which is no longer supported”'
My apologies for the rough upgrade experience. I think you actually ran into a couple of separate issues here: The update to beta 3, and the expiration of beta 1.
The dialog you’ve included in your post is what users see when they try to run applications on the now-expired beta 1 runtime. Now, let me be really clear about this: all of our beta releases are going to expire, but final releases (i.e., 1.0) will NOT expire. We’re not so silly as to just go breaking people’s apps for no good reason.
Why do the betas expire at all? So that we can put our resources into the final releases, like 1.0, and not spend time maintaining the betas. For example, if beta 1 hadn’t expired and someone discovered a vulnerability in it, we’d have to issue a patch. We’re just not interested in spending our time on that.
That the beta 3 updates came out at the same time as the expiration is a coincidence–it’s not your upgrade to Flash CS3 that disabled the beta 1 apps. I can’t speak to the Flash CS 3 upgrade issues in particular, but I will say those teams have a tough job because they get squeezed between when we freeze the AIR code for a given release and they have to get their extensions done.
Oh, one more thing: the expiration dates for all of the beta releases are clearly documented in the AIR FAQ on labs.adobe.com. You might want to keep the beta 2 and beta 3 expiration dates in mind.
regards,
Oliver Goldman
Adobe AIR Engineering
Adobe Systems Inc.
Add a Comment: