Main Page

From Flexerrorcodes

Revision as of 16:09, 21 February 2007

Flex and ActionScript Error Codes

One of the great things about working on the Flex development team is seeing how people create these amazing applications; things you never would have thought possible. However, the flip side of that is that when people are developing things you never would have thought possible, they get errors you never would have thought possible. This page is an attempt to capture and catalog Flex and ActionScript compiler and run-time errors, along with the environment in which the occur, and what it took to fix them.

Existing Documentation

Before you add an error to this page, please check out the existing error-code documentation. It may be covered already/

• Compiler warnings
• Compiler errors
• Run-time errors

Flex errors

Flex compiler errors

Flex run-time errors

   <tdConnect failed because the object is already connected.</td>
   <td>
    If your application dies unexpectedly, it can leave the history LocalConnection in a hung state.  One workaround is to shut down all instances of the Flash Player, including all browsers, and Yahoo IM, then you should be all set. A code-based workaround is as follows:

If connecting to a named LocalConnection "A" fails, you can try setting up a temporary callback LocalConnection and then invoke a send() to connection "A". If the owning instance is running it receives the call to connection "A" and should ping back over the temporary connection and you'll know that the connect failure is legitimate because the owning player instance is running. If you don"t hear back after 5 seconds (magic number) the Player assumes that connection "A" is orphaned and cleans up the shared memory, and at this point you can retry your connect() and it should succeed.

    </td>

ActionScript errors