Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
Adobe Flex SDK 4.1 (Release)
-
None
-
None
-
Affected OS(s): Linux
Affected OS(s):
Browser: Firefox 3.x
Language Found: English
Description
Steps to reproduce:
1. Compile a flex swf with "static-link-runtime-shared-libraries" set to "false"
2. open swf with debug flash player
3. receive error
Actual Results:
Compiling with the Flex SDK 4.1.0.16076 and using the default RSLs in flex-config.xml gives me the following error as of today when running the output swf in the debug player:
Error #2046: The loaded file did not have a valid signature.
Failed to load RSL http://fpdownload.adobe.com/pub/swz/tlf/1.1.0.604/textLayout_1.1.0.604.swz
Failing over to RSL textLayout_1.1.0.604.swz
Warning: Ignoring 'secure' attribute in policy file from http://fpdownload.adobe.com/pub/swz/crossdomain.xml. The 'secure' attribute is only permitted in HTTPS and socket policy files. See http://www.adobe.com/go/strict_policy_files for details.
Error #2046: The loaded file did not have a valid signature.
Expected Results:
swf should load with RSLs from fpdownload.adobe.com
Workaround (if any):
set "static-link-runtime-shared-libraries" in flex-config.xml to "true"
This 'fix' increases the size of the output swf by about 400kB. I've also found several related issues to this regarding RSL signatures.
http://bugs.adobe.com/jira/browse/SDK-28016
http://stackoverflow.com/questions/3531649/error-when-converting-a-site-from-flex-3-to-flex-4
http://stackoverflow.com/questions/4218779/can-one-rely-exclusively-on-adobe-for-flex-flash-rsls-to-avoid-using-own-bandwi
This leads me to believe that relying on RSLs from adobe is not such a good idea. I'd rather force customers to download the extra payload in the initial swf than risk the app not loading because of a signature expiration or update from adobe.