I don't think this has anything to do w/you updater code. You do need the applicationupdater swc files, but the fact that it's working suggests to me that they are already in your class path.
The problem sounds like the installer is creating a bad shortcut. I would investigate the following: 1. Where does the shortcut point before the installer runs and installs the new update? 2. Where does the shortcut point after the installer runs and installs the new update? 3. Where should it point? 4. Are you adding items to the start menu? Where do they point? The items in 1, 2 and 4 should point to the same .exe location, as you cannot change the location or filename of the .exe via an update. Maybe there are some troublesome characters in the path/filename that are causing confusion when the shortcut gets created (e.g. a slash in the filename)? On Fri, Oct 3, 2014 at 9:39 AM, Jack Ring <jackri...@gmail.com> wrote: > I didn't change anything else either. It updates - but it just breaks the > Desktop Alias on Windows 7 and above... > I am using the built in AIR installers and badge page and the built in air > update ui classes... > > Do I need a to include a .swc to use this? It is working without one. > > I am using AIR 14.0 SDK on FB 4.7 - maybe I'll try updating to AIR 15 - any > input on where instructions to do this would be to do this? > > > My code... > > import air.update.events.UpdateEvent; > import air.update.ApplicationUpdaterUI; > > protected var appUpdater:ApplicationUpdaterUI = new > ApplicationUpdaterUI(); > > init... this.checkUpdate(); > > appUpdater.updateURL = "http://*********/update.xml";; > appUpdater.addEventListener(UpdateEvent.INITIALIZED, onUpdate); > appUpdater.addEventListener(ErrorEvent.ERROR, onUpdaterError); > appUpdater.isCheckForUpdateVisible = false; // don't ask to check > appUpdater.isDownloadUpdateVisible = false; // don't ask to do > appUpdater.isDownloadProgressVisible = false; // don't show download > progress > appUpdater.isInstallUpdateVisible = false; // don't ask to launch the > updator and install the app. > appUpdater.initialize(); > } > > protected function onUpdate(event:UpdateEvent):void { > appUpdater.checkNow(); > } > > protected function onUpdaterError(event:ErrorEvent):void > { > Alert.show(event.toString()); > } > > How do we know that this > > On Wed, Sep 24, 2014 at 4:30 PM, Scott Talsma <sc...@talsma.tv> wrote: > > > Jack, > > > > I am doing something similar, using the built-in .air installers and a > > badge page. My build script increments the version number in the > -app.xml > > config file. (I'm using the built-in update ui classes from AIR.) > > > > When I run a .air file to update a previous installation, I see it delete > > the desktop shortcut, and then creates a new one. I don't have any > issues > > with the shortcut breaking. Are you dealing w/user-created shortcuts? > > FWIW, in my experience, if you change the name of the .exe, the upgrade > > process tends to break anyway. > > > > Scott > > > > On Tue, Sep 9, 2014 at 3:23 PM, Jack Ring <jackri...@gmail.com> wrote: > > > > > ***** > > > > > > Is there any chance that this is related to Apache Flex SDK - rather > than > > > an Adobe AIR issue? > > > > > > ***** > > > > > > When I push out an update for one of my desktop AIR apps that a client > > may > > > have installed on a Windows 7 or 8 machine, the shortcuts to the app > > become > > > broken and therefore useless. This gives my clients the appearance that > > my > > > application is busted when it is not. I continuously have to instruct > > > Windows 7 and 8 users to delete any shortcuts and go to the install > > > directory and create a new shortcut. > > > > > > > > > Note that I use the Apache Flex 4.13 build (My IDE is FlashBuilder 4.7) > > AND > > > that I only tally the version number in the *-app.xml file as I always > > > have. > > > > > > > > > Thanks, > > > > > > Jack Ring > > > > > >
