Often when refactoring code I'll extract ActionScript code out of an MXML file into an ActionScript based superclass to get a cleaner separation between logic and the view. In doing so I sometimes forget to update MXML variable declrations, leading to the confusing error: Could not resolve <mx:states> to a component implementation. In this case my MXML class extends another custom class and looks