Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Cannot Reproduce
-
Adobe Flex SDK 3.5 (Release)
-
None
-
None
-
Affected OS(s): All OS Platforms
Affected OS(s): All OS Platforms
Browser: Other (specify version)
Language Found: English
Description
Steps to reproduce:
1. Unpack the attached zip archive and double-click the Swizzle_3.5.swf
2. This was compiled against the 3.5 swz and SDK with the following command:
mxmlc --runtime-shared-library-path+=swcs/framework_3.5.0.12683.swc,rsls/framework_3.5.0.12683.swz,,rsls/framework_3.5.0.12683.swf --runtime-shared-library-path+=swcs/rpc_3.5.0.12683.swc,rsls/rpc_3.5.0.12683.swz,,rsls/rpc_3.5.0.12683.swf -output=Swizzle_3.5.swf -source-path+=. Swizzle.mxml
3. In the Flashlog, you should see:
[trace] Error #2046: The loaded file did not have a valid signature.
[trace] Failed to load RSL rsls/framework_3.5.0.12683.swz
[trace] Failing over to RSL rsls/framework_3.5.0.12683.swf
[trace] Error #2046: The loaded file did not have a valid signature.
[trace] Failed to load RSL rsls/rpc_3.5.0.12683.swz
[trace] Failing over to RSL rsls/rpc_3.5.0.12683.swf
Expected Results:
If instead you run the Swizzle_3.4.swf, the signed RSLs are loaded correctly.
Workaround (if any):
Cannot use signed RSLs with the Flex 3.5 release build of the framework.
See the rakefile.rb inside of the attached archive for more details, and to confirm build specifics.