Skip to main content
M
michelangelo.capraro
Inspiring
May 22, 2013
Question

Type Coercion failures with MovieClips in ASC 2.0

  • May 22, 2013
  • 11 replies
  • 12254 views

Hi all, i am seeing this Type Coercion problem with SWCs containing MovieClip assets in 3.7 and 3.8 versions of ASC 2.0

here is the bug i filed: https://bugbase.adobe.com/index.cfm?event=bug&id=3562040

Adobe: would love to see a fix in the next beta update if possible so i dont have to go back to the flex compiler. I posted this accidentally in the Flex group, so sorry about hte cross post, want to be sure adobe sees it, my bug, and can issue a fix.

Basically, when i compile using ASC 2.0 and am calling assets from a SWC generated in Flash CS6, i get an intermittent type coercion error. What seems to trigger this is adding a child of a MovieClip in the SWC to the stage of a Sprite not in the SWC (generated programatically).

Exception fault: TypeError: Error #1034: Type Coercion failed: cannot convert flash.display::MovieClip@d7dd431 to assets.ui.GoButtonAsset.

          at flash.display::Sprite/constructChildren()

          at flash.display::Sprite()

          at flash.display::MovieClip()

    This topic has been closed for replies.

    11 replies

    Show previous replies
    M
    michelangelo.capraroAuthor
    Inspiring
    May 29, 2013

    Is anyone else seeing this? it's really killing a few of my projects right now

    chris.campbell
    Community Manager
    chris.campbellCommunity Manager
    Community Manager
    May 29, 2013

    I can have someone take a look.  Could you do me a favor and add a sample project to the bug report or email it to ccampbel@adobe.com if you'd like to keep it private?

    Z
    Zobo__
    Participant
    June 11, 2013

    "Me too".

    We also switched to ASC 2.0 and are experiencing this at random intervals. We have older SWC files (SWF version 11) and when an instance of the movieclip extended class is created, the error is thrown.

    What's even more strange is, that this seems to be decided at build time. Whenever I build the code on my dev PC, I never got this sort of error so far. When we build the code on the build server (linux, java 1.6.0_24) the resulting binaries sometines thrw the error, sometimes not. When the error is presenting it self, it is ther always, 100% repeatable. If the error is not there, it is never there.

    We experience this on AIR platform Windows 3.7 and on Flash platform (FP 11.7).

    Looking at the SWF, it seems they arn't that much different.

    Any progess here?

    Best,

    Damjan

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices