I created a new air project in aptana but launching it gets me
This application requires a version of the Adobe Integrated Runtime (AIR) which is no longer supported. Please contact the application author for an updated version.
How does one go about updating the application for a newer version of air? I suspect it is related to
<application xmlns="http://ns.adobe.com/air/application/1.5">
in the application.xml
You installed the AIR 1.0 runtime, mostly sometime before Frebruary 2009. AIR 1.5 was launched on around the last week of February. The runtime installer does check for updates. You will need the updated runtime.
There should be a link where it tells you to update the application (when you launch your application). Just click on it and install the new version of the runtime. In case you missed it -- here's the link.
Read more about AIR 1.5 here.
If I missed the real question -- let me know!
Related
I followed the recommended solution:
IBM Worklight v6.0 - Error while adding an application to the Mobile Test Workbench
still got the error even though my jdk seems to be already correct
I didn't see any errors in the test workbench mobile client log (emulator), which log should I be looking at?
I suppose that you are using Android 4.4 and not Android 4.4W or 4.4L which are not yet supported. And you should have made recently an update of the Android SDK tools to version 23 (you can verify by opening the SDK Manager)
Google has modified in this release the way the tools are organized and this made MTWW regressed when instrumenting.
There is a workaround: copy <android-sdk-dir>/build-tools/20.0.0/zipalign[.exe] to <android-sdk-dir>/tools.
Dominique
I had same problem. You may need hotfix or uptdate to RTW8.6.
https://www-304.ibm.com/support/docview.wss?uid=swg21678859
With the new firefox we are shipping more and more libraries as the XPom interfaces we interact with are changing. We are at 10 dlls and increasing, each with a size of almost 2M.
This size is a concern for some users.
While we look at restructuring the library to seperate the parts we can make common between them, we are thinking about how we might reduce space on the disk while supporting version upgrades.
For instance, user has FireFox 3.6 and 4.0 installed and when our product is installed we install a dll for each version. When Firefox is 4.0 upgraded (say to 6.0) how might we now install from the msi the missing dll for 6.0 support.
Any ideas on how we could achieve this?
Are we worrying for no reason?
My first thought was we 'AllowAdvertise' and when FF tries to load the dll as directed by chrome it will cause the install, it doesn't seem to work.
My first reaction is to suggest that you move away from XPCOM and towards js-ctypes. After all, this is the direction that Mozilla is pushing extension developers (see Wladimir Palant's comments for example). If there isn't anything in your binary code that absolutely positively requires use of XPCOM, you'll be much happier to ship a DLL that interfaces with JS when needed via js-ctypes.
I guess that your extension is Windows-only so supporting multiple platforms is not an issue. A possible short-term solution:
Have a separate extension package for each Firefox version, mark it as compatible with this Firefox version only (e.g. minVersion 4.0 and maxVersion 4.*).
When your extension is installed, install the version that is compatible with user's installed Firefox version.
Make sure that your extensions have an updateURL entry that is pointing to your server. It is important to have %APP_VERSION% in the URL.
Make sure to test Firefox betas and prepare a new extension version in time for the next Firefox release (releases are scheduled on Tuesdays every 6 weeks, next release being on September 27th).
Configure your server to indicate different packages as updates depending on the Firefox version used. So an update check with %APP_VERSION% 4.0.1 would be sent to extension-ff4.xpi while %APP_VERSION% 6.0 would get extension-ff6.xpi.
Firefox will always check for extension updates when the application is updated. If you can give it a compatible update it will install it. But preparing new packages every six weeks requires tons of effort and I guess that you want to refactor your code/move to js-ctypes ASAP. Oh, and I think that you need to ignore the unlikely scenario that some user has more than one Firefox version installed.
I use FlashDevelop as my code editor and the Flash CS4 IDE for publishing my AIR files (as well as asset control, animation creation etc...). The bonus of this is the Flash IDE handles all the crap of creating certificates and whatnot very easily as well.
Flash CS4 uses Adobe AIR 1.5, which is very old and I am wanting to update it to AIR 2.6, which as of current writing, is the latest version of AIR. Also, I don't know if this is of any significance, but I would like to publish AIR apps for Android now. I've successfully made an AIR app for PC in the past, using AIR 1.5.
I downloaded the AIR 2.6 SDK from the Adobe website and replaced all the files inside the "AIK1.5" folder of my Flash installation (the folder being still named 1.5 inherently annoys me).
Is there any other steps I must take? Because I'm not convinced I'm publishing AIR 2.6 apps as the application.xml file in my AIR project still reads:
<application xmlns="http://ns.adobe.com/air/application/1.5">
If I change the version in the .xml, Flash explodes (doesn't compile, gives me an error).
Furthermore, if I go File > Publish Settings, then the Flash tab, the player field reads as "Adobe AIR 1.5". Is this right? I'm assuming this will always be this way, even if you do successfully update the AIR version, since apparently Adobe is too lazy to update CS4 so that it can logically figure out it has the new version of AIR.
Also, if AIR is free, why the hell does Adobe not at the very least, release updates to CS4 that update the version of AIR it uses. This seems to be fully within their power, and it seems incredibly negligent that they don't do this for people who have bought their software.
Please, if you could provide clear step by step help, because I'm very ignorant when it comes to development configurations and stuff. I just want to write code and be off.
UPDATE
Once you've updated Flash's AIR library with AIR 2.6, and have compiled your AIR project, make sure you use the new application descriptor template from the AIR SDK. I originally thought it just required changing the version number from 1.5 to 2.6 or whatever new version you're using. As seen below.
<application xmlns="http://ns.adobe.com/air/application/1.5">
But the format as changed, and you really need to use the new template, otherwise it won't work. And when you compile you won't automatically get a preview of your compiled .swf. This will happen in FlashDevelop too if you've set-up your descriptor file incorrectly.
Bzzzzzzt wrong you can hack apart your CS IDE and get it working follow the concepts in this tutorial, they should get you going and you should be able to piece it together from there.
http://swfhead.com/blog/?p=16
If you have any problems just post a comment I'll help you sort it.
You will need to purchase the latest version of Creative Suite or Flash/Flash Builder to take advance of the latest versions of AIR.
Like any other software, releases are versioned with specific features and newer versions support newer features and integration into other newer technologies.
Its like Microsoft is well in their power to provide docx support in windows 2003, but that would just cause compatibilty, support and licensing issues.
These are the tutorial for Flash cs 5:
http://blog.prevail.co.nz/2011/06/21/overlaying-air2-7-in-flash-cs5/
These are the tutorial for Flash cs 5.5:
http://www.yeahbutisitflash.com/?p=2949
http://helpx.adobe.com/x-productkb/multi/overlay-air-sdk-flash-professional.html
This is the tutorial for Flash cs 6:
http://www.leebrimelow.com/?p=3335
I downloaded Carbide.c++ 1.2 and also downloaded the SDK S60 2nd Edition CW.
I installed the SDK and it is recognized in the Window->Preferences->Carbide C++->SDK preferences.
but when I try to create a new project, the templates related to the SDK aren't displayed.
and the editor seems not to detect the SDK.
has anyone ever experienced this ?
how do you solve it ?
Attilah, these are quite old versions of both the SDK and Carbide. But if you need to develop an app for an S60 2nd edition device this makes sense. I don't have either of this installed currently, so it's hard to diagnose exactly.
You said the SDK is recognized. In the SDK preferences, if the checkbox next to the SDK is turned off then the SDK is disabled. Make sure it's enabled.
One thing you could try is to turn of the "Filter templates based on enabled SDKs" checkbox in the new Symbian OS C++ project wizard.
Also, you could try importing one of the example apps from the SDK to confirm you can import and build the project OK.
If you decide to do any work with 3rd or 5th edition phones then you can get the latest Carbide from http://developer.symbian.org/main/tools_and_kits/downloads/view.php?id=2
I have written an HTML/AJAX application with Adobe Air and run it on my WinXP laptop. But now I've released a newer version on my update site, the application downloads the update and says "The application could not be installed because the AIR file is damaged. Try obtaining a new AIR file from the application author."
I've tried repackaging the application and incrementing the version number but that hasn't helped. I am creating it in Aptana Studio on OSX.
Can anyone explain please what could cause that error?
I haven't worked with aptana but...
in adobe flex builder, you have to change the first line of the file: "applicationName-app.xml". (where applicationName is the name of your application or project)
When you change from pc to mac-osx you have to change the line:
<application xmlns="http://ns.adobe.com/air/application/1.1">
to
<application xmlns="http://ns.adobe.com/air/application/1.5">
Don't know if you have this file when creating a project in aptana... maybe in the project properties.
Then repackage and deploy.
I just ran into the same problem. After trying every "solution" mentioned on every blog on the planet it occurred to me that my server didn't have .air as a recognized MIME type. Once I added this, all was well.