It takes a few hours of setup work and then half an hour to an hour each time you create a new build.
I've created a class that helps with the process here <http://bit.ly/2jQ73yh>. Once you set it up you don't have to change the code. The setup instructions are in the class ASDocs. They may be slightly outdated. Let me know. Then in the future you update the application descriptor online. For the updating process I use the steps listed here <http://bit.ly/2lcQc5K>. Whenever you upload a new version and the user opens your app a window will pop up that asks them if they want to update. If they click yes then your existing application is updated. All the users existing data is preserved. On Sat, Feb 4, 2017 at 9:36 PM, bilbosax <waspenc...@comcast.net> wrote: > I haven't looked into it yet, so thought I would start by asking the wise > people here. I have written an AIR app that runs on the desktop, with a > version that works on mobile as well. If I ever add a new feature or > improve the efficiency of the code, I want to offer users updates that they > can download from the app store or from my website for the desktop app. > How > hard is it to get an AIR app to update? And by update, I mean totally > replace the existing application with the new application, I am concerned > that it will just install a new application next to the existing > application > instead of replacing it. > > > > -- > View this message in context: http://apache-flex-users. > 2333346.n4.nabble.com/Updating-a-Program-tp14613.html > Sent from the Apache Flex Users mailing list archive at Nabble.com. >
