Unable to resolve resource bundle “*” for locale “en_US” (Flex, Flash Builder)

Question

since I'm using custom skin classes in Flex I'm getting an error, when trying to open the design view in Flash Builder:

Description Resource Path Location Type

Unable to resolve resource bundle "components" for locale "en_US". 
Unable to resolve resource bundle "core" for locale "en_US". 
Unable to resolve resource bundle "effects" for locale "en_US". 
Unable to resolve resource bundle "layout" for locale "en_US". 
Unable to resolve resource bundle "skins" for locale "en_US". 
Unable to resolve resource bundle "styles" for locale "en_US". 

I tried a lot with setting locales in compiler arguments - but I thinks this error is directly related to a locale problem. When I check the flex framework directories "C:\Program Files\Adobe\Adobe Flash Builder 4\sdks\4.0.0\frameworks\projects\spark\src\spark" - here are the original skin classes located - I can see all the "missing" folders.

Anybody has a clue about that issue?

Answer 1

I could solve my problem by adding following Library Path to the Project settings / Flex Build Path:

C:\Program Files\Adobe\Adobe Flash Builder 4\sdks\4.0.0\frameworks\locale\en_US

It seems that the Flex compiler knows the path when working with the standard skins but somehow it can't find it when dealing with custom skins.

Answer 2

If any issue like this type, means it can not found your file path

Go to Project --> Property-->Flex Build Path-->Source path-->Add Folder --> locale\en_US

which file error show on Description

here is additional source folder can be add outside of the main source folder

Answer 3

In addition to what the previous answers here already address, there is another possible cause.

This error appears also when a required locale is missing from the SDK itself. The list of existing SDK locales can be found at SDK.INSTALL.DIR/sdks/VERSION.NO/frameworks/locale. If a required locale is not there, then you need to create it with the copylocale command.

For more information, see Creating a new locale for i18N capable application.