AIR auto-updater -- include markup?

I have had my AIR application able to auto-update for some time.  But I'm wondering if you can somehow include HTML in the description you see of the auto-updater.  Here is my update.xml file on the server:
<?xml version="1.0" encoding="utf-8"?> 
<update xmlns="http://ns.adobe.com/air/framework/update/description/1.0">
  <version>1.0.0</version>
<url>url-to-air-installation-file</url>
   <description><![CDATA[Text of new things in this version....   ]]></description></update>
I've tried to remove the <![CDATA[ and use HTML inside the <description> block, but it doesn't work.  Am I missing something?  Is this even possible??
Thanks,
Ian

Just Got The Solution for Error 16811 &  16816
Note Following things to avoide update error
No 1.>
You xml schema for update descriptor.xml in  server should look similar to this
<?xml version="1.0" encoding="utf-8"?>
<update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
  <versionNumber>2.0</versionNumber>
  <url>http://localhost/SerialHunter/SerialHunter.air</url>
  <description><![CDATA[
SerialHunter Version 2.0 by Rajendra Khope
This new version includes:
    * AutoUpdate
    * Enhaced UI functions
    * Ability to add providers       
  ]]></description>
</update>
Note xmlns="http://ns.adobe.com/air/framework/update/description/2.5"
and versionNumber instead of version
Also make similar changes in appxml version field (in Burrito its by default versionNumber )
No 2>
if u are using code to display veesion number make sure it should look like:
var appXML:XML = NativeApplication.nativeApplication.applicationDescriptor;
var ns:Namespace = appXML.namespace();
pnlMain.title=appXML.ns::name+" v "+appXML.ns::versionNumber
Thats it...!
Rajendra Khope
bkrajendra at gmail dot com

Similar Messages

  • Air Auto Update Error -- Flash Builder Burrito.

    This is my first attempt at this, so I may be missing something simple.
    I'm not having any luck getting an Air app to automatically update.
    If I manually go to  http://localhost/air1/air1.air and redownload the file I will get a popup that asks if I want to update the app, but when I say ok I get this error.
    "There was an error checking for updates. Error# 16816"
    I haven't found a reason yet,
    Any ideas?
    update.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
      <version>2.0</version>
      <url>http://localhost/air1/air1.air</url>
      <description>1.0 - First version</description>
    </update>
    file -- air1.mxml
    <?xml version="1.0" encoding="utf-8"?>
    <s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009"
                           xmlns:s="library://ns.adobe.com/flex/spark"
                           xmlns:mx="library://ns.adobe.com/flex/mx"
                           applicationComplete="init()">
        <fx:Declarations>
            <!-- Place non-visual elements (e.g., services, value objects) here -->
        </fx:Declarations>
        <fx:Script>
            <![CDATA[
                import air.update.events.UpdateEvent;
                import air.update.ApplicationUpdaterUI;
                import mx.controls.Alert;
                protected var appUpdater:ApplicationUpdaterUI = new ApplicationUpdaterUI(); // Used for auto-update
                protected function init():void
                    // Check for update
                    this.checkUpdate();
                    Alert.show("checking update");
                // This function is triggered when the application finished loading.
                // Initialize appUpdater and set some properties
                protected function checkUpdate():void
                    // set the URL for the update.xml file
                    appUpdater.updateURL = "http://localhost/air1/update.xml";
                    appUpdater.addEventListener(UpdateEvent.INITIALIZED, onUpdate);
                    appUpdater.addEventListener(ErrorEvent.ERROR, onUpdaterError);
                    // Hide the dialog asking for permission for checking for a new update.
                    // If you want to see it just leave the default value (or set true).
                    appUpdater.isCheckForUpdateVisible = true;
                    appUpdater.initialize();
                // Handler function triggered by the ApplicationUpdater.initialize.
                // The updater was initialized and it is ready to take commands.
                protected function onUpdate(event:UpdateEvent):void
                    // start the process of checking for a new update and to install
                    appUpdater.checkNow();
                // Handler function for error events triggered by the ApplicationUpdater.initialize
                protected function onUpdaterError(event:ErrorEvent):void
                    Alert.show(event.toString());
            ]]>
        </fx:Script>
        <s:Button x="47" y="55" label="Button"/>
        <mx:ColorPicker x="61" y="119"/>
        <s:ComboBox x="77" y="216"/>
        <s:ComboBox x="77" y="185"/>
        <s:ComboBox x="77" y="154"/>
    </s:WindowedApplication>
    file  -- air1-app.xml
    <?xml version="1.0" encoding="utf-8" standalone="no"?>
    <application xmlns="http://ns.adobe.com/air/application/2.5">
    <!-- Adobe AIR Application Descriptor File Template.
        Specifies parameters for identifying, installing, and launching AIR applications.
        xmlns - The Adobe AIR namespace: http://ns.adobe.com/air/application/2.5
                The last segment of the namespace specifies the version
                of the AIR runtime required for this application to run.
        minimumPatchLevel - The minimum patch level of the AIR runtime required to run
                the application. Optional.
    -->
        <!-- A universally unique application identifier. Must be unique across all AIR applications.
        Using a reverse DNS-style name as the id is recommended. (Eg. com.example.ExampleApplication.) Required. -->
        <id>air1</id>
        <!-- Used as the filename for the application. Required. -->
        <filename>air1</filename>
        <!-- The name that is displayed in the AIR application installer.
        May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <name>air1</name>
        <!-- A string value of the format <0-999>.<0-999>.<0-999> that represents application version which can be used to check for application upgrade.
        Values can also be 1-part or 2-part. It is not necessary to have a 3-part value.
        An updated version of application must have a versionNumber value higher than the previous version. Required for namespace >= 2.5 . -->
        <versionNumber>2.0.0</versionNumber>
        <!-- A string value (such as "v1", "2.5", or "Alpha 1") that represents the version of the application, as it should be shown to users. Optional. -->
        <!-- <versionLabel></versionLabel> -->
        <!-- Description, displayed in the AIR application installer.
        May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <!-- <description></description> -->
        <!-- Copyright information. Optional -->
        <!-- <copyright></copyright> -->
        <!-- Publisher ID. Used if you're updating an application created prior to 1.5.3 -->
        <!-- <publisherID></publisherID> -->
        <!-- Settings for the application's initial window. Required. -->
        <initialWindow>
            <!-- The main SWF or HTML file of the application. Required. -->
            <!-- Note: In Flash Builder, the SWF reference is set automatically. -->
            <content>[This value will be overwritten by Flash Builder in the output app.xml]</content>
            <!-- The title of the main window. Optional. -->
            <!-- <title></title> -->
            <!-- The type of system chrome to use (either "standard" or "none"). Optional. Default standard. -->
            <!-- <systemChrome></systemChrome> -->
            <!-- Whether the window is transparent. Only applicable when systemChrome is none. Optional. Default false. -->
            <!-- <transparent></transparent> -->
            <!-- Whether the window is initially visible. Optional. Default false. -->
            <!-- <visible></visible> -->
            <!-- Whether the user can minimize the window. Optional. Default true. -->
            <!-- <minimizable></minimizable> -->
            <!-- Whether the user can maximize the window. Optional. Default true. -->
            <!-- <maximizable></maximizable> -->
            <!-- Whether the user can resize the window. Optional. Default true. -->
            <!-- <resizable></resizable> -->
            <!-- The window's initial width in pixels. Optional. -->
            <!-- <width></width> -->
            <!-- The window's initial height in pixels. Optional. -->
            <!-- <height></height> -->
            <!-- The window's initial x position. Optional. -->
            <!-- <x></x> -->
            <!-- The window's initial y position. Optional. -->
            <!-- <y></y> -->
            <!-- The window's minimum size, specified as a width/height pair in pixels, such as "400 200". Optional. -->
            <!-- <minSize></minSize> -->
            <!-- The window's initial maximum size, specified as a width/height pair in pixels, such as "1600 1200". Optional. -->
            <!-- <maxSize></maxSize> -->
        <autoOrients>false</autoOrients>
        <fullScreen>false</fullScreen>
        <visible>false</visible>
      </initialWindow>
        <!-- We recommend omitting the supportedProfiles element, -->
        <!-- which in turn permits your application to be deployed to all -->
        <!-- devices supported by AIR. If you wish to restrict deployment -->
        <!-- (i.e., to only mobile devices) then add this element and list -->
        <!-- only the profiles which your application does support. -->
        <!-- <supportedProfiles>desktop extendedDesktop mobileDevice extendedMobileDevice</supportedProfiles> -->
        <!-- The subpath of the standard default installation location to use. Optional. -->
        <!-- <installFolder></installFolder> -->
        <!-- The subpath of the Programs menu to use. (Ignored on operating systems without a Programs menu.) Optional. -->
        <!-- <programMenuFolder></programMenuFolder> -->
        <!-- The icon the system uses for the application. For at least one resolution,
        specify the path to a PNG file included in the AIR package. Optional. -->
        <!-- <icon>
            <image16x16></image16x16>
            <image32x32></image32x32>
            <image36x36></image36x36>
            <image48x48></image48x48>
            <image72x72></image72x72>
            <image128x128></image128x128>
        </icon> -->
        <!-- Whether the application handles the update when a user double-clicks an update version
        of the AIR file (true), or the default AIR application installer handles the update (false).
        Optional. Default false. -->
        <!-- <customUpdateUI></customUpdateUI> -->
        <!-- Whether the application can be launched when the user clicks a link in a web browser.
        Optional. Default false. -->
        <!-- <allowBrowserInvocation></allowBrowserInvocation> -->
        <!-- Listing of file types for which the application can register. Optional. -->
        <!-- <fileTypes> -->
            <!-- Defines one file type. Optional. -->
            <!-- <fileType> -->
                <!-- The name that the system displays for the registered file type. Required. -->
                <!-- <name></name> -->
                <!-- The extension to register. Required. -->
                <!-- <extension></extension> -->
                <!-- The description of the file type. Optional. -->
                <!-- <description></description> -->
                <!-- The MIME content type. -->
                <!-- <contentType></contentType> -->
                <!-- The icon to display for the file type. Optional. -->
                <!-- <icon>
                    <image16x16></image16x16>
                    <image32x32></image32x32>
                    <image48x48></image48x48>
                    <image128x128></image128x128>
                </icon> -->
            <!-- </fileType> -->
        <!-- </fileTypes> -->
        <!-- Specify Android specific tags that get passed to AndroidManifest.xml file. -->
        <!--<android>
            <manifestAdditions>
            <![CDATA[
                <manifest android:installLocation="auto">
                    <uses-permission android:name="android.permission.INTERNET"/>
                    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
                    <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
                    <uses-configuration android:reqFiveWayNav="true"/>
                    <supports-screens android:normalScreens="true"/>
                    <uses-feature android:required="true" android:name="android.hardware.touchscreen.multitouch"/>
                    <application android:enabled="true">
                        <activity android:excludeFromRecents="false">
                            <intent-filter>
                                <action android:name="android.intent.action.MAIN"/>
                                <category android:name="android.intent.category.LAUNCHER"/>
                            </intent-filter>
                        </activity>
                    </application>
                </manifest>
            ]]>
            </manifestAdditions>
        </android> -->
        <!-- End of the schema for adding the android specific tags in AndroidManifest.xml file -->
    </application>

    This appears to be a Flex question. Please try posting to the Flex forums here http://forums.adobe.com/community/flex/flex_general_discussion for better response.

  • AIR Auto update error

    Hello all,
    I am trying to build an autoupdate app in AIR using FB4. I use the code :
    import flash.system.System;
            import flash.events.ErrorEvent;
            import air.update.ApplicationUpdaterUI;
            import air.update.events.UpdateEvent;
            [Bindable]
            private var appUpdater:ApplicationUpdaterUI = new ApplicationUpdaterUI();
    protected function checkForUpdate():void {
                NativeApplication.nativeApplication.addEventListener( Event.EXITING,
                    function(e:Event):void {
                        var opened:Array = NativeApplication.nativeApplication.openedWindows;
                        for (var i:int = 0; i < opened.length; i ++) {
                            opened[i].close();
                setApplicationVersion();
                appUpdater.updateURL = "http://localhost/updateTest/update.xml";
                appUpdater.isCheckForUpdateVisible = false;
                appUpdater.addEventListener(UpdateEvent.INITIALIZED, onUpdate);
                appUpdater.addEventListener(ErrorEvent.ERROR, onError);
                appUpdater.initialize();
            protected function onError(event:ErrorEvent):void {
                Alert.show(event.toString());
            protected function onUpdate(event:UpdateEvent):void {
                appUpdater.checkNow();
            protected function setApplicationVersion():void {
                var appXML:XML = NativeApplication.nativeApplication.applicationDescriptor;
                var ns:Namespace = appXML.namespace();
                ver.text = "Current version is " + appXML.ns::version;
    whats wrong in the above code.... when the checkForUpdate function initiated an error occured :
    TypeError: Error #1007: Instantiation attempted on a non-constructor.
        at mx.controls::ProgressBar/createChildren()
        at mx.core::UIComponent/initialize()[E:\dev\beta1\frameworks\projects\framework\src\mx\core\ UIComponent.as:6510]
        at mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::childAdded()[E:\dev\beta1\frameworks\projects\ framework\src\mx\core\UIComponent.as:6402]
        at mx.core::Container/http://www.adobe.com/2006/flex/mx/internal::childAdded()[E:\dev\beta1\frameworks\projects\ framework\src\mx\core\Container.as:3879]
        at mx.core::Container/addChildAt()[E:\dev\beta1\frameworks\projects\framework\src\mx\core\Co ntainer.as:2541]
        at mx.core::Container/addChild()[E:\dev\beta1\frameworks\projects\framework\src\mx\core\Cont ainer.as:2459]
        at ApplicationUpdaterDialogs/_ApplicationUpdaterDialogs_ApplicationUpdaterVBox10_c()
        at mx.core::DeferredInstanceFromFunction/getInstance()[E:\dev\beta1\frameworks\projects\fram ework\src\mx\core\DeferredInstanceFromFunction.as:105]
        at mx.states::AddChild/createInstance()
        at mx.states::AddChild/set targetFactory()
        at ApplicationUpdaterDialogs/_ApplicationUpdaterDialogs_AddChild8_i()
        at ApplicationUpdaterDialogs/_ApplicationUpdaterDialogs_State7_c()
        at ApplicationUpdaterDialogs()
        at _ApplicationUpdaterDialogs_mx_managers_SystemManager/create()
        at mx.managers::SystemManager/initializeTopLevelWindow()[E:\dev\beta1\frameworks\projects\fr amework\src\mx\managers\SystemManager.as:3581]
        at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::docFrameHandler()[E:\dev\beta1\frameworks\proj ects\framework\src\mx\managers\SystemManager.as:3400]
        at mx.managers::SystemManager/docFrameListener()[E:\dev\beta1\frameworks\projects\framework\ src\mx\managers\SystemManager.as:3258]

    Just Got The Solution for Error 16811 &  16816
    Note Following things to avoide update error
    No 1.>
    You xml schema for update descriptor.xml in  server should look similar to this
    <?xml version="1.0" encoding="utf-8"?>
    <update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
      <versionNumber>2.0</versionNumber>
      <url>http://localhost/SerialHunter/SerialHunter.air</url>
      <description><![CDATA[
    SerialHunter Version 2.0 by Rajendra Khope
    This new version includes:
        * AutoUpdate
        * Enhaced UI functions
        * Ability to add providers       
      ]]></description>
    </update>
    Note xmlns="http://ns.adobe.com/air/framework/update/description/2.5"
    and versionNumber instead of version
    Also make similar changes in appxml version field (in Burrito its by default versionNumber )
    No 2>
    if u are using code to display veesion number make sure it should look like:
    var appXML:XML = NativeApplication.nativeApplication.applicationDescriptor;
    var ns:Namespace = appXML.namespace();
    pnlMain.title=appXML.ns::name+" v "+appXML.ns::versionNumber
    Thats it...!
    Rajendra Khope
    bkrajendra at gmail dot com

  • AIR auto update error, and question about POST parameters

    Hello,
    I'm getting a Download Failed error in the AIR autoupdating process;
    There was an error downloading the update. Error# 16822
    I recall this working once, the very first time that I tried it.
    My app.xml file contains this line:
        <version>12</version>
    and my update.xml file contains:
    <update xmlns="http://ns.adobe.com/air/framework/update/description/1.0">
      <version>12</version>
      <url>http:/players.biemedia.com/ooyala/Composer/Composer.air</url>
      <description>12 - Bug fixes and prepopulating defaults for player creation screen</description>
    </update>
    Pasting the URL into a browser works.
    However, this stuffresides on cloudfront.  in the past i have noticed that if something tries to send post parameters along with the request, cloudfront will deny the request.  Is it possible that the AIR app is sending POST parameters when hitting the download URL, and could this behavior be new in the last 6 months or so?
    Any other ideas?
    Thanks,
    Gerry

    Just Got The Solution for Error 16811 &  16816
    Note Following things to avoide update error
    No 1.>
    You xml schema for update descriptor.xml in  server should look similar to this
    <?xml version="1.0" encoding="utf-8"?>
    <update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
      <versionNumber>2.0</versionNumber>
      <url>http://localhost/SerialHunter/SerialHunter.air</url>
      <description><![CDATA[
    SerialHunter Version 2.0 by Rajendra Khope
    This new version includes:
        * AutoUpdate
        * Enhaced UI functions
        * Ability to add providers       
      ]]></description>
    </update>
    Note xmlns="http://ns.adobe.com/air/framework/update/description/2.5"
    and versionNumber instead of version
    Also make similar changes in appxml version field (in Burrito its by default versionNumber )
    No 2>
    if u are using code to display veesion number make sure it should look like:
    var appXML:XML = NativeApplication.nativeApplication.applicationDescriptor;
    var ns:Namespace = appXML.namespace();
    pnlMain.title=appXML.ns::name+" v "+appXML.ns::versionNumber
    Thats it...!
    Rajendra Khope
    bkrajendra at gmail dot com

  • Windows XP Permissions vs AIR Auto Update

    Hello All,
    I've just started getting into AIR, and I've run into an
    issue. I'm planning an app that would be distributed to Windows XP
    users with limited accounts. The issue I'm currently trying to
    tackle is how to get the application to auto update when a user
    opens it from a limited account. Currently it gives me the error:
    "An error occurred while updating the application. Try updating it
    again. If the problem persists, contact the application author.
    Error# 0".
    Since I'm a Mac guy, I don't know too much about permissions
    and account settings in XP. Is there a way to simply give the
    application the necessary permissions without having the user have
    to login every time like the "Run with different credentials"
    option.

    No, there's no way around this. Prevent applications from
    updating themselves is part of what limited accounts are supposed
    to do.
    You might try finding out how software is normally updated
    for these machines. That's probably the path you want to take for
    this application, too.

  • Why doesn't AIR auto-update

    Secunia PSI tells me that Adobe AIR is updating, but the update doesn't proceed automatically. It's been "updating" for a week. What do I need to do to get it to actually do the update?

    manually update
    Archived Adobe AIR SDK versions

  • How to setup air help auto-update

    RH8 HTML.
    Im fiddling around with the AIR Help file and trying to get the auto update working.
    So far I have the comments syncing perfectly across users with a shared folder on our network.
    I'm now publishing the air file to a shared folder again where everyone can get the  file and where the update.xml file is sitting.
    so I have this looking structure.
    \\networkdrive\Adobe_AIR\Generic_AIR\AdobeAIRApplication\Help File.air
    \\networkdrive\Adobe_AIR\Generic_AIR\AdobeAIRApplication\Help_Update.xml
    I set everything in RH Air output to publish to these folders, and I can see the newest files each time I do, I change the version numbers from 1.28 to 1.29, and this is reflected in the update.xml file where the version number has changed.
    but when I go into the actual instaleld 1.28 version and use the Check Now feature to look for the latest 1.29 which has over written the 1.28 files in the shared folder, it finds nothing.
    I cant find any way to manually point to where the update should be found.....do the update files have to sit in the same install directory or something? How does this work....aarrrgghhh
    Is there another things I'm not doing?
    Thanks.

    Hi Nick
    Good to hear that you are looking into AIR and Comment syncing is working fine.
    Regarding the AIR auto update feature, you need to do the following
    While generating the AIR file, you need to specify the update XML file location in AIR Help SSL generation option shown in the image below.
    Now install this AIR file, and update the update.xml file and new version of AIR file, and it should work fine.
    So the point is the installed air file need to know where to look for the update.xml file, it can be shared folder or a website.
    Hope this will help you.
    -Praful

  • Authenticating AIR application auto-update

    Hi, I'm building documentation for my desktop-product with RH8 and AIR SSL auto-update functionality.  It looks like I need to expose any revision of my documentation on Internet for the auto-update.  My company does not want to expose it freely since it is intellecual property.  Is there a way to protect the revision with some authentication that would work with the AIR auto-update mechanism?  Thanks in advance.
    --dh

    Same situation like ours! :-)
    If your documentation on the internet is accessed using "https", then that's the link that will be used for auto-updating and thus an authentication box will be displayed anytime a request for an update is made.
    Good luck.
    K
    P.S.: Any chance you encountered this problem with AIR and external links: http://forums.adobe.com/thread/422870?tstart=0

  • Best practice for auto update flex web applications

    Hi all
    is there a best practice for auto update flex web applications, much in the same way AIR applications have an auto update mechanism?
    can you please point me to the right direction?
    cheers
    Yariv

    Hey drkstr
    I'm talking about a more complex mechanism that can handle updates to modules being loaded into the application ect...
    I can always query the server for the verion and prevent loading from cach when a module needs to be updated
    but I was hoping for something easy like the AIR auto update feature

  • How to use auto update in android ?

    hi,
    i want to use adobe air auto update in android devices.. what can i do ?

    Did you install the maintenance service properly in download and install updates in the background?
    *Tools > Options > Advanced > Update: "Use a background service to install updates"
    *https://support.mozilla.org/kb/what-mozilla-maintenance-service
    If updating Firefox isn't working properly then this could be that the maintenance service isn't installed and enabled properly or not allowed in security software.
    The maintenance service can be uninstalled separately, it shows up as a new item under add/remove programs.
    You can try to uninstall and reinstall the maintenance service as a user by running the installer file in the Firefox program folder.
    *maintenanceservice_installer.exe

  • Adobe Air runtime auto-update

    Adobe Air runtime auto-updates itself without any notification or request on my Mac OSX 10.6.7 machine. I do not like this behavior. Is there any way to change it?

    Please see our Disable automatic updates of the runtime document.  However, please be aware that our updates include both new functionality and bug and security fixes.  I'd definitely recommend keeping an eye out for future releases and manually installing if you disable the updates.
    Thanks,
    Chris

  • Adobe air 2.6 auto update problem..

    hi friends,
    i am writing a multitouch application for like kiosk machine..
    and i want to add auto update functionally,
    i write this codes, but i am getting There was an error downloading the update. Error# 16824 error after downloading update...
    update_2_6.xml :
    <?xml version="1.0" encoding="utf-8"?>
    <update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
        <versionNumber>0.0.4</versionNumber>
        <url>http://www.abc.com/updates/RixossIBoard_v004.air.zip</url>
        <description>This is an AIR2.6 release of my application</description>
    </update>
    update_config.xml :
    <?xml version="1.0" encoding="utf-8"?>
    <configuration xmlns="http://ns.adobe.com/air/framework/update/configuration/1.0">
        <url>http://www.abc.com/updates/update_2_6.xml</url>
        <delay>0</delay>
         <defaultUI>
           <dialog name="checkForUpdate" visible="false" />
           <dialog name="downloadUpdate" visible="true" />
           <dialog name="downloadProgress" visible="true" />
           <dialog name="installUpdate" visible="true" />
       </defaultUI>    
    </configuration>
    in flash code:
    var updater:ApplicationUpdaterUI = new ApplicationUpdaterUI();
    updater.configurationFile = new File("app:/update_config.xml");
    updater.addEventListener(UpdateEvent.INITIALIZED, updaterInitialized);
    updater.addEventListener(ErrorEvent.ERROR, hatavarupdate);
    //updater.addEventListener(ErrorEvent.ERROR.hatavarupdate);
    updater.initialize();
    function hatavarupdate(evt:ErrorEvent):void
        //trace (evt.type);   
    function updaterInitialized(e:UpdateEvent):void{
        updater.checkNow();
    what is problem?
    it check update ok, download update ok, but after download update i get the There was an error downloading the update. Error# 16824
    Thanks for relation,
    Ercan

    Why don't you post some of the relevant lines for your application?
    Makes hard to guess what the issue is otherwise.
    The first line of your matching app file (<appname>-app.mxml) must have the same matching air sdk version as in...
    <application xmlns="http://ns.adobe.com/air/application/2.6">
    The version number if that same file must match the versionNumber in your update file, as in
    <versionNumber>0.0.4</versionNumber>
    Compile it and distribute it to the url specified in your update xml file
    http://www.abc.com/updates/RixossIBoard_v004.air.zip
    Manually check your app:/update_config.xml - make sure it is what you think it is
    Don

  • Flash Builder 4.5.1 - Air ApplicationUpdaterUI Auto Update Fails

    I just reinstalled my FlashBuilder 4.5.1 and built a new HelloWorld App
    in order to test the SDK 2.6 with the Air ApplicationUpdaterUI.
    I get no errors but it won't update using the 2.6 namespace in both the -app.mxml and update.xml on server.
    A trace in the StatusUpdateEvent never shows up in debug mode.
    The only window that pops up is the one asking to Check for Update?
    Pulling my hair out - must be something obvious I'm doing wrong here - can a new set of eyes spot something?
    Main xml file:
    <?xml version="1.0" encoding="utf-8"?>
    <s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009"
                           xmlns:s="library://ns.adobe.com/flex/spark"
                           xmlns:mx="library://ns.adobe.com/flex/mx"
                           creationComplete = "checkForUpdate();" title="Test Air Updater">
        <fx:Declarations>
            <!-- Place non-visual elements (e.g., services, value objects) here -->
        </fx:Declarations>
        <fx:Script>
            <![CDATA[
                import air.net.URLMonitor;
                import air.update.ApplicationUpdaterUI;
                import air.update.events.StatusUpdateErrorEvent;
                import air.update.events.StatusUpdateEvent;
                import air.update.events.UpdateEvent;
                import flash.events.ErrorEvent;
                import mx.controls.Alert;
                import mx.events.CloseEvent;
                import mx.events.FlexEvent;
                private const APP_VERSION_FILE:String     = "http://www.public-knowledge.com/Quest/Timesheets/new_app_version.xml";
                private var appUpdater:ApplicationUpdaterUI = new ApplicationUpdaterUI();
                private function checkForUpdate():void {
                    // Add events
                    appUpdater.addEventListener(UpdateEvent.INITIALIZED, onInitialized);
                    appUpdater.addEventListener(StatusUpdateErrorEvent.UPDATE_ERROR, onUpdateStatusError);
                    appUpdater.addEventListener(StatusUpdateEvent.UPDATE_STATUS, updateStatusHandler); 
                    appUpdater.addEventListener(ErrorEvent.ERROR, onError); // If something goes wrong, run onError               
                    appUpdater.isCheckForUpdateVisible = true;
                    appUpdater.isUnexpectedErrorVisible = true;
                    appUpdater.isDownloadUpdateVisible= true;
                    appUpdater.isDownloadProgressVisible=true;
                    appUpdater.isInstallUpdateVisible = true;               
                    appUpdater.updateURL = APP_VERSION_FILE; // Server-side XML file describing update               
                    trace(APP_VERSION_FILE);
                    appUpdater.initialize();
                private function onError(event:ErrorEvent):void {
                    Alert.show('ERROR: ' + event.toString());
                private function onUpdateStatusError(event:StatusUpdateErrorEvent):void {
                    Alert.show('Error Checking For Update: ' + event.toString());
                private function onInitialized(event:UpdateEvent):void {
                    trace('Checking For Updates ...');       
                    appUpdater.checkNow();
                private function updateStatusHandler(event:UpdateEvent):void {
                    //var descriptor:XML = NativeApplication.nativeApplication.applicationDescriptor;
                    //var ns:Namespace   = descriptor.namespaceDeclarations()[0];
                    //var verNum:String  = descriptor.ns::versionNumber;
                    trace('Update Event Reached ...');       
            ]]>
        </fx:Script>   
        <s:TitleWindow x="63" y="35" width="250" height="200" title="Hello">
            <s:Label x="24" y="80" text="Hello World"/>
        </s:TitleWindow>
    </s:WindowedApplication>
    -App.MXML File: (first part)
    <?xml version="1.0" encoding="utf-8" standalone="no"?>
    <application xmlns="http://ns.adobe.com/air/application/2.6">
    <!-- Adobe AIR Application Descriptor File Template.
        Specifies parameters for identifying, installing, and launching AIR applications.
        xmlns - The Adobe AIR namespace: http://ns.adobe.com/air/application/2.6
                The last segment of the namespace specifies the version
                of the AIR runtime required for this application to run.
        minimumPatchLevel - The minimum patch level of the AIR runtime required to run
                the application. Optional.
    -->
        <!-- A universally unique application identifier. Must be unique across all AIR applications.
        Using a reverse DNS-style name as the id is recommended. (Eg. com.example.ExampleApplication.) Required. -->   
        <id>ca.questgeomatics.testairapp</id>
        <!-- Used as the filename for the application. Required. -->
        <filename>TestAirUpdater</filename>
        <!-- The name that is displayed in the AIR application installer.
        May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <name>TestAirUpdater</name>
        <!-- A string value of the format <0-999>.<0-999>.<0-999> that represents application version which can be used to check for application upgrade.
        Values can also be 1-part or 2-part. It is not necessary to have a 3-part value.
        An updated version of application must have a versionNumber value higher than the previous version. Required for namespace >= 2.5 . -->
        <versionNumber>1.0.0</versionNumber>
        <!-- A string value (such as "v1", "2.5", or "Alpha 1") that represents the version of the application, as it should be shown to users. Optional. -->
        <versionLabel>v 1.0.0</versionLabel>
    Updater XML file (new_app_version.xml):
    <?xml version="1.0" encoding="utf-8"?>
    <update xmlns="http://ns.adobe.com/air/framework/update/description/2.6">
    <versionNumber>1.0.1</versionNumber>
    <versionLabel>v 1.01</versionLabel>
    <url>http://www.public-knowledge.com/Quest/Timesheets/TestAirUpdater.air</url>
    <description><![CDATA[
    * First official release that implemements Auto Updating feature
    ]]></description>
    </update>
    Bolded appl descriptor versions
    Message was edited by: DonMitchinson

    Status Update - don't know if this is a bug, design flaw, install problem or my misunderstanding.
    I got it to work by first changing my Flex library to 4.5.0 - still didn't work with current
    app and update mxml files using "2.6" for their namespace versions. But I did at least
    get the popup error number 16815 - indicating an error in the update version namespace.
    By leaving my application namespace version at "2.6" and changing the update version to "2.5" ... bingo!
    I got my new update installed autiomatically.
    Is this how it's supposed to work - or are my runtimes mixed up?
    Will this work the same using the Flex 4.5.1 SDK? I'll find out shortly
    Hope this helps others.

  • Auto update using AIR 2.0

    This is my code
    <?xml version="1.0" encoding="utf-8"?><mx:WindowedApplication  xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" fontWeight="bold" textDecoration="
    underline" creationComplete="preCheckForUpdate()">
     <mx:Script> 
    <![CDATA[
    import air.update.ApplicationUpdater; 
    import flash.events.ErrorEvent; 
    import flash.events.IOErrorEvent; 
    import air.update.ApplicationUpdaterUI; 
    import air.update.events.UpdateEvent; 
    import mx.controls.Alert; 
    private var appUpdater:ApplicationUpdater = new ApplicationUpdater(); 
    private var updateXMLURL:String = "http://localhost/AutoUpdate1/update.xml"; 
    // Pre-read the server-side XML file to look for <force>yes</force>  
    private function preCheckForUpdate():void{
    try{
    var loader:URLLoader = new URLLoader(); 
    loader.addEventListener(Event.COMPLETE, checkForUpdate);
    loader.addEventListener(IOErrorEvent.IO_ERROR, onIOError);
    // Just in case we can't read the update.xml loader.load(
    new URLRequest(updateXMLURL));}
    catch(e:Error){
    Alert.show(e.toString());
    private function checkForUpdate(event:Event):void{
    try{
    setApplicationVersion();
    // Find the current version so we can show it below  
    var myXML:XML = new XML(event.target.data); 
    namespace items = "http://ns.adobe.com/air/framework/update/description/2.0beta2"; 
    use namespace items; 
    var forceUpdate:String = myXML.force; 
    appUpdater.updateURL = updateXMLURL;
    // Server-side XML file describing update  
    //appUpdater.isCheckForUpdateVisible = false; // We won't ask permission to check for an update  
    // If <force>yes</force> was found above, turn off the download and install dialogs  
    /* if(forceUpdate.toLowerCase() == "yes") { 
    appUpdater.isDownloadUpdateVisible = false;
    appUpdater.isInstallUpdateVisible = false;
    appUpdater.addEventListener(UpdateEvent.INITIALIZED, onUpdate);
    // Once initialized, run onUpdate  
    //appUpdater.addEventListener(ErrorEvent.ERROR, onError); // If something goes wrong, run onError  
    appUpdater.initialize();
    // Initialize the update framework}
    catch(e:Error){
    Alert.show(e.toString());
    private function onError(event:ErrorEvent):void { 
    Alert.show(event.toString());
    private function onIOError(event:IOErrorEvent):void 
    Alert.show(event.toString());
    trace("Error loading URL.");}
    private function onUpdate(event:UpdateEvent):void{
    try{
    appUpdater.checkNow();
    // Go check for an update now}
    catch(e:Error){
    Alert.show(e.toString());
    // Find the current version for our Label below  
    private function setApplicationVersion():void{
    try{
    var appXML:XML = NativeApplication.nativeApplication.applicationDescriptor; 
    var ns:Namespace = appXML.namespace(); ver.text =
    "Current version is " + appXML.ns::version;}
    catch(e:Error){
    Alert.show(e.toString());
    ]]>
    </mx:Script> 
    <mx:WipeRight  id="slowright" duration="1000"/>
     <mx:Label x="93" y="135" text="Welcome to Rapidcare" fontSize="36" fontFamily="Times New Roman" color="#3C0B1F"creationCompleteEffect="
    {slowright}" height="89"/>
     <mx:Label x="178" y="186" color="#F81908" fontSize="36" fontWeight="bold" textDecoration="normal" id="ver"/>
     <mx:Label x="93" y="279" text="Hai"/>
     </mx:WindowedApplication>
    IT throws an error in this appUpdater.checkNow();
    Error #2044: Unhandled updateError:. text=unknown update version
    Please any provide solution for this
    Regards,
    Jayagopal

    Hi Jayagopal,
    The error you are getting might be from the fact that you are using an invalid namespace within your update.xml. Can you make sure that the specified namespace from the update.xml is the same with the following one xmlns="http://ns.adobe.com/air/framework/update/description/1.0" and then then try to reproduce this issue?
    Here is the update.xml which i've used when trying to reproduce your issue:
    <?xml version="1.0" encoding="utf-8"?>
    <update xmlns="http://ns.adobe.com/air/framework/update/description/1.0">
      <version>v1.1</version>
      <url>http://localhost/AutoUpdate1/update.air</url>
      <description><![CDATA[
    Version 1.1. This new version includes:
        * Feature 1
        * Feature 2
        * Feature 3       
      ]]></description>
    </update>
    If you can still reproduce this issue can you also attach your update.xml or host your air app and update.xml on an external server from where I could access them?
    Hope this helps you,
    -Catalin

  • Use the system lang of AIR applications auto update.

    Hello,
    I recently used the auto update framework for my AIR application, this works fine but i have a small problem.
    I made some reasearches and i found AIR uses the system lang by default. When i install my package for the first time, the lang is my sytem lang but when i find a new update after running auto update of my app, the AIR updater window doesn't use my sytem lang, which is french, but uses english lang. I'd like to put this window in french.
    Thanks.

    Try loading and using the add-on from this link: https://addons.mozilla.org/en-US/firefox/addon/add-on-compatibility-reporter/
    Many add-ons do in fact work if you force them to run. The procedure to roll-back is given in this article: [[installing previous versions of firefox]]
    Unfortunately the official Firefox policy is that you downgrade to 3.6 which is supported for a while longer, and not the now unsupported Firefox 4. If after installing and running the ''add-on compatibility reporter'' you still have problems there are ways around the official policy.
    I think it is absurd that Firefox 4 may be used by tens of millions of users one day and a few days later those that upgrade to Firefox 5 should be not only told not to use a now unsupported browser, if they need to revert due to problems, but are actually obstructed in attempts to do so. See also [/questions/840397#answer-205154]

Maybe you are looking for