I have a largish mobile / Flex project that I am compiling for debug / review / test.
In "ad hoc" release mode, it runs perfectly.
In "Fast" mode, it runs perfectly.
In "Standard" mode debug...
[SWF] gustavo_mobile_as_app.swf - 35,408,264 bytes after decompression
TypeError: Error #1009: Cannot access a property or method of a null object reference.
at mx.resources::ResourceBundle()[C:\svn\4.y\frameworks\projects\framewo rk\src\mx\resources\ResourceBundle.as:121]
at mx.resources::ResourceManagerImpl/installCompiledResourceBundle()[E:\ dev\4.y\frameworks\projects\framework\src\mx\resources\ResourceManager Impl.as:396]
at mx.resources::ResourceManagerImpl/installCompiledResourceBundles()[E: \dev\4.y\frameworks\projects\framework\src\mx\resources\ResourceManage rImpl.as:306]
at mx.resources::ResourceManagerImpl/processInfo()[E:\dev\4.y\frameworks \projects\framework\src\mx\resources\ResourceManagerImpl.as:450]
at mx.resources::ResourceManagerImpl()[E:\dev\4.y\frameworks\projects\fr amework\src\mx\resources\ResourceManagerImpl.as:133]
at mx.resources::ResourceManager$/getInstance()[E:\dev\4.y\frameworks\pr ojects\framework\src\mx\resources\ResourceManager.as:117]
at mx.styles::StyleManagerImpl()[E:\dev\4.y\frameworks\projects\framewor k\src\mx\styles\StyleManagerImpl.as:380]
at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::kickOff()[E:\dev\4.y\frameworks\projects\framework\src\mx\managers\SystemMana ger.as:2815]
at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::preloader_completeHandler()[E:\dev\4.y\frameworks\projects\framework\src\mx\managers\SystemMana ger.as:2723]
at mx.preloaders::Preloader/timerHandler()[E:\dev\4.y\frameworks\project s\framework\src\mx\preloaders\Preloader.as:542]
I have run through the code and there is an undefined reference for a Flex generated method. Because it happens so early on, it just kills the app and there is no way to work around it... yet I _NEED_ standard mode to test against as not all issues that occur occur in Fast mode...
Obviously, I have done nothing to modify core Flex functionality, and it works fine in the other compile modes, so can anybody direct me to a good way to resolve this?
Also, can anybody direct me to the appropriate bug base for Flex / Flash Builder? All the links I can find are either broken or won't let me in.
It's easy to feel abandoned by the Adobe team regarding the Flex SDK. From last year they have moved to the Apache project and as far as I'm aware they are in charge of dealing with bugs in relation to the compiler. (A shame, because I only just recently bought Flash Builder outright for 1000 dollars and there's absolutely NO support for features and bugs) I've had problems in the past with the compiler/linker running out of JVM memory for a large application. The Java SDK located inside of the Flash Builder directory has a config file where you can change the memory allocation as described here:
Though probably that isn't your problem. Since Flex moved to Apache... if you have filled in the form and received the complimentary upgrade to Flash Builder 7.0, you can try upgrading your Flex SDK to Apache's version 4.9 as outlined here:
Best of luck!
But no, not my problem. I can compile fine, I just can't run the app afterwards - it throws a #1009 during pre initialisation that prevents any of my code _EVER_ coming into play.
I have compiled projects where this doesn't happen, so it _could_ be down to my code, but equally, the code that is affected is Flex generated code that I have no involvement with... So...
It is the linker that decides which functions make it into the final executable. If there is a bug in the linker with your current Flex framework, there's a small chance the Apache team have already dealt with it. If they have not then I'd suggest placing a bug report with the Apache Flex project. :-)
I got to the bottom of it, I think.
When the resource bundle declaration is included in main app, it causes the bug, when it is not, it doesn't. I have moved it to firstView now for the moment, but am a bit irritated to do that as I am declaring a globally referenced resource bundle.