Air update Issue

What things can be wrong when this error occurs for air updateaplplication_ui
There was an error checking for updates. Error# 16815
config:
<?xml version="1.0" encoding="utf-8"?>
<configuration xmlns="http://ns.adobe.com/air/framework/update/configuration/1.0">
     <url>http://afiadesign.com/vislaw/update.xml</url>
    <delay>.001</delay>
</configuration>
update.xml:
<?xml version="1.0" encoding="utf-8"?>
     <update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
       <versionName>1.1</versionName>
       <url>http://afiadesign.com/vislaw/HeartMonitor.air</url>
       <description>This is the latest version of the Sample application.</description>
  </update>
I am using AIR 2.6 for publishing but I read that even if you are using air 2.6 you should still keep the 2.5 description.

EDIT:
Changed update.xml to:
<?xml version="1.0" encoding="utf-8"?>
<update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
    <versionNumber>1.1</versionNumber>
    <versionLabel>Beta 2</versionLabel>
    <url>http://afiadesign.com/vislaw/HeartMonitor.air</url>
    <description><![CDATA[
This version has fixes for the following knowns issues:
*First issue
*Second issue  
  ]]></description>
</update>
still having the same issue.

Similar Messages

  • Air 2.7 update issue

    Hi all
    Been using a very useful desktop app called Rightmove - for searching property listings.
    It has stopped working, and I'm wondering if it's since Air updated itself to 2.7. The app hangs on the opening screen and that's it. Have tried everything, including full clean up and reinstall, rolling back to earlier versions (2.5 and 2.6) of Air but no luck, it just won't work and I NEED IT! Was fine for months up until recently. Running Windows 7 Home Premium. I have the same issue with my netbook, running W7 Starter.
    Here's the Installation log.....oh....was going to paste it here, now I can't see how to that or to attach a text file! Help!

    Hi HelBel65,
    It may be related with some data corruption in local data for your application. We've heard that local data can be corrupted when updating application version but AIR team haven't ever been able to reproduce internally.
    Can you try to delete following folder after making a backup copy somewhere in different location?
    [this is my case of file path so change bold part as appropriate]
    C:\Users\<your account>\AppData\Roaming\com.rightmove.rmdesktop.303FAAB8E16C565CA4B74422796CD427470CE949.1
    It is better to remove above folder after uninstall the application first. So the steps are:
    1. uninstall application
    2. uninstall Adobe AIR (just in case)
    3. remove above folder
    4. install Adobe AIR 2.7.1 (latest release)
    5. install Rightmove application
    If you still see same problem, please log a bug in this public bugbas so AIR team can investigate the issue you have.
    https://bugbase.adobe.com/
    thanks,
    Hitomi

  • Air Update Framework Issue... Help please!

    The following code is from the Air Employee Directory example
    to which I have added an Update Object, the app installs and
    updates with no problem, but as soon as the update is done and it's
    time for the app to start, the app just doesn't come up. It was
    working fine before I added the update object... Any idea on what I
    could be doing wrong?
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application xmlns:mx="
    http://www.adobe.com/2006/mxml"
    layout="absolute" xmlns:ui="com.adobe.empdir.ui.*"
    applicationComplete="onApplicationComplete()" height="100%"
    width="100%" frameRate="45"
    horizontalScrollPolicy="off" verticalScrollPolicy="off"
    visible="false"
    showEffect="Fade" xmlns:local="*"
    creationComplete="checkUpdate()">
    <mx:Script>
    <![CDATA[
    import mx.logging.Log;
    import com.adobe.empdir.commands.ui.CloseApplicationCommand;
    import mx.binding.utils.BindingUtils;
    import mx.events.StateChangeEvent;
    import mx.events.ResizeEvent;
    private function onApplicationComplete() : void
    callLater( ui.init );
    // We listen to CLOSING fromboth the stage and the UI. If
    the user closes the app through the taskbar,
    // Event.CLOSING is emitted from the stage. Otherwise, it
    could be emitted from TitleConrols.mxml.
    ui.addEventListener( Event.CLOSING, onWindowClosing );
    stage.nativeWindow.addEventListener( Event.CLOSING,
    onWindowClosing );
    stage.nativeWindow.addEventListener( Event.CLOSE,
    onWindowClose );
    private function onWindowClose( evt:Event ) : void
    NativeApplication.nativeApplication.exit();
    private function onWindowClosing( evt:Event ) : void
    evt.preventDefault();
    var cmd : CloseApplicationCommand = new
    CloseApplicationCommand();
    cmd.execute();
    ]]>
    </mx:Script>
    <mx:Script>
    <![CDATA[
    import air.update.events.UpdateEvent;
    import mx.controls.Alert;
    import flash.events.ErrorEvent;
    import air.update.ApplicationUpdaterUI;
    * @var the object that that handles the update related
    actions
    private var appUpdater:ApplicationUpdaterUI = new
    ApplicationUpdaterUI();
    * This function is triggered when the application finished
    to load;
    * Here we initialize <code>appUpdater</code> and
    set some properties
    private function checkUpdate():void {
    setApplicationVersion();
    // we set the URL for the update.xml file
    appUpdater.updateURL = "
    http://localhost/updater/update.xml";
    //we set the event handlers for INITIALIZED nad ERROR
    appUpdater.addEventListener(UpdateEvent.INITIALIZED,
    onUpdate);
    appUpdater.addEventListener(ErrorEvent.ERROR, onError);
    //we can 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 = false;
    //if isFileUpdateVisible is set to true, File Update, File
    No Update,
    //and File Error dialog boxes will be displayed
    appUpdater.isFileUpdateVisible = false;
    //if isInstallUpdateVisible is set to true, the dialog box
    for installing the update is visible
    appUpdater.isInstallUpdateVisible = false;
    //we initialize the updater
    appUpdater.initialize();
    * Handler function triggered by the
    ApplicationUpdater.initialize;
    * The updater was initialized and it is ready to take
    commands
    * (such as <code>checkNow()</code>
    * @param UpdateEvent
    private 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
    * @param ErrorEvent
    private function onError(event:ErrorEvent):void {
    Alert.show(event.toString());
    * A simple code just to read the current version of the
    application
    * and display it in a label.
    private function setApplicationVersion():void {
    var appXML:XML =
    NativeApplication.nativeApplication.applicationDescriptor;
    var ns:Namespace = appXML.namespace();
    ]]>
    </mx:Script>
    <mx:TraceTarget level="0" includeDate="false"
    includeTime="false"
    includeCategory="true" includeLevel="true">
    <mx:filters>
    <mx:Array>
    <mx:String>*</mx:String>
    </mx:Array>
    </mx:filters>
    </mx:TraceTarget>
    <ui:ApplicationUI id="ui" width="100%" height="100%"
    />
    </mx:Application>

    This was an issue with the Update Framework in AIR SDK 1.5.3, which has been fixed. If you still want to use the ApplicationUpdaterUI, you can replace the swc in Flex SDK 3.6 with an applicationupdater_ui.swc from a newer version of AIR.
    Have a look at solution 3 in this post for some details on where to find the applicationupdater_ui.swc and how to replace it.
    http://forums.adobe.com/message/3060118#3060118
    Hope this helps!
    Horia

  • Flex/Air Update Object Issue...

    The following code is from the Air Employee Directory example
    to which I have added an Update Object, the app installs and
    updates with no problem, but as soon as the update is done and it's
    time for the app to start, the app just doesn't come up. It was
    working fine before I added the update object... Any idea on what I
    could be doing wrong?
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application xmlns:mx="
    http://www.adobe.com/2006/mxml"
    layout="absolute" xmlns:ui="com.adobe.empdir.ui.*"
    applicationComplete="onApplicationComplete()" height="100%"
    width="100%" frameRate="45"
    horizontalScrollPolicy="off" verticalScrollPolicy="off"
    visible="false"
    showEffect="Fade" xmlns:local="*"
    creationComplete="checkUpdate()">
    <mx:Script>
    <![CDATA[
    import mx.logging.Log;
    import com.adobe.empdir.commands.ui.CloseApplicationCommand;
    import mx.binding.utils.BindingUtils;
    import mx.events.StateChangeEvent;
    import mx.events.ResizeEvent;
    private function onApplicationComplete() : void
    callLater( ui.init );
    // We listen to CLOSING fromboth the stage and the UI. If
    the user closes the app through the taskbar,
    // Event.CLOSING is emitted from the stage. Otherwise, it
    could be emitted from TitleConrols.mxml.
    ui.addEventListener( Event.CLOSING, onWindowClosing );
    stage.nativeWindow.addEventListener( Event.CLOSING,
    onWindowClosing );
    stage.nativeWindow.addEventListener( Event.CLOSE,
    onWindowClose );
    private function onWindowClose( evt:Event ) : void
    NativeApplication.nativeApplication.exit();
    private function onWindowClosing( evt:Event ) : void
    evt.preventDefault();
    var cmd : CloseApplicationCommand = new
    CloseApplicationCommand();
    cmd.execute();
    ]]>
    </mx:Script>
    <mx:Script>
    <![CDATA[
    import air.update.events.UpdateEvent;
    import mx.controls.Alert;
    import flash.events.ErrorEvent;
    import air.update.ApplicationUpdaterUI;
    * @var the object that that handles the update related
    actions
    private var appUpdater:ApplicationUpdaterUI = new
    ApplicationUpdaterUI();
    * This function is triggered when the application finished
    to load;
    * Here we initialize <code>appUpdater</code> and
    set some properties
    private function checkUpdate():void {
    setApplicationVersion();
    // we set the URL for the update.xml file
    appUpdater.updateURL = "
    http://localhost/updater/update.xml";
    //we set the event handlers for INITIALIZED nad ERROR
    appUpdater.addEventListener(UpdateEvent.INITIALIZED,
    onUpdate);
    appUpdater.addEventListener(ErrorEvent.ERROR, onError);
    //we can 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 = false;
    //if isFileUpdateVisible is set to true, File Update, File
    No Update,
    //and File Error dialog boxes will be displayed
    appUpdater.isFileUpdateVisible = false;
    //if isInstallUpdateVisible is set to true, the dialog box
    for installing the update is visible
    appUpdater.isInstallUpdateVisible = false;
    //we initialize the updater
    appUpdater.initialize();
    * Handler function triggered by the
    ApplicationUpdater.initialize;
    * The updater was initialized and it is ready to take
    commands
    * (such as <code>checkNow()</code>
    * @param UpdateEvent
    private 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
    * @param ErrorEvent
    private function onError(event:ErrorEvent):void {
    Alert.show(event.toString());
    * A simple code just to read the current version of the
    application
    * and display it in a label.
    private function setApplicationVersion():void {
    var appXML:XML =
    NativeApplication.nativeApplication.applicationDescriptor;
    var ns:Namespace = appXML.namespace();
    ]]>
    </mx:Script>
    <mx:TraceTarget level="0" includeDate="false"
    includeTime="false"
    includeCategory="true" includeLevel="true">
    <mx:filters>
    <mx:Array>
    <mx:String>*</mx:String>
    </mx:Array>
    </mx:filters>
    </mx:TraceTarget>
    <ui:ApplicationUI id="ui" width="100%" height="100%"
    />
    </mx:Application>

    The following code is from the Air Employee Directory example
    to which I have added an Update Object, the app installs and
    updates with no problem, but as soon as the update is done and it's
    time for the app to start, the app just doesn't come up. It was
    working fine before I added the update object... Any idea on what I
    could be doing wrong?
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application xmlns:mx="
    http://www.adobe.com/2006/mxml"
    layout="absolute" xmlns:ui="com.adobe.empdir.ui.*"
    applicationComplete="onApplicationComplete()" height="100%"
    width="100%" frameRate="45"
    horizontalScrollPolicy="off" verticalScrollPolicy="off"
    visible="false"
    showEffect="Fade" xmlns:local="*"
    creationComplete="checkUpdate()">
    <mx:Script>
    <![CDATA[
    import mx.logging.Log;
    import com.adobe.empdir.commands.ui.CloseApplicationCommand;
    import mx.binding.utils.BindingUtils;
    import mx.events.StateChangeEvent;
    import mx.events.ResizeEvent;
    private function onApplicationComplete() : void
    callLater( ui.init );
    // We listen to CLOSING fromboth the stage and the UI. If
    the user closes the app through the taskbar,
    // Event.CLOSING is emitted from the stage. Otherwise, it
    could be emitted from TitleConrols.mxml.
    ui.addEventListener( Event.CLOSING, onWindowClosing );
    stage.nativeWindow.addEventListener( Event.CLOSING,
    onWindowClosing );
    stage.nativeWindow.addEventListener( Event.CLOSE,
    onWindowClose );
    private function onWindowClose( evt:Event ) : void
    NativeApplication.nativeApplication.exit();
    private function onWindowClosing( evt:Event ) : void
    evt.preventDefault();
    var cmd : CloseApplicationCommand = new
    CloseApplicationCommand();
    cmd.execute();
    ]]>
    </mx:Script>
    <mx:Script>
    <![CDATA[
    import air.update.events.UpdateEvent;
    import mx.controls.Alert;
    import flash.events.ErrorEvent;
    import air.update.ApplicationUpdaterUI;
    * @var the object that that handles the update related
    actions
    private var appUpdater:ApplicationUpdaterUI = new
    ApplicationUpdaterUI();
    * This function is triggered when the application finished
    to load;
    * Here we initialize <code>appUpdater</code> and
    set some properties
    private function checkUpdate():void {
    setApplicationVersion();
    // we set the URL for the update.xml file
    appUpdater.updateURL = "
    http://localhost/updater/update.xml";
    //we set the event handlers for INITIALIZED nad ERROR
    appUpdater.addEventListener(UpdateEvent.INITIALIZED,
    onUpdate);
    appUpdater.addEventListener(ErrorEvent.ERROR, onError);
    //we can 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 = false;
    //if isFileUpdateVisible is set to true, File Update, File
    No Update,
    //and File Error dialog boxes will be displayed
    appUpdater.isFileUpdateVisible = false;
    //if isInstallUpdateVisible is set to true, the dialog box
    for installing the update is visible
    appUpdater.isInstallUpdateVisible = false;
    //we initialize the updater
    appUpdater.initialize();
    * Handler function triggered by the
    ApplicationUpdater.initialize;
    * The updater was initialized and it is ready to take
    commands
    * (such as <code>checkNow()</code>
    * @param UpdateEvent
    private 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
    * @param ErrorEvent
    private function onError(event:ErrorEvent):void {
    Alert.show(event.toString());
    * A simple code just to read the current version of the
    application
    * and display it in a label.
    private function setApplicationVersion():void {
    var appXML:XML =
    NativeApplication.nativeApplication.applicationDescriptor;
    var ns:Namespace = appXML.namespace();
    ]]>
    </mx:Script>
    <mx:TraceTarget level="0" includeDate="false"
    includeTime="false"
    includeCategory="true" includeLevel="true">
    <mx:filters>
    <mx:Array>
    <mx:String>*</mx:String>
    </mx:Array>
    </mx:filters>
    </mx:TraceTarget>
    <ui:ApplicationUI id="ui" width="100%" height="100%"
    />
    </mx:Application>

  • No WIFI after iOS 5.0.1 over-the-air update on original iPad

    No WIFI after iOS 5.0.1 over-the-air update on original iPad. I have reset the network settings,  power off the iPad, trying static IP and nothing, it's unable to join my wifi network. anybody with the same issue?

    Great!  Thanks, this works.
    I have an old Linksys WRT54G in it I can select WPA Personal and AES as algorithm--it works for me (though maybe just changing to anything works!  but I will not try anything different since I have spent already so much time with this problem.)  Again, thanks for the solution Juan.

  • AIR Update framework with Flash Builder

    Hi,
    I am not sure if this is the right place but since this problem happens with the new Flash Builder 4 and AIR, I am putting it here :
    When I run the Air update framework with the new flash builder , i get this exception when I call appUpdater.initialize() in the same given in http://www.adobe.com/cfusion/communityengine/index.cfm?event=showdetails&product Id=4&postId=9543
    The error is
    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\sr c\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\Container.as:2541]
        at mx.core::Container/addChild()[E:\dev\beta1\frameworks\projects\framework\src\mx \core\Container.as:2459]
        at ApplicationUpdaterDialogs/_ApplicationUpdaterDialogs_ApplicationUpdaterVBox10_c ()
        at mx.core::DeferredInstanceFromFunction/getInstance()[E:\dev\beta1\frameworks\pro jects\framework\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\p rojects\framework\src\mx\managers\SystemManager.as:3581]
        at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::docFrameHandler()[E:\dev\beta1\frameworks\projects\framework\src\mx\managers\SystemManager.as:3 400]
        at mx.managers::SystemManager/docFrameListener()[E:\dev\beta1\frameworks\projects\ framework\src\mx\managers\SystemManager.as:3258]
    The code is the exact same give in the example i mentioned above.
     This works fine in my Flex Builder 3. 
    Thanks
    Hironmay Basu

    the issue is already reported here:
    http://bugs.adobe.com/jira/browse/SDK-22886?page=com.atlassian.jira.plugin.system.issuetab panels:all-tabpanel
    As a workaround, you can try using:
    http://www.websector.de/blog/2009/09/09/custom-applicationupdaterui-for-using-air-updater- framework-in-flex-4/

  • Flash Builder and Adobe AIR update framework

    Hi,
    I posted this in AIR forum , but thought it happens with new flash builder and flex 4 beta , i should do here also
    When I run the Air update framework with the new flash builder , i get this exception when I call appUpdater.initialize() in the same given in http://www.adobe.com/cfusion/communityengine/index.cfm?event=showdetails&product Id=4&postId=9543
    The error is
    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\sr c\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\Container.as:2541]
        at mx.core::Container/addChild()[E:\dev\beta1\frameworks\projects\framework\src\mx \core\Container.as:2459]
        at ApplicationUpdaterDialogs/_ApplicationUpdaterDialogs_ApplicationUpdaterVBox10_c ()
        at mx.core::DeferredInstanceFromFunction/getInstance()[E:\dev\beta1\frameworks\pro jects\framework\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\p rojects\framework\src\mx\managers\SystemManager.as:3581]
        at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::docFrameHandler()[E:\dev\beta1\frameworks\projects\framework\src\mx\managers\SystemManager.as:3 400]
        at mx.managers::SystemManager/docFrameListener()[E:\dev\beta1\frameworks\projects\ framework\src\mx\managers\SystemManager.as:3258]
    The code is the exact same given in the updater example i mentioned in the link above. Only difference is i am using spark framework. The appUpater.initialize() never seem to work and keeps throwing an exception. Any alternatives so suggestions ?
     This works fine in my Flex Builder 3. 
    Thanks
    Hironmay Basu

    the issue is already reported here:
    http://bugs.adobe.com/jira/browse/SDK-22886?page=com.atlassian.jira.plugin.system.issuetab panels:all-tabpanel
    As a workaround, you can try using:
    http://www.websector.de/blog/2009/09/09/custom-applicationupdaterui-for-using-air-updater- framework-in-flex-4/

  • Air update

    I am about to cry...or break something atleast.
    VerifyError: Error #1014: Class air.update::ApplicationUpdaterUI could not be found.
    I am on cs5.5 flash pro.
    I am creating an updater.
    Library path set for:
    applicationupdater_ui.swc
    code:
    var appUpdater:ApplicationUpdaterUI = new ApplicationUpdaterUI();
                                  appUpdater.configurationFile = new File("app:/updateConfig.xml");
                                  appUpdater.initialize();
                                  appUpdater.checkNow();
    updateConfig:
    <?xml version="1.0" encoding="utf-8"?>
    <configuration xmlns="http://ns.adobe.com/air/framework/update/configuration/1.0">
         <url>http://afiadesign.com/vislaw/update.xml</url>
        <delay>0</delay>
    </configuration>
    app descriptor:
    <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
    <application xmlns="http://ns.adobe.com/air/application/2.6">
      <id>HeartMonitor</id>
      <versionNumber>1.0</versionNumber>
      <filename>HeartMonitor</filename>
      <description/>
      <!-- To localize the description, use the following format for the description element.<description><text xml:lang="en">English App description goes here</text><text xml:lang="fr">French App description goes here</text><text xml:lang="ja">Japanese App description goes here</text></description>-->
      <name>HeartMonitor</name>
      <!-- To localize the name, use the following format for the name element.<name><text xml:lang="en">English App name goes here</text><text xml:lang="fr">French App name goes here</text><text xml:lang="ja">Japanese App name goes here</text></name>-->
      <copyright/>
      <initialWindow>
        <content>HeartMonitor.swf</content>
        <systemChrome>standard</systemChrome>
        <transparent>false</transparent>
        <visible>true</visible>
        <fullScreen>false</fullScreen>
        <aspectRatio>portrait</aspectRatio>
        <renderMode>auto</renderMode>
      </initialWindow>
      <icon/>
      <customUpdateUI>false</customUpdateUI>
      <allowBrowserInvocation>false</allowBrowserInvocation>
    </application>
    update:
    <?xml version="1.0" encoding="utf-8"?>
         <update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
           <version>1.1</version>
           <url>http://afiadesign.com/vislaw/HeartMonitor.air</url>
           <description>This is the latest version of the Sample application.</description>
        </update>
    I don't know what to do?!?!?!?! Please save me from jumping out a windows!

    Ya I did.....
    import flash.display.MovieClip;
              import com.vislaw.utils.LoadImgSet;
              import flash.display.Stage;
              import flash.display.StageAlign;
              import flash.display.StageScaleMode;
              import flash.events.Event;
              import flash.events.MouseEvent;
              import flash.display.Sprite;
              import flash.utils.Timer;
              import flash.events.TimerEvent;
              import fl.events.SliderEvent;
              import flash.display.SimpleButton;
              import com.vislaw.utils.DragButton;
              import com.vislaw.utils.playControl;
              import com.vislaw.utils.LoadingALL;
              import com.vislaw.utils.Eraser;
              import com.vislaw.utils.magnify;
              import flash.net.SharedObject;
              import com.vislaw.utils.penTool;
              import com.vislaw.utils.highlightTool;
              import com.vislaw.utils.lineButton;
              import air.update.ApplicationUpdaterUI; <<<<<<HERE
              import flash.filesystem.File;
    This is very strange.....I had it working on my computer, than I went online and it started failing. I went through a couple issues that i fixed and this "VerifyError: Error #1014: Class air.update::ApplicationUpdaterUI could not be found."  is were I got stuck..Any other suggestions?
    The wierd thing is that i am using a cs5.5 and i am using applicationupdater_ui.swc..I thought this was something you can import without using a swc in the library path. Is there differnet applicationupdater_ui.swc, one for air 1.5 and one for air 2.5 and higher or do you use the same one?

  • AIR 3.2 RC1 Installing & Running Android .APK asks for an AIR update?

    I am packaging my app in Flash Pro CS5.5 using the overlay method with AIR 3.2 RC1 (everything is functioning correctly/publishing fine no issues).
    Then once i publish Air for Android directly to the device on application launch, this message pops up -  
    "This app requires a newer version of Adobe AIR.
    Update Abode AIR now?"
    Is there a new version or a different way of packaging the APK? as i heard you dont need AIR now you can package everything inside the APK, please can someone let me know would be appriciated! cheers  

    Hi,
    Sorry I hadn't gotten to your post yet.  I'm behind and still going through posts from a week and a half ago
    AIR isn't required for your operating system unless you use an application that depends on it.  Think of AIR like you would Java.  It's a platform/runtime for other applications to be built on.  If you don't use any application that was built with AIR (or Java) then there is no need for it to be installed.
    If you do have an AIR application installed that requires AIR, I would definitely recommend updating to the latest version just to make sure you have all of the security updates that we've provided.  You can do this by visiting get.adobe.com/air and downloading the latest version, which is 3.2.  Updating your OS will not update the AIR runtime.  You can also get updates by actually launching your AIR based applications.  AIR will notice that it's out of date and prompt you to install and update to the latest version.
    Since you haven't received any AIR update notifications, this leads me to believe you aren't actually using any AIR applications.
    You can always start the AIR uninstall process, if AIR applications are installed you'll get a dialog letting you know which applicaiton's will be affected.  You can choose to continue to uninstall or cancel at that point.
    Hopefully this makes sense.
    Chris

  • Air update, now video scrubbing has stopped working?

    Well ok, not exactly sure what's happened here, myself but... the main issue is this: I believe that since I did the most recent air update, video seeks no longer work while the video is paused.  Basically meaning, I can't scrub through a video any more.  No compiler errors, works fine in the flash environment, just stopped working (immediately after an adobe update) when running the actual air app.
    Details if you want 'em: I write somewhat large video apps where I work, and to help some of the others there, I've written some air apps that let them scrub through the videos, etc.  I'm quite certain it happened right after an air update, 'cause I was using one of the apps myself just fine, when an adobe update window appeared.  Pretty sure it was air.  Anyway, I let it do it.  Then when I went back to work, I could no longer scrub.  Tried re-installing air, but no go.  Then tried recompiling, but still nothing.  Oddly, like I said, I don't get compiler errors, and it works in the flash environment when I test movie.  Just won't work on the external air app.  Basically, I'm doing this:
    click on scrubber
       pause movie
       start scrubber drag
    while dragging scrubber
       seek to location based on scrubber position
    release scrubber
       stop scrubber drag
       resume movie
    When i release the scrubber, the movie will resume from the proper new location based on the final scrubber position, but the movie just sits frozen during the scrubbing process, so you can't see where you are in the movie while scrubbing.  I can display other stuff, like the scrubber position.  but the video just won't seek.  worked until the second I got that update.
    Anyway, been searching but havn't seen anyone else complaining about this.  Maybe air's not as popular as I wish it was.  It's even possible that my feeble old brain missed something and this is a windows 7 thing, but I'm quite certain I was using it and it was fine the instant it broke, 'cause that update window appeared and made me shut my app down to do the update.  Tried rolling back to a previous version of air, but that doesn't seem possible.  Thanks to anyone who has any ideas about this.

    I had the same problem(I couldn´t see myself neither the other person, but the other person could see me).
    I have solved it doing this:
    Log into your Gmail account > Settings > Labs. Enable Video Chat Enhancement lab. Save change. Restart Gmail. Test video.
    And now I can see myself and the other person.

  • AIR Update Proccess and the File System

    I have a client who’s using a 3rd party installer to install their  AIR. They’re doing this because they’ve got a large amount of content  (600mb) and the typical packaging process is falling over. We’ve got a  workable solution where we install the content into the app directory  (/Applications/OurApp) via the 3rd party installer after the AIR app is  installed, but we’re a bit concerned that the directory may get blown  away with a future update on our part using the standard air updater  process.
    We’ve tested on mac and windows and everything seems to be OK, ie our  content files seem to stay intact. I’m wondering though, is this just a  happy mistake? Is what we’re doing safe or should we go about it in a  different way? Should we be storing our content outside of the  application directory? I’m concerned this process may change in a future  version of AIR and all of our content will disappear.
    I know the forum is closing soon, but I figured this could be relevant  because it relates to future versions of AIR.

    This is a situation I'm dealing with -- where 3rd party java (DataCash credit card gateway) insists on accessing filesystem based resources, in particular binary files containing card information (bin ranges etc to work out what bankk/country issued a card). We have no control over how this accesses these two files; it insists on a filesystem based path location like "C://Java//DataCash-Java-2.0.10//cardinfo".
    Just feeding it a package location doesn't work, nor has using the classloader to point to the actual location to derive something like: "jar:file:/C:/Java/jboss-3.0.4/server/betex/tmp/deploy/blahblah/blah.ear/81.blah/blah.jar!/com/ourpackage/blah/blah" (even if I strip off the jar:file:/ bit)
    All we know about the client code is that the reference to the file is initialised using the File(String pathname) constructor of the java.io.File object.
    I'm currently looking at the jakarta commons VFS package for a solution, but without success so far (I have an odd compilation issue to resolve).
    So any tips/pointers greatly appreciated.

  • OMG, after last AIR update before current ALL my AIR apps will not work, HELP!

    I have 5 or 6 AIR based apps after I did an update last month, none of them will work. I just re-installed and updated AIR again today and re-installed all the apps multiple times and when I go to one it trys to open the last I installed for every app it only opens the last installed. App installions always end with "faled to open app" and in the log I see this "Error: Missing necessary file META-INF/AIR/application.xml" not sure?
    Windows 7 (all lastest updates)
    Latest Air (13.057 I believe?)
    How do I fix this, why did it break?
    Full log:
    http://ge.tt/2IDeU4b1/v/0?c

    Hello,
    I could install and run the AIR application successfully with AIR 4.0, 12.0 and 13.0.
    Looking into the log, it seems that "missing application.xml" and "Application Installer end with exit code 7" issues have been there from 2014-02-09, below is the detailed log seen from http://ge.tt/2IDeU4b1/v/0?c. This issue maybe caused by the application.
    Is there an application.xml under C:\Program Files (x86)\YourApplicationXXX\META-INF\AIR\ ?
    If possible, could a bug against this issue be logged in https://bugbase.adobe.com/, and upload the AIR application which does not work. That would be very helpful to triage and find the root cause for this issue.
    Thanks your support!
    ===================================================
    [2014-01-04:01:26:19] Launching subprocess with commandline c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Resources\Adobe AIR Updater -updatecheck
    [2014-01-04:01:26:20] Runtime Installer begin with version 3.9.0.1380 on Windows 7 x86
    [2014-01-04:01:26:20] Commandline is: -updatecheck
    [2014-01-04:01:26:20] Installed runtime (3.9.0.1380) located at c:\Program Files (x86)\Common Files\Adobe AIR
    [2014-01-04:01:26:20] Performing pingback request
    [2014-01-04:01:26:21] Pingback request completed with HTTP status 200
    [2014-01-04:01:26:21] Starting runtime background update check
    [2014-01-04:01:26:21] Clearing unused background update directory
    [2014-01-04:01:26:21] Begin Background update download from http://airdownload.adobe.com/air/3/background/windows/x86/patch/3.9.0.1380/update
    [2014-01-04:01:26:21] Unpackaging http://airdownload.adobe.com/air/3/background/windows/x86/patch/3.9.0.1380/update to C:\Users\Owner\AppData\Roaming\Adobe\AIR\Updater\Background
    [2014-01-04:01:26:21] Runtime update not available
    [2014-01-04:01:26:21] Unpackaging cancelled
    [2014-01-04:01:26:21] Runtime Installer end with exit code 0
    [2014-02-09:13:58:50] Application Installer begin with version 3.9.0.1380 on Windows 7 x86
    [2014-02-09:13:58:50] Commandline is: C:\Users\Owner\Downloads\SPPro\SocialPostingPro-4.air
    [2014-02-09:13:58:50] Installed runtime (3.9.0.1380) located at c:\Program Files (x86)\Common Files\Adobe AIR
    [2014-02-09:13:58:53] Unpackaging file:///C:/Users/Owner/Downloads/SPPro/SocialPostingPro-4.air to C:\Users\Owner\AppData\Local\Temp\fla3EA0.tmp
    [2014-02-09:13:58:53] Application signature verified
    [2014-02-09:13:58:53] Unpackaging/validation complete
    [2014-02-09:13:58:53] No app located for appID 'com.igs.socialpostingpro' and pubID ''
    [2014-02-09:13:59:06] Converting unpackaged application to a native installation package in C:\Users\Owner\AppData\Local\Temp\fla729C.tmp
    [2014-02-09:13:59:06] Native installation package creation succeeded
    [2014-02-09:13:59:06] Starting app installation to C:\Program Files (x86). Installing app com.igs.socialpostingpro version 1.0.8 using the source file at file:///C:/Users/Owner/Downloads/SPPro/SocialPostingPro-4.air
    [2014-02-09:13:59:06] Installing msi at C:\Users\Owner\AppData\Local\Temp\fla729C.tmp\setup.msi with guid {050F1169-D97B-B822-C803-D727DB278A96}
    [2014-02-09:13:59:17] Got an unexpected fatal error while accessing app for launch: Error: Missing necessary file META-INF/AIR/application.xml
    [2014-02-09:13:59:41] Application Installer end with exit code 7

  • Why can't we get a straight answer from Apple about updater issues?

    Why are there thousands and thousands of posts from people all having the same issue? We try to update IPod software using latest updater, and it causes IPod to no longer be recognized. All we want is someone from Apple to FIX THE PROBLEM! Yet all we get are refferals to complicated articles that never seem to work for at least half the people. Clearly it is a problem with these updaters. WHY IS APPLE NOT FIXING THIS ISSUE? Can anyone give me a straight answer!?

    Hi Wolf,
    Welcome to Apple Discussions
    "thousands and thousands of posts"
    There are roughly 10,300 thread with 50,000 posts in the iPod Nano forum, and there are probably another 500,000 who don't even know it exists. I don't there there has been a thousand posts on the updater issue. It may seem like thousands upon thousands, but don't forget; you're at an Apple Support Forum.
    "All we want is someone from Apple to FIX THE PROBLEM!thousands and thousands of posts"
    There's no need to "shout". I don't think Apple is going to hear you from shouting in a user to user forum. Nor will you probably get a answer (here) from Apple for the same reason. I have a -------- (straight) answer for you. I don't know what's going on specifically (no one really knows in this forum because they are all users. Anyone who would know won't say), but I can assure you that Apple isn't ignoring the issue. They are the quickest to respond to any problem that comes their way. If you would like to get Apple's attention, I don't suggest ranting and raving in the iPod user to user forum. I suggest submitting polite feedback to Apple here.
    Jon

  • Is there a consensus on how to solve security update issues?

    hi,
    i'm writing to you from a PPC G4 (AGP graphics) that will self-destruct by the time i switch off and (attempt) to re-start tomorrow. i will then need to do a re-install, just to see if i have gotten any replies (grinds teeth to the root). it will probably be my 8 th re-install in the past month. i just can'st takes no mores, Cap'n
    <exasperation>deep breath... each time i have done a clean install, zero-ed all data when erasing (7 times over, on this occasion), repaired permissions before and after each software update, and followed every advice i could find via google to pre-empt another "Error: underlying task reported failure on exit" and the inevitable hanging grey screen; i have earned nothing but another Disk Utility report of the same problem. my HD seems to be OK - Disk Utility and Disk Warrior both say it's "verified" by SMART (although i've read this could be no assurance...). it's 40 GB, nothing else installed but NetBarrier; nothing saved on it (just 3GB of OS).
    i've searched this forum over the last weekend and come across a diverse range of methods in resolving software update issues. i have tried downloading the security update and safari 3.2 directly from the site and bypassing Software Update- to no avail (but noticed that they are quite larger in MB than via Software Update??).
    the one suggestion the intrigued me was installing the update via Terminal. why would this be any different? the worst thing about this is that there is no universal way that'll work for all, just individual solutions for different macs??? could my problem be exacerbated by using the double layer (double the permissions to fix?) of a Panther OS with Tiger Upgrade disk?
    when i last tried to resolve the "error" with safe mode, fsck and DU Repair Disk/Permissions, which initially failed, i resorted to Disk Warrior, which re-built the directory, and "fixed" the HD. when i re-tried fsck it said the HD was "ok", but i still had the "error: underlying task..." on DU?
    is there an issue with the Security Update oo8 because it's PRIMARILY for 10.5 and not Tiger? why have some encountered this problem and others escaped any seeming conflicts ? is this problem also caused by JAVA updates (there are, after all, 4 updates!)
    more importantly, WHAT CAN I DOOOOOOOO?
    thank you

    looking at your suggestion to check /Library/Startup items in the concurrent thread ("Help needed after installing Security Update 2008-008"), i recalled that the only thing i have in this file system is 3 folders concerning Intego, NetBarrier and Virus Barrier. one of these contains the NetBarrier x4 daemon which has no image, just the apple "pencil, ruler, pen on paper" "A" image. i don't think it correctly downloaded, but this the case in every instance.
    i'm running netbarrier x4 10.4.5 updated and downloaded on installation. intego Support says that there should be nothing in my "Startup/Login items". i thought they meant Login items (users>login items) because when i take the folders out of my "/Library/Startup items", NetBarrier fails to "initialize".
    intego is now on newtbarrier x5, but they say x4 is fully compatible with Tiger???
    my baby maybe getting on, but it's strong enough, i just need to know what's bugging it!

  • Unable to install Adobe Air Update

    I am unable to install an Adobe Air update.  I am running Windows7, getting error code 80040154.  Could it be Kapersky anti virus software blocking?

    Thank you for your help.  I have suspended Kapersky but I cannot find Air when I search in the Programs and when I try to install I now get a message saying 'it may be your administrator blocking you'.  I am the only user and set up as the Administrator but do not know how to check if this is the case.
    I have managed to install the application that needs Air on an old XP notebook.  Much Appreciation for your help. RJ

Maybe you are looking for

  • Credit Management requirement for cash business

    Hi Gurus, Actually my client business is a cash business, there is no credit concept for the customers. My requirement is when i create a sales order, system should check the credit balance of the customer(Business receives the payment through cheque

  • How to automatically close PR ?

    Hi all, PR item has an indicator : CLOSED . It is said: Purchase Requisition Closed Flags a purchase requisition as closed, that means that no further purchase orders are to be created for this purchase requisition. Use You can: Set this indicator ma

  • How touse an external NAS to hold your iPhoto library?

    Hi, I'm new to Mac. I want to start using iPhoto which seems to be amazing. Problem: I have a NAS hooked up to my wireless network at home. Both my wife and I always download our camera's photos to the NAS so they are safe and easy to find from our d

  • IPhone could not be restored. An unknown error occurred (36)?

    I have an iPhone 4s. Earlier this week the battery died and when I plugged it in to charge instead of it turning on it showed the connect to iTunes logo. I did this and it said my iPhone needed to be restored. It updated to the latest software as I h

  • Fail to build SSIS/SSAS projects via VS2012 command line (devenv.exe) with SSDT BI tool installed

    Hello, I installed recently released SSDT BI tools for VS2012 and I can work on my existing SSIS/SSAS projects all well in VS2012. But when I try to build my SSIS/SSAS projects via the command line of VS2012, such as devenv.exe mySolution.sln /rebuil