How do we access our update.xml file to provide descriptions of whats in an update?
Also, if a published app used an older configuration namespace 'http://ns.adobe.com/air/framework/update/configuration/1.0' - when getting ready to update can we change that to 'http://ns.adobe.com/air/framework/update/configuration/2.5' and not cause any problems?
let me answer these two questions separately.
Passing in a descriptions to the update.xml is something that we currently can't do. But it is an interesting feature request and I will take it back to the product team. We generate the update.xml file dynamically based on the approval state of the application and the information we hold in the repository.
As for the second question, instead of giving a longer answer I want to direct you to the section we added to the documentation once we started supporting AIR 2.5. (http://learn.adobe.com/wiki/display/InMarket/04+Updating+your+applicat ion+to+AIR+2.5)
We also have follow the approach that AIR lays out and updating an application from pre-AIR 2.5 to a AIR 2.5 application (or higher). Requires an interim application. You may also want to look at the updated section 4.8 (http://learn.adobe.com/wiki/display/InMarket/4.8+Configuring+your+appl ication+for+updates) because the format for the url element in the updateConfig.xml has changed for AIR 2.5 applications.
I hope this answers your questions
For this one, does it affect your answer if I tell you that everything about
the initial application submission was 2.5 EXCEPT the namespace in the
updateConfig.xml file itself? I don't mind leaving it at 1.0, but I have
ADD in that I like everything to be uniform That being said, if I don't
follow these steps and leave the namespace inside the updateConfig.xml file
as 1.0 - will I not be able to publish an update and/or will users not be
able to update?
If you are talking about the namespace of the updateConfig.xml ... that has never changed and is still
So you have to write
<?xml version="1.0" encoding="utf-8"?>
regardless of whether the app is build with for AIR 1.5.3, 2.0 or 2.5.
The URL I was referring to was the content of the <url> element in that file. For AIR 2.5 applications we started mandating a different pattern for the url
which is described in more detail in the section 4.8. of the documentation.
So, if you leave it as it is you will be able to update your application. We do validate the updateConfig.xml file of your application upon upload.