Problem with flash player 10.3 & Flash Catalyst Compatible Project

[rjp421]

I have just installed flash player 10.3 debug ax and plugin, and replaced the original builder and catalyst  player files with 10.3 in both:

C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.5\player\win\10.3

C:\Program Files (x86)\Adobe\Adobe Flash Catalyst CS5.5\player\win\

Everything works so far if i keep min flash player version at 10.2 in the project properties.

I then copied the flashplayer_inc_playerglobal_051211.swc to both:

C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.5\sdks\4.5.0\frameworks\libs\player\10.3\playerglobal.swc

C:\Program Files (x86)\Adobe\Adobe Flash Catalyst CS5.5\sdks\4.5.0\frameworks\libs\player\10.3\playerglobal.swc

If I change the project properties to a minimum player version of 10.3, and add -swf-version=12 to the compiler args,

I get a Flash Catalyst Incompatibility error:

Configuration problem: The library path must include the following entry: ${PROJECT_FRAMEWORKS}/libs/player/10.2/playerglobal.swc

MyApplication       Unknown    Flash Catalyst Project Incompatibility

Any input is greatly appreciated.

Thanks!

Message was edited by: rjp421

[rjp421]

Am I the only one with this problem?

How am I supposed to correctly target 10.3 in a flash catalyst compatible project?

Thanks.

[rjp421]

A simple yes or no would be helpful, so I can stop this wild goose chase.

Thanks.

[rjp421]

I just noticed the 10.3 release playerglobal swc was released finally.

http://download.macromedia.com/pub/labs/flashplatformruntimes/flashplayer10-3/flashplayer10-3_playerglobal_052011.swc

[rjp421]

The problem seems to be with setting the minimum flash player version in the project properties.

10 2 0 works.

10 3 0 does not work, and gives the catalyst incompatibility warning.

What's the deal?

Message was edited by: rjp421

[Sunil_Bannur · Accepted solution]

This seems to be a bug, I have filed http://bugs.adobe.com/jira/browse/TH-13654 for you to track.

If you are not able to open the project in FC, then I would recommend you to fallback to 10.2 and when packaging agian change it to 10.3 as a workaround for now.

[rjp421]

This problem still exists in FB 4.5.1.

That bug tracker link does not work, it says permission violation.

I did delete my .metadata, .fxpTemp, and cascaded folders in my workspace before launching FB.

Any updated info is appreciated, thanks.

Message was edited by: rjp421

[rjp421]

The bug link does not work, is there any update to this problem?

Is there any config file or anything that i can change, to allow it to look for the /10.3/ folder,

instead of /10.2/ like in the compatibility error?

Thanks

[rjp421]

Is there a new link for this bug??

Thanks.