There are no known bugs with using external linkage. I would create a link report and find the asset in there. The compiler may be generating a different name for the asset than before so I would check for that.
I made the link reports for both FB 4.6 and FB 4.7.
In FB 4.6 one the external assets are correctly marked under <external-defs>
While in FB 4.7 they are exported as if they were merged into code.
Note. When I build this with the new compiler using ant/mxmlc and
compiler.external-library-path property the results are what you would expect (i.e externally linked).
When I compare the FB 4.7 link reports between having the setting merged into code or externally linked, there does not seem to be very little difference, and no difference at all how the assets appear.
It seems that FB 4.7 is simply ignoring the setting
As long as the assets aren’t in frame1 I would expect them to be external. Could you provide some simple projects that demonstrate the problem so I can investigate?
here is a demo project set up similar to the main project having the problem.
If you adjust the linkage on the directory ./export/normal/swc to external, on the web project it makes absolutely no difference. While in FB 4.6 or using ant build it is smaller and requires a swf to be loaded at runtime.
That being said, I am now in the process of seeing if the method we are trying to use will actually work, since the iOS packager refuses to make a release build if it cannot find the class definitions at compile time.
The idea is basically that the compiler uses external linkage to flash assets, and then depending if the device is retina or not it loads the appropriate swf.
There is a bug in FB 4.7 with the "Add SWC Folder..." feature in the "Library Path" tab. As you noticed all the libraries, regardless of linkage, are reported to the compiler as being "Merged into code". The workaround is to use the "Add SWC..." feature to add each SWC individually and change its linkage to "External".
Sorry for the inconvenience.
Thanks. This is a bit annoying since we are using about 50 asset .swc that we want to link externally.
Any estimates when a Flash builder 4.7 patch will be made available? Since this seems to be far from the only problem with it. I frequently go back to 4.6 or just ant/command line builds when I get frustrated.