It's possible the two machines are compiling with different SDK 
versions even though the RSL URL is the same. It is a known problem 
that when you switch to a different SDK, the RSL URLs are not 
updated to match the new SDK.

To debug the issue you can you the "-keep" compiler option to keep 
the generated source. In the "generated" folder look for a file 
named "_{your app name}_mx_managers_SystemManager-generated.as". 
Inside of this file find the "info()" method. In there you will see 
a "digests" field(see below). 

    override    public function info():Object
    {
        return {
            backgroundColor: "white",
            cdRsls: [{"rsls":
["framework_3.0.0.477.swz","framework_3.0.0.477.swf"],
"policyFiles":["",""]
,"digests":
["ca055b87d42f411598ab8d0aac9447ccf1318dc7da82f4e7a5e1bfa6e5c5184e","
ca055b87d42f411598ab8d0aac9447ccf1318dc7da82f4e7a5e1bfa6e5c5184e"],
"types":["SHA-256","SHA-256"],
"isSigned":[true,false]
}]

This is the digest that is causing the digest mismatch. Compare the 
digests fields generated by the two machines. If the digests are 
different then it means you are compiling against different versions 
of framework.swc.

On the topic of RSL information, I may be biased but I think this is 
one of the better sources of information: 
http://www.adobe.com/devnet/flex/articles/flash_player_cache.html


-Darrell

--- In [email protected], "Kenneth Sutherland" 
<[EMAIL PROTECTED]> wrote:
>
> Yes I know that you need to point at the same framework file etc.  
This is exactly what we are doing.
> 
>  
> 
> For example in flex builder the framework path on both our 
machines is set to 
‘/swf/flex_framework/3.1/framework_3.1.0.2710.swf’ and if you 
look at the request from a tool such a fiddler or service capture 
you can see the request being made and it does get the required swz 
& swf but it gives you a digest error if the circumstances are the 
same as point 2 below.
> 
>  
> 
> Both versions of flexbuilder are the same.
> 
>  
> 
> So we have App1 built on PC 1, App2 built on PC 2 and 
framework_3.1.0.2710 taken from PC 1.
> 
>  
> 
> So what happens is
> 
> 1)      The user already has the 3.1 framework cached, both App1 & 
2 both work fine. 
> 
> 2)      The user does NOT have the framework cached, only App1 
will work, App2 will give a RSL error even though you can see it get 
the file from the server when you view it through a HTTP tool. 
(digest mismatch)
> 
>  
> 
> Any pointers? Anyone else had this.  I’d have though it was a 
fairly common thing to do (have a single framework file referenced 
by several apps generated by different programmers).
> 
>  
> 
> Cheers.
> 
>  
> 
>  
> 
>  
> 
> From: [email protected] 
[mailto:[EMAIL PROTECTED] On Behalf Of gabriel
> Sent: 26 November 2008 16:28
> To: [email protected]
> Subject: Re: [flexcoders] framework issues
> 
>  
> 
> On Wed, Nov 26, 2008 at 3:25 AM, Kenneth Sutherland
> <[EMAIL PROTECTED] ><mailto:kenneth.sutherland%40realise.com> 
> wrote:
> > [...] worked just fine until we got someone else other than
> > myself to build the final application swf files.
> 
> > Am I missing some settings?
> 
> remember that the cached framework is just another (albeit signed) 
rsl. you
> have to make sure that, when you compile, your -runtime-shared-
library-path is
> correctly set up (and consistently set up between different 
developers so that
> the code is compiled against the same version of the library).
> 
> here's a chunk of one of the config.xml i use when compiling for 
framework
> caching. (i use command line fcsh, so i prefer to use the xml to 
just be able
> to type mxmlc -load-config config.xml on the fcsh, but you can 
turn it into
> -runtime-shared-library-path=... etc. command line argument syntax 
if you need
> to).
> 
> <runtime-shared-library-path>
> <path-element>/opt/flex3sdk/frameworks/libs/framework.swc</path-
element>
> <rsl-url>framework_3.1.0.2710.swz</rsl-url>
> <policy-file-url></policy-file-url>
> <rsl-url>framework_3.1.0.2710.swf</rsl-url>
> <policy-file-url></policy-file-url>
> </runtime-shared-library-path>
> 
> <static-link-runtime-shared-libraries>false</static-link-runtime-
shared-libraries>
> 
> the best resource that i've found for all these things is 
the 'building and
> deploying flex 3 applications' pdf from the adobe website.
> 
> HTH,
> gabriel.
> 
> BTW, does someone knows how to determine which framework versions 
does one
> have already cached?
> 
> -- 
> gabriel montagné láscaris comneno
> http://rojored.com
> t/506.8367.6794
> 
>  
> 
> Disclaimer 
> -------------------------------------------------------------------
------------------------
> This electronic message contains information which may be 
privileged and confidential. The information is intended to be for 
the use of the individual(s) or entity named above. If you are not 
the intended recipient, be aware that any disclosure, copying, 
distribution or use of the contents of this information is 
prohibited. If you have received this electronic message in error, 
please notify us by telephone on 0131 476 6000 and delete the 
material from your computer. 
> Registered in Scotland number: SC 172507. 
> Registered office address: Quay House 142 Commercial Street 
Edinburgh EH6 6LB. 
> 
> This email message has been scanned for viruses by Mimecast.
> -------------------------------------------------------------------
------------------------
>


Reply via email to