Errors during packaging AIR mobile application.

Report · Apr 20, 2013

I have two problems with AIR 3.7.

First problem is the same as described in topic http://forums.adobe.com/message/5211842

If I compile with flah -debug=true it is ok. But with -debug=false I can't package my .apk/ipa file because of error:

"error 304: Initial window content is invalid"

I tried with newest AIR SDK beta (downloaded from http://labs.adobe.com/downloads/air.html) dated as "Apr 16 2013" (build number 1680) but the same result.

Second problem is when I try to use .swf file compiled with -debug=true flag. Here is output:

'/opt/adobe_sdks/AIR_3.7/bin/adt' -package -target ipa-ad-hoc -provisioning-profile 'Profil_Radek_B.mobileprovision' -storetype pkcs12 -keystore 'Iphone Developer Radoslaw Bulat.p12' -storepass XXXX test.ipa test-app.xml icons/icon114.png icons/icon128.png icons/icon16.png icons/icon32.png icons/icon36.png icons/icon48.png icons/icon512.png icons/icon57.png icons/icon72.png test.swf

Exception in thread "main" java.lang.Error: Unable to find named traits: org.papervision3d.core.geom::Pixels

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:332)

at com.adobe.air.ipa.AOTCompiler.convertAbcToLlvmBitcodeImpl(AOTCompiler.java:611)

at com.adobe.air.ipa.BitcodeGenerator.main(BitcodeGenerator.java:104)

If I try to package .apk file everything is ok.

Here are additional commands I use:

$ /opt/adobe_sdks/AIR_3.7/bin/mxmlc -version

Version 2.0.0 build 353448

$ /opt/adobe_sdks/AIR_3.7/bin/amxmlc -compiler.source-path project-air/src/ flash/src/ flash/lib/GreenSock/ flash/lib/HiResStats/lib/ flash/lib/as3corelib/ flash/lib/asunit/ flash/lib/mochi/src/ flash/lib/starling/src/ flash/lib/starling-imagebatch/src/ flash/lib/feathersui/src/ -swf-version=20 -static-link-runtime-shared-libraries=true -locale en_US -define=CONFIG::DEBUG,false -frame start "App" -define=CONFIG::CLASSIC,true -compiler.include-libraries flash/lib/assets.swc flash/lib/flash.swc flash/lib/analytics.swc flash/lib/as3crypto.swc flash/lib/CJSignals\ 1.0.32.swc flash/lib/Stardust\ 1.3.186.swc flash/lib/PNGEncoder2.swc -managers flash.fonts.AFEFontManager -debug=true -o test.swf project-air/src/AirMain.as

Report · Apr 20, 2013

Ok, I could find a way around 2nd problem. I replaced some swc file library with it's source and adt didn't complain during packaging but I still had to use -debug=true flag.

Report · Apr 21, 2013

Thank you radarak for your bug report. We will investigate it and update you soon.

-Nimit

Report · Apr 21, 2013

Hi,

The first problem you reported could not be reproduced with the build # 3.7.0.1680. Could you please verify the problem with the project attached at https://bugbase.adobe.com/index.cfm?event=bug&id=3532285, kindly share the results.

Regards,

Nimit

Report · Apr 22, 2013

I checked attached project from https://bugbase.adobe.com/index.cfm?event=bug&id=3532285 and my results are as follows:

If I compile it as it was stated in compile_and_package.bat file ($AIR_HOME/bin/amxmlc +configname=airmobile -swf-version=$SWF_VERSION -debug=false -output out/Main_non_debug.swf src/Main.as) it works ok

But if I change "+configname=airmobile" to "+configname=air" (which I believe is default) it will produce bad .swf file (which I cannot package with adt).

I've tried it with my project and results are the same: with +configname=airmobile it works ok but with +configname=air it produce bad .swf.

Could you please verify if it behaves the same for you?

Report · Apr 22, 2013

Thank you radarek for the information. Is there any particular use case where you are using air instead of airmobile?

-Nimit

Report · Apr 26, 2013

To be honest I don't know what is the difference between air and airmobile. I used default config and didn't care about until I spotted this problem.

So should I use airmobile config? What abou building air desktop app? Can I use airmobile config to do that?