We are having a wierd problem driving us nuts when attempting a release build(ad-hoc) or "Standard" debug build for IOS that uses an ANE.
during the release build, we get the message "Some classes used in the application could not be resolved for packaging. See the error log for more details." The ANE works just fine if we do a "Fast" debug build.
The detail of the error log shows:
Error occurred while packaging the application: Exception in thread "main" java.lang.Error: Unable to find named traits: com.edt.nativeane.alert::NativeAlert at adobe.abc.Domain.resolveTypeName(Domain.java:231)
Research we did points to the complier not finding the ANE or not having the extensionID set in he app xml.
1. The extensionID is present in the app-xml, in fact is set automaticatlly by flash builder when we include the ANE in the build path.
2. The ANE works just fine if we do a "Fast" debug build.
3. The ANE is set in the Flex Build Path in FB and has the green check.
Here is where I think the problem is:
4. In Flex Build Packaging for IOS, the ANE is set with a green checkmark, however when we click the "Package" checkbox, we get the message: "This ANE is not used in the application. Are you sure you want to include it in the package." Also the "Used" indicator shows an "X".
This seems to indicate that FB isnt including the ANE in the release or standard-debug build and explains the java error in the errror log shown above. Of course the classes in the Native extension are indeed referenced in the default mxml file and the app and ANE work fine with a "Fast" debug build.
This isnt making a lot of sense. Could anyone shed some light on what might be causing this?
Europe, Middle East and Africa