Main Page
From Flexerrorcodes
(→Other useful liniks) |
|||
| Line 9: | Line 9: | ||
*[http://livedocs.adobe.com/flex/201/langref/runtimeErrors.html Run-time errors] | *[http://livedocs.adobe.com/flex/201/langref/runtimeErrors.html Run-time errors] | ||
| - | =Other useful | + | =Other useful links= |
* [http://www.bodhost.com/web-hosting/index.php/2007/08/10/http-error-codes/ HTTP Status Code Information] | * [http://www.bodhost.com/web-hosting/index.php/2007/08/10/http-error-codes/ HTTP Status Code Information] | ||
Revision as of 13:16, 30 October 2007
Contents |
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 they 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:
Other useful links
Run-time errors
| Error code | Description | Solution or workaround |
|---|---|---|
| 1009 | TypeError - Cannot access a property or method of a null object reference | When using modules, be careful using shared code between modules that share the same classes or assets. If those modules share managers, then the developer must be careful. One common mistake is to accidentally bring in Managers (PopUpManger, DragManager) in a module and use from another module. For more information, see http://thanksmister.com/?p=54.
If you get this error from clicking a cell an ItemRenderer, add the following line to the renderer's "override public function set data(...)": super.data = value; |
| 1030 | VerifyError | Make sure you are running the current version of the player. |
| 1034 | TypeError: Type Coercion failed: cannot convert class to class. | This is a common error when two modules or SWFs try to share a class across ApplicationDomains. |
| 1068 | VerifyError: classname and classname Cannot be reconciled | One developer who experienced this error reports that restarting the application server fixed the problem. |
| 1151 | A conflict exists with definition definition in namespace namespace | The declaration of a variable of a certain type cannot be overridden to a different type in the same scope. |
| 1502 | A script has executed for longer than the default timeout period of 15 seconds. | For Flex Charting, ensure that you're using unique category names in the category axis. |
| 2032 | HTTP request error | The referenced resource does not exist or the swf is trying to access a file across a restricted domain. |
| 2082 | Connect failed because the object is already connected. | If your application dies unexpectedly, it can leave the history LocalConnection in a hung state:
Another cause of this error is using managers (or other singletons) within a module before they're loaded by the main application. There's a lengthy thread on this topic in flexcoders here: http://tech.groups.yahoo.com/group/flexcoders/message/63829 |
| 2137 | Sandbox security violation | Possible solutions include:
|
| SWF is not a loadable module | If you load modules across domains, the target domain must implement a crossdomain.xml file with the appropriate permissions. |
