This content has been marked as final. Show 7 replies
I rebuilt the projects in Flex 2.0.1 and the error when away. (???)
I had the same problem, but rebuilding the project did not fix it.
Instead, I had to delete the project in FlexBuilder (not deleting the source files), then to recreate a new project with the same name.
The new project automatically reuses existing source files, and mysteriously, the error goes away !!!
However, on the application using this SWC, I now have an "Internal build error, please check error log"
Of course, there is no error log in the Flex SDK....
Aaarrgghh... yep this just happened to me when I was updating one of my libraries!
I get the "unable to export SWC oem" error, and then when I tried rebuilding my projects, the projects using my my SWC gives a lovely "unable to open "c:\lib\mySWC.swc".
I'm now completely stuck as I can't run my projects without this SWC. I'll have to go back to the previous version until this BUG is sorted
By "rebuilding" the project I meant not simply recompling but creating a fresh project in Flex Builder 2.0.1.
I've the same problem. When using my SWC, two errors appear
"Connect failed because the object is already connected."
TypeError: Error #1009: Cannot access a property or method of a null
Will Adobe resolve or comunicate on this bug ???
I resolved the problem reading the isntallation instructions :(
When opening an existing project, I had to launch the following command FlexBuilder clean -vmargs -Xmx512m.
But it remained the problem Connect failed because the object is already connected." related to my swc.
I solved it when I discover with a step by step debug that it was caused by the history management. I disable it in the compiler options.
I do not know why the history management has a different behaviour from flex version 2 to version 2.0.1...
Mister Adobe, any ideas ?
I ran into that problem when using an [IconFile] metadata tag that refers to a file that does not exist. In that case, there is no entry in the Eclipse log to indicate the error. It also happens when you have the .swc file open in another application (at least it does in Windows), but at least there is an error in the log for that one.