Select to view content in your preferred language

Flex Mobile using 3.4 or 3.5 compile problems

991
7
10-01-2013 10:49 AM
KathleenBrenkert
Regular Contributor
I can not get a release build using either the 3.4 or 3.5 api on a flex mobile project.  I switch the library back to 3.3 and it's working again.  Using 3.4/3.5 I can debug, launch the project on the device with a fast packaging (I have not tried standard) - problem only occurs when I go to compile my release build.

My log file for 3.4/3.5:
!ENTRY com.adobe.flexbuilder.project 4 43 2013-10-01 09:40:08.431
!MESSAGE Error occurred while packaging the application:

Exception in thread "main" java.lang.Error: Unable to find named traits: mx.controls::RichTextEditor
at adobe.abc.Domain.resolveTypeName(Domain.java:232)
at adobe.abc.Domain.resolveTypeName(Domain.java:149)
at adobe.abc.GlobalOptimizer$InputAbc.resolveTypeName(GlobalOptimizer.java:273)
at adobe.abc.GlobalOptimizer$InputAbc.resolveSlotType(GlobalOptimizer.java:956)
at adobe.abc.GlobalOptimizer$InputAbc.resolveType(GlobalOptimizer.java:536)
at adobe.abc.GlobalOptimizer$InputAbc.resolveTypes(GlobalOptimizer.java:449)
at adobe.abc.LLVMEmitter.generateBitcode(LLVMEmitter.java:334)
at com.adobe.air.ipa.AOTCompiler.convertAbcToLlvmBitcodeImpl(AOTCompiler.java:611)
at com.adobe.air.ipa.BitcodeGenerator.main(BitcodeGenerator.java:104)
Compilation failed while executing : ADT

It continues from there...
I don't know what else to do but to stick with 3.3 for all my mobile projects.  I'm using flash builder 4.7, apache flex 4.10.0 11.8 Air 3.8.
Tags (2)
0 Kudos
7 Replies
MikeDahm
Frequent Contributor
Did you add both mx.swc and sparkskins.swc to the library?  The  AttributeInspector and RelationShipInspector where also redone in 3.4 from 3.3.
0 Kudos
KathleenBrenkert
Regular Contributor
I did try adding mx.swc and sparkskins.swc but it did not solve the issue.  I added skins to solve the warnings we get bc of the attributeInspector/relationshipInspector and the warnings clear but still can't build a final release.  I am using multiple libraries and I created a test project where I tested each library individually.  I only run into issues when I pull in 3.4 or 3.5.  I have only worked on mobile projects since I upgraded, so I do not know if I have the same problem with a desktop project.

3.3 is working great, there is no need to use skins and it has all the functionality I need to create my project.  So for now it's my work around.
0 Kudos
IsaiahAguilera
Frequent Contributor
Please review following thread.  This issue should help you.

http://forums.arcgis.com/threads/89517-Runtime-error-with-new-3.4-API

Hope This Helps,
0 Kudos
KathleenBrenkert
Regular Contributor
Thanks, I'm actually the last commenter on that thread.  I can get the warnings to clear, which then allows me test the application.  Even with this fix I can not get a release build.
0 Kudos
IsaiahAguilera
Frequent Contributor
After that thread I still had release build problems also. I was able to solve it by making an additional change to the AttributeInspectorSkin. I had to change the memoField to use a text field. This solved my problem, not sure it will solve yours but your welcome to try.

<fx:Component id="memoField">
            <fieldClasses:MemoField minWidth="200"/>
</fx:Component>


Change To:
 <fx:Component id="memoField">
            <fieldClasses:TextField minWidth="200"/>
</fx:Component>


Also I am on 3.4 and I am no referencing the mx.swc or sparksskins.swc at all. Everything compiles and release builds fine.

Hope This Helps,
0 Kudos
KathleenBrenkert
Regular Contributor
Thanks! I'll give this a try next time I upgrade the api.  I think for now I'm sticking with 3.3, unless I hit a limitation with the functionality it saves me from having to apply the fix.
0 Kudos
LloydHeberlie
Regular Contributor
You might try this sample: https://github.com/lheberlie/building-mobile-apps-flex/tree/develop/samples/hello-infowindow.  I compiled this just the other day using version 3.5.
0 Kudos