Apr 27, 2011 8:03 AM
application update problem after switching to air 2.6 sdk
-
Like (0)
Hello all,
Until now I compiled my air app with the Air 2.5 sdk.
Accordingly, my update.xml file used the following namespace: <update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
And the adobe update mechanizem worked great!
Now I want to switch to Air 2.6 sdk.
My compilation works, but when I switch the namespace to: <update xmlns="http://ns.adobe.com/air/framework/update/description/2.6">
I don't get an update.
When I ran the application in debug mode (FB4), I noticed the following error in my console: "updater error unknown update descriptor namespace".
Why does is not recognze the 2.6 namespace? Can anyone think of a reason for why this happens?
p.s
If I switch the namespace back to 2.5, I get the update window, but it fails to update (understood since the app is now compiled with the 2.6 sdk)
I believe you'll want to keep your updater xml set to 2.5. I'm using this on an app built with 2.6, though I admit that it took a bit of trial and error on my part. What error message do you get when you do run against 2.5? Do you mind posting the contents of your update.xml file?
Thanks,
Chris
I get "Download failed" and "There was an error downloading the update. Error# 16824"
The update.xml (after I changed it back to 2.5 namespace):
<?xml version="1.0" encoding="utf-8"?>
<update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
<versionNumber>0.9.924</versionNumber>
<url>[url to product name]</url>
<description>
<text xml:lang="en">
[description...]
</text>
<text xml:lang="ru">
</text>
<text xml:lang="de">
</text>
<text xml:lang="pt">
</text>
<text xml:lang="cs">
</text>
</description>
</update>
What do you mean that it took some trial and error? how did you make it work?
And also, isn't this a bug? it makes sense to me that an app compiled with the 2.6 sdk will need the 2.6 namespace
I just tested another scenario:
If I make another version of my app (with the 2.6 sdk) and update from the previous version of my app (also built with the 2.6 sdk), I update successfully (still when using the 2.5 namespace in the update.xml and not the 2.6... but whatever).
So it seems that the problem is updating from an app compiled with 2.5 sdk to one complied with the 2.6.
Could this be?!
I did not run into this problem when I updated my app from the 2.0 sdk to the 2.5 sdk.
I'm not exactly sure what I did, though it's possible that it ended up being what you suggested. I might have just built a 2.6 app, then updated with a newer 2.6 version. I was trying a number of things to correct the problem and wasn't as methodical as I should have been (this was after 6 hours of continous coding on Easter and my wife was "urging" me to stop
)
I've asked the team responsible for the Updater Framework to take a look at this thread so hopefully we'll find out more soon. I'll also try and find some time to try and recreate the problem.
I have a similar issue with implementing the updater on Windows XP
AIR Runtime installed 2.6.0.19140
adl.exe Version 2.6.0.18830 2.6.0.19120
update.xml
<?xml version="1.0" encoding="utf-8"?>
<update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
<versionNumber>1.3</versionNumber>
<url>http://www.url.com/app.air</url>
<description>
<text xml:lang="en">Version v1.3</text>
</description>
</update>
updateConfig.xml
<?xml version="1.0" encoding="utf-8"?>
<configuration xmlns="http://ns.adobe.com/air/framework/update/configuration/2.6">
<url> http://www.url.com/update.xml</url>
<delay>0</delay>
<defaultUI>
<dialog name="checkForUpdate" visible="false" />
<dialog name="downloadUpdate" visible="true" />
<dialog name="downloadProgress" visible="false" />
<dialog name="installUpdate" visible="true" />
</defaultUI>
</configuration>
Throwing the following error for
updater.addEventListener(ErrorEvent.ERROR, onError);
So for now it seems that for my update to work I should continue using the 2.5 namespace in both my app.xml file and update.xml. (that's a shame... :q)
I hope this issue will rezolved quickly.
Thanks for the reply ![]()
One more thing I'd like to understand:
Let's say I compile my application using the 2.5 namespace in the files mentioned above. If my user runs it with the AIR 2.6 runtime, do all the improvements made in 2.6 (such as performance) take effect?
For those following along, I've got a small update. It appears that this was a known issue in 2.6, but there is a solution. I don't have detailed steps yet (the team that works on this is based in Europe, so I should have either a link to a knowledge base article or detailed steps tomorrow) but I've heard it's something like: "users must first update their current app with an application that contains the new application updater framework (the one from AIR 2.6) and after that make another update to their app with the 2.6 NS."
I'll post again as soon as I learn more.
Chris
Thanks for the update and the info that you the team is on it.
Though I'm not sure if this solution works for me since I'm developing a new application right now, so its not deployed yet. I have the update-issues in debug and release builds that I launch from Flex Builder. I'll give it a try again soon and keep watching this post here.
Hi Matt,
In the updateConfig.xml, could you try changing
<configuration xmlns="http://ns.adobe.com/air/framework/update/configuration/2.6">
<configuration xmlns="http://ns.adobe.com/air/framework/update/configuration/1.0">
Here are some additional details. Due to a bug in the AIR 2.5 application updater framework (internal bug #2793950), updating 2.5 applications to 2.6 still requires a three step process. However, this should be in no way different from the three-step process needed to update from 2.0 to 2.5.
The original KB article can be found here:
http://kb2.adobe.com/cps/873/cpsid_87300.html .
An article describing the process when using Flash Builder can be found here:
I hope this helps and please us know if you run into any issues.
Thanks,
Chris
Hi Chris,
thanks for finding this little number-error. Works for me now this way with the 2.5 SDK .
I am alos having same problem.. update manager not working for 2.6 descriptor... it was fine up to 2.5 any idea...?
Shiju Varkey wrote:
I am alos having same problem.. update manager not working for 2.6 descriptor... it was fine up to 2.5 any idea...?
Hi Shiju,
Did the steps and documents that I referenced in this post help you at all?
http://forums.adobe.com/message/3653528#3653528
Chris
Hello chris..
i tried all the options as mentioned above .. but not working
also the urls you mentiond for reference---http://kb2.adobe.com/cps/873/cpsid_87300.html .....http://www.adobe.com/devnet/air/articles/air_update_framework.html#art iclecontentAdobe_numberedheader_4
not working now
any idea???
Sorry about the broken links. Not sure what happened there. They should be fixed now.
Chris
Finally fixed the problem..
May 4, 2010
is the fix for the issue.. My issue was i was testing the aplication works or not just by changing it in update.xml(this testing was successfull in my previous projects upto 2.5), I assuming this technique changed and each time you want to test with a new update first compile the project with new verson umber then update the xml..this will work
Thank you
North America
Europe, Middle East and Africa
Asia Pacific
Copyright © 2011 Adobe Systems Incorporated. All rights reserved.
Use of this website signifies your agreement to the Terms of Use and Online Privacy Policy (updated 07-14-2009).