Home > Flash Player 10, flex, tips & tricks > The infamous Error #2044: Unhandled StatusEvent:. level=error, code= on LocalConnection

The infamous Error #2044: Unhandled StatusEvent:. level=error, code= on LocalConnection

July 24th, 2009

This is a blog post to all that was almost to throw their computers out of the window because they got "Error #2044: Unhandled StatusEvent:. level=error, code=" trying to communicate through LocalConnection.

So I am trying to send a message from a Flex application running in Flash Player to an AIR application. In the AIR application (called testAIR) I have something like:

private function initApp():void {
	var inbound:LocalConnection = new LocalConnection();
	//only allow connections from localhost
	inbound.client = new Object();
	//this is the function that will be called by the Browser App
	inbound.client.notifyPayment = function test():void {

pretty straightforward, right from the book.

In the Flex app I just do:


You might think that this should work. Well … NOT.  This is because in the AIR app the inbound LocalConnection is a variable that is declared in the local scope of a method. Now I was expecting that when I call  the connect method the inbound object will be referenced by another object (some LocalConnection manager, or event handler) and it will not get garbage collected after the method ends. Well, apparently is not the case. Either there is a bug in AIR, either this reference is a weak reference so it gets garbage collected. This means that by the time you try to send the message from Flash Player your inbound object is long gone!

The resolution is quite simple. You just need to reference the inbound object somewhere else, making him a member of class or something. In my case I just declare it as a private variable inside my MXML component:

private var inbound:LocalConnection = new LocalConnection();

private function initApp():void {
	//only allow connections from localhost

Hope this will help someone :)

Categories: Flash Player 10, flex, tips & tricks Tags:
  1. George
    July 24th, 2009 at 12:12 | #1

    This happened to me also. The sad thing was that I initially had the variable declared as a class property and then, I accidentally moved it as a local variable in a function. The behaviour was exactly the same (and I wasn’t using AIR, but the web browser player).

    I also collected a few reasons for why this error might happen :

Comments are closed.