The error that "No class registered for interface ‘mx.styles::IStyleManager2′"

User-48x48 When I compiled “flex3_sdk ->samples ->explorer ->containers ->SimpleTitleWindowExample.mxml” with mxmlc and run it,i got the error below:

Error: No class registered for interface ‘mx.styles::IStyleManager2′.
   at mx.core::Singleton$/getInstance()
   at mx.styles::StyleManager$/get impl()
   at mx.styles::StyleManager$/
   at simpleTitleWindowExample/  at SimpleTitleWindowExample()

Maybe it’s too simple for you,but i spend too much time fixing this error. I found there was a comment like below:

<?xml version="1.0" encoding="utf-8"?>
<!-- Simple custom MXML TitleWindow component.
     The TitleWindowApp application displays this component. 
     You cannot run it independently. -->

Yes,it denpends on another mxml and can not be directly run.:)

Share and Enjoy:
  • Digg
  • Facebook
  • Google Bookmarks
  • DZone
  • Reddit
  • Technorati
  • StumbleUpon
  • Twitter
RSS Enjoy this Post? Subscribe to

RSS Feed   RSS Feed     Email Feed  Email Feed Follow us Follow us
You can leave a response, or trackback from your own site.

6 Responses to “The error that "No class registered for interface ‘mx.styles::IStyleManager2′"”

  1. Sam Dean says:


    I ran into this same problem whilst compiling an actionscript project. I fixed it by adding the line :

    Singleton.registerClass(“mx.styles::IStyleManager2″, Class(ApplicationDomain.currentDomain.getDefinition(“mx.styles::StyleManagerImpl”)));

    as the first line in my constructor.

    Hope this is useful,


  2. [...] reading this, I found out I was unintentionally running/debugging a flex component instead of a flex [...]

  3. Quantium says:

    Hi all,

    Thanks Sam, I’ve already done the Singleton.registerClass thing. But now I have a new issue, When i compile I see ‘value is not a function’ when Singleton calls c['getInstance']() function.

    That function is there in IBrowserManager but still don’t reconigsed.

  4. whois says:


    Same issue on my part.=( can’t figure out.

  5. Daerd says:

    I have this very same problem. From doing a bit of Googling, I’ve come to understand that the problem seems to be that one shouldn’t compile/run an AS3 application from a component (a subclass of mx.controls.* or, in my case, from a MovieClip), lest you will have this error. Compile/run from your Application class instead.

    Not sure if this will really solve the problem (since I’m a n00b at AS3 and I haven’t got to testing it yet) but it seems quite logical to me! :)

Leave a Reply to Quantium