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.

Similar Messages

  • AIR runtime on Windows 2003 Server - switch off auto-updates???

    Hello,
    Trying to switch off auto-updates in Win 03. Have tried:
    - Adobe settings manager
    - Updating Windows registry keys
    Nothing works..updates are still requested
    Any ideas..?

    Could you check to see if a file named updateDisabled is present in either of these two folders (I suspect the Win 2003 folder would be similar to XP)?
    Windows XP
    C:\Documents and Settings\<username>\Application Data\Adobe\AIR\
    Window Vista / Windows 7
    C:\Users\<username>\Application Data\Adobe\AIR\
    That should take care of it on a per user basis.  For the registry, did you have HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\AIR\UpdateDisabled set to 1?

  • 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-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

  • 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

  • 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

  • Windows failed to restart after auto update

    Hi I have a dual boot machine with Windows 8.1 & Windows XP. The Windows 8.1 OS was itself an upgrade of Windows 8.0 . Everything was working well till last week.
    Last weekend 14th Feb, Windows 8.1 wanted to install some updates while shutting down. It installed about 14 updates and shut down promising to restart soon. After restarting, Windows 8.1 never booted. I waited for around 20 minutes and them manually restarted
    the machine. This time I selected Windows  XP. Windows XP started, but in the process fixed something on the file structure by running chkdisk, while starting.
    Later a friend told me that he'd similar issues of his computer not starting after the patch for a long time. But ultimately it did after about half an hour. I tried to boot Windows 8.1 again, leaving it no for an hour. But it was a vain effort.
    I tried to repair my machine by booting with the Windows 8.0 setup disk. But this also failed saying some partitions are locked.
    Can you please tell me what are the options available to me to revive my machine.

    Here is the forum for you.
    -- pa

  • Windows and dialogs, when resizing, auto-update UI?

    How do you allow the ui to keep being updated as you resize a window or dialog? I keep seeing the border move, then when I stop it updates the UI. I know its faster, but I was just curious of the other could be done?
    Thanks.

    Thanks. It works, but definitely noticeably slow. Even on a PIV1.8Ghz with 1GB memory I see that it doesn't update very smoothly. It seems if I move the pane slowly it will update alright, but if I move it even partly fast, it doesn't refresh until the move is done. Definitely shows the slowness of swing compared to native.

  • No toolbar and nothing on bottom of page to show me my other open windows.at all after firefox auto updated on it's own w/out even prompting me as usual.

    new firefox autoupdated instead o asking me as usual. ( soubds similar to other ppls prob., but w a twist or two. now no toolbar, so ur answer to click bookmarks or whatever doesn't help me n there is no sidebar. also, i no longer can see which other windows i have open at the bottom of the page so i can switch back w/out minimizing the current window. the url box doesn't show until i move the cursor over that top area. i love firefox, but w this and the older version locking up my computer on occasion and not disconnecting from the internet idk what's going on at firefox to cause subpar performance and causing near strokes or heart attacks in ppl.

    Your Firefox may have been in full screen mode. You can switch between full screen and normal mode using the F11 key.
    Do you have the orange Firefox button (abbreviated two-column menu) on the title bar? If you prefer the classic menu bar, tap the Alt key, and use View > Toolbars > Menu Bar to restore it. You can also use View > Toolbars to turn other toolbars on and off.
    Do you want to describe these problems in more detail?
    # Freezes and crashes - any pattern to them?
    # Not disconnecting - what do you mean?

  • We are trying to package our iTunes Windows and we can't stop the auto update feature.  How can we do this?

    We have consultants here packaging many of our Apps for deployment with Windows 7.  We cannot find a way to turn off the auto update feature within iTunes for Windows.  Has someone been successful in packaging iTunes for Windows and NOT do the auto update piece?

    The Apple advice revolves around the editing the registry:
    Windows OS Managed Client: How to manage iTunes control features
    ... but it's beyond my competence to advise how to work that particular registry edit into a deployment, I'm afraid.

  • 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

Maybe you are looking for