Comments on: Can an AIR application restart itself?

By: How to restart an AIR application from code | hufkens.net

How to restart an AIR application from code | hufkens.net — Tue, 10 Mar 2009 11:45:54 +0000

[...] Joy of Flex blog wrote an article “Can an AIR application restart itself?” I tried it out, but this [...]

By: czBin’s RIA Blog » Blog Archive » AIR程序可以自动重启吗？

czBin’s RIA Blog » Blog Archive » AIR程序可以自动重启吗？ — Mon, 01 Dec 2008 09:07:38 +0000

[...] http://www.colettas.org/?p=267 [...]

By: jim hayes

jim hayes — Sun, 30 Nov 2008 00:37:23 +0000

Apologies, the info I provided for getting the application and publishers ID is now old and out of date, for current versions of AIR it’s simpler :

var appID:String = nativeApplication.nativeApplication.applicationID;
var pubID:String = NativeApplication.nativeApplication.publisherID;

By: Nick Kwiatkowski

Nick Kwiatkowski — Sun, 12 Oct 2008 13:57:51 +0000

Have you thought about dropping a sophomore file on the filesystem and then trying your launchApplication? In the section of your app where you check to see a version is already running, you could check to see if the sophomore file exists and ignore the checking code (making sure to delete the file on the filesystem at the same time).

In a .NET app I had to write a long time ago, we used the above approach. The file we ended up writing to disk was actually a struct of the information that we wanted to send to our server. We let the clean copy of our app send the data (we were under the assumption that one of the errors that could occur could prevent us from communicating properly to our syslog server).

Just a thought!

By: Javier Julio

Javier Julio — Fri, 10 Oct 2008 00:58:29 +0000

I second George’s comment. Well said. I’ve been wanting to do this for awhile since I had thought of a nice component this would make. Just like you see in Mac or Windows, you get an alert style prompt to send an error report to the server. But without globally error handling this is near impossible. If possible extremely painful.

By: Jim Hayes

Jim Hayes — Thu, 09 Oct 2008 23:50:26 +0000

// get applicationID and publisher ID //
var descriptor:XML = nativeApplication.nativeApplication.applicationDescriptor;
var ns:Namespace = descriptor.namespaceDeclarations()[0]; var appID:String = descriptor.ns::applicationID;
var pubID:String = descriptor.ns::publisherID;

By: George

George — Thu, 09 Oct 2008 22:18:35 +0000

David,

I’m curious how you globally trap “unrecoverable errors” and report meaningful information back to your servers for diagnosis. I’m developing a moderate size Flex/AIR app and the lack of a global error handling mechanism is quite frustrating. This is one of the most glaring oversights in Flex/AIR.

I’m curious how you handled this in Buzzword. I’ve tried numerous approaches to global error handling in Flex, but none are ideal. And even if one could catch all errors globally, stack trace information is not normally available making diagnosis much harder.

This could and should be much easier…

By: 创建一个可以自我启动的AIR应用是否可能？ | 中文Flex例子

创建一个可以自我启动的AIR应用是否可能？ | 中文Flex例子 — Thu, 09 Oct 2008 14:51:11 +0000

[...] http://www.colettas.org/?p=267 [...]