Is it possible to build a captive runtime package with native extension?

Hi. Now I try to build a captive runtime package with one native extension file(ANE) for Windows.
I use Flash Builder 4.6 Premium and try to export release build.
But Flash Builder warns that captive runtime can not bundle ane file.
So I can not build package.
Official document seems that captive runtime  supports native extensions.
Does anyone know about?

Hi. Now I try to build a captive runtime package with one native extension file(ANE) for Windows.
I use Flash Builder 4.6 Premium and try to export release build.
But Flash Builder warns that captive runtime can not bundle ane file.
So I can not build package.
Official document seems that captive runtime  supports native extensions.
Does anyone know about?

Similar Messages

  • ADT packaging with native extensions : permission denied error when running remote build.

    Hi Team,
    We are facing the following error when running the nightly ant build script on Mac machine for our air mobile application. We are using iOS native extensions and package with ADT. This works fine when we run the build as local user in the Mac machine. Earlier we faced some issues due to headless build and we have added the <headless-server>true</headless-server> in corresponding config files (flex-config.xml, airmobile-config.xml). After that we are facing the following error, even when we run the ant build in headless mode using the following command.
    ant -Djava.awt.headless=true -f build.xml buildPackage
    When running this build as local user in the Mac build machine, we see a window opening with com.adobe.air.ADT while packaging. This is the issue when running nightly build as there is no graphics window.
    Can anybody please help how to get rid of this issue for nightly build using adt,jar?
    Here is the error from build log:
    buildiOSPackageWithNativeExtensionMac:
         [echo] Export the iOS package with Native extension for ApprovalsMobile in Mac
         [java] Exception in thread "main" java.lang.InternalError: Can't connect to window server - not enough permissions.
         [java]  at java.lang.ClassLoader$NativeLibrary.load(Native Method)
         [java]  at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1827)
         [java]  at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1724)
         [java]  at java.lang.Runtime.loadLibrary0(Runtime.java:823)
         [java]  at java.lang.System.loadLibrary(System.java:1045)
         [java]  at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50)
         [java]  at java.security.AccessController.doPrivileged(Native Method)
         [java]  at java.awt.Toolkit.loadLibraries(Toolkit.java:1605)
         [java]  at java.awt.Toolkit.<clinit>(Toolkit.java:1627)
         [java]  at java.awt.Dimension.<clinit>(Dimension.java:70)
         [java]  at com.adobe.air.validator.ApplicationDescriptorValidator.validateImageUri(ApplicationDescri ptorValidator.java:183)
         [java]  at com.adobe.air.validator.ApplicationDescriptorValidator20.validateElement(ApplicationDescr iptorValidator20.java:121)
         [java]  at com.adobe.air.validator.ApplicationDescriptorValidator25.validateElement(ApplicationDescr iptorValidator25.java:65)
         [java]  at com.adobe.air.validator.ApplicationDescriptorValidator26.validateElement(ApplicationDescr iptorValidator26.java:62)
         [java]  at com.adobe.air.validator.ApplicationDescriptorValidator30.validateElement(ApplicationDescr iptorValidator30.java:52)
         [java]  at com.adobe.air.validator.ApplicationDescriptorValidator31.validateElement(ApplicationDescr iptorValidator31.java:46)
         [java]  at com.adobe.air.validator.DescriptorValidator.endElement(DescriptorValidator.java:239)
         [java]  at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser .java:601)
         [java]  at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XML DocumentFragmentScannerImpl.java:1782)
         [java]  at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDri ver.next(XMLDocumentFragmentScannerImpl.java:2939)
         [java]  at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImp l.java:648)
         [java]  at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScanne rImpl.java:140)
         [java]  at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDo cumentFragmentScannerImpl.java:511)
         [java]  at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.ja va:808)
         [java]  at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.ja va:737)
         [java]  at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
         [java]  at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java :1205)
         [java]  at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.j ava:522)
         [java]  at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
         [java]  at javax.xml.parsers.SAXParser.parse(SAXParser.java:198)
         [java]  at com.adobe.air.Descriptor.validateXML(Descriptor.java:182)
         [java]  at com.adobe.air.Descriptor.<init>(Descriptor.java:56)
         [java]  at com.adobe.air.ApplicationDescriptor.<init>(ApplicationDescriptor.java:84)
         [java]  at com.adobe.air.ApplicationPackager.validateApplicationDescriptor(ApplicationPackager.java: 101)
         [java]  at com.adobe.air.ApplicationPackager.createPackage(ApplicationPackager.java:64)
         [java]  at com.adobe.air.ipa.IPAPackager.createPackage(IPAPackager.java:217)
         [java]  at com.adobe.air.ADT.parseArgsAndGo(ADT.java:557)
         [java]  at com.adobe.air.ADT.run(ADT.java:414)
         [java]  at com.adobe.air.ADT.main(ADT.java:464)
    Thanks,
    Swathi.

    Note: Before the above error that were two other errors .
    1) The build complained that the adt-bundle-linux toolchain could not be found and required that it be added to .mozconfig. This was done.
    2) The build complained that dx could not be found.
    The configure file was edited and the values $DX, $AAPT and $AIDL were all set to the adt-bundle-linux/sdk/build-tools/android-4.4 path.
    The instructions given on the Mozilla Wiki did not work right for Android and several modifications were made to move it along. But this permission error is tough to figure out.

  • Is possible to sign a Captive runtime bundle executable in mac with a mac distribution using codesign (to avoid security Alert)

    Hi, again:
    Is possible to sign a Captive runtime executable (.app) in mac with a mac distribution certificate using codesign (to avoid security Alert)?
    Considering that Flash Builder does not allow you to create an unsigned .app (captive).
    Basically, apparently is imposible to do it, when I try codesign always return a: part of the bundle is sealed.
    Please anyone there can help me to solve this?
    Thank you.

    Hi, again:
    Is possible to sign a Captive runtime executable (.app) in mac with a mac distribution certificate using codesign (to avoid security Alert)?
    Considering that Flash Builder does not allow you to create an unsigned .app (captive).
    Basically, apparently is imposible to do it, when I try codesign always return a: part of the bundle is sealed.
    Please anyone there can help me to solve this?
    Thank you.

  • Export Captive Runtime Bundle with ANE

    I'm trying to export a release build of my app which makes use of AIR native extensions. Due to certain requirements, the app needs to be exported as a captive runtime bundle package.
    Flash Builder 4.6 refuses to do such an export and displays this message"Native extensions are being used in the project but are not supported by the CAPTIVE_RUNTIME_BUNDLE package type. Runtime issues can occur."
    Does anyone know exactly what these runtime issues are?

    Solved thanks to myself.  export to a different drive. in my case- Desktop. 
    turns out i can't copy to the terrablock volume i'm working off of.  I figured this out after trying to do this solely in Flash Pro.  I received a crazy error message.  I googled that and i found a post that i commented on a 6 months ago.  To see me talking to my future self look here - http://forums.adobe.com/message/5475543
    hope this helps someone.

  • Bus Error: 10 while packaging a Flash Builder 4.6 application containing a native extension (ANE)

    I get this error:
    ld: warning: -ios_version_min not specificed, assuming 4.0
    ld: warning: -dead_strip with lazy loaded static (library) archives has resulted in a duplicate symbol.  You can change your source code to rename symbols to avoid the collision.  This will be an error in a future linker.
    /var/folders/y4/svqv7kzn469_ljcrvw1b99500000gn/T/cmd8085539752601990184.tmp: line 2: 25159 Bus error: 10           "/Applications/Adobe Flash Builder 4.6/sdks/4.6.0/lib/aot/bin/ld64/i686-apple-darwin10-ld64" -ObjC -dead_strip -Z -arch armv7 -syslibroot "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iP honeOS6.0.sdk" -L/usr/lib -F"/System/Library/Frameworks/" -L"/Applications/Adobe Flash Builder 4.6/sdks/4.6.0/lib/aot/lib" -o "../aot8213014594451590298.tmp" -L"/var/folders/y4/svqv7kzn469_ljcrvw1b99500000gn/T/07f32573-0d2b-42c6-b431-916954d76791" -exported_symbol _main -exported_symbol _ExtInitializer -exported_symbol _ExtFinalizer "extensionglue.o" -lstdc++ -lRuntimeInterpreter.arm-air -lgcc_s.1 -lstdc++.6 -lcrt1.o -lSystem.B -lz -lobjc -framework CoreFoundation -framework UIKit -framework MobileCoreServices -framework CoreGraphics -framework Foundation -framework SystemConfiguration -framework AudioToolbox -framework CFNetwork -framework QuartzCore -framework OpenGLES -framework CoreLocation -framework CoreMedia -framework CoreVideo -framework AVFoundation -framework Security -lcom.pgi.native.extensions.softphone
    Compilation failed while executing : ld64
    The ane was created using this command:
    "/Applications/Adobe Flash Builder 4.6/sdks/4.6.0/bin/adt" -package -target ane SPExtension.ane extension.xml -swc SPTest.swc -platform iPhone-ARM -C ios . -platformoptions platform.xml
    The ANE file seemed to load in my project ok, and build ok.  But when I hit run to package for my ios device, I get the above error.

    Here's the fix in case anyone else runs into this problem.  When Flash Builder is building the deployment during launch, it converts the mapped path to a mangled local path for the ane to find the descriptor to a relative path, which can't be found and throws the null pointer.  Making the Output Folder path actually local to the computer, as opposed to the default that FB creates, resolves the error, and still allows blazeds access from the device.

  • Sidecar AIR Runtime install with  Native .exe installer using ADT

    I have packaged my AIR app into a Native .exe installer using ADT. If the user does not have air installed and they are connected to the internet, the AIR runtime is automatically installed.
    Is it possible to package the AIR runtime into the exe so that if the user is not online the AIR runtime is installed?
    I have experimented with the sidecar install and .air file but ideally I want to only have the one file(.exe). I already have a distribution licence from Adobe.

    manicjames wrote:
    I have packaged my AIR app into a Native .exe installer using ADT. If the user does not have air installed and they are connected to the internet, the AIR runtime is automatically installed.
    Is it possible to package the AIR runtime into the exe so that if the user is not online the AIR runtime is installed?
    I have experimented with the sidecar install and .air file but ideally I want to only have the one file(.exe). I already have a distribution licence from Adobe.
    This isn't available at this time, but I think it's a great idea.  You might want to add a feature request for this over at ideas.adobe.com and bugbase.adobe.com, or review and vote for these current feature requests if they provide for what you're looking for:
    Portable AIR Apps
    Create portable AIR apps
    If you decide to add a new request, please post back with the URL so others can cast their votes and add comments.
    Chris

  • ANT build produces not working package with 3.5 AIR SDK

    I used AIR SDK 3.1 and have ANT script to compile and package iPad(AdHoc for testing) application. I tried to switch to 3.5 SDK today but when I install *.ipa and launch on iPad it hangs at the spalsh screen.
    I tried to make release build using Flash Builder UI and it worked. So the question is has anything changed in terms of packaging/compilation options?
    Just in case attached my current ANT script:
    <target name="Compilation" depends="Initialization">
         <mxmlc file="${main_class}" output="${swf_file}" locale="${LOCALE}"  static-rsls="false" accessible="false" configname="airmobile"
                    optimize="true" actionscript-file-encoding="UTF-8" keep-generated-actionscript="false" static-link-runtime-shared-libraries="true"
                   debug="${debug_mode}"  failonerror="true" fork="true"  maxmemory="1024m">
              <source-path path-element="${class_path}"/>
              <load-config filename="${FLEX_HOME}/frameworks/airmobile-config.xml"/>
              <load-config filename="${config_file}"></load-config>
              <library-path dir="${lib_path}" includes="*.swc" append="true"/>
         </mxmlc>
    </target>
    <target name="Packaging" depends="Compilation">
          <java jar="${ADT}" fork="true" failonerror="true">
              <arg value="-package"/>
              <arg value="-target"/>
              <arg value="ipa-test"/>
              <arg value="-provisioning-profile"/>
              <arg value="${ios_provisioning}"/>
              <arg value="-storetype"/>
              <arg value="pkcs12"/>
              <arg value="-keystore"/>
              <arg value="${ios_keystore}"/>
              <arg value="-storepass"/>
              <arg value="${ios_pass}"/>
              <arg value="${ipa_file}"/>
              <arg value="${app_descriptor}"/>
              <arg value="${swf_file}"/>
              <arg value="-C" />
              <arg value="${class_path}"/>
              <arg value="assets/icons"/>
              <arg value="-C" />
              <arg value="${release_path}"/>
              <arg value="Default-Portrait.png"/>
         </java>
    </target>
    Thanks

    You may want to try using the settings used by Flash Builder to package the application, more details of which can be found at:http://helpx.adobe.com/x-productkb/multi/compilation-results-flex-builder-flex.html
    Update your ANT script with these, and try again.
    Please get back and tell if it resolved the issue and what change you had to made in your ANT script.
    Thanks,
    Neha

  • How to use ADT command line to build an iOS application including ActionScript native extension file

    Hi All,
    I have ANE files packaged in my iOS application. I can export them to release build through FB no problem.
    But How can I include those ANE files through ADT command line? Can I do like other library files?
    Thanks in advance for any helps.

    I was stupid that did not find the right syntax.
    -extdir extensionsDir will do the trick.

  • AIR3[Mobile] – Is it possible to add native Android visual elements with native extensions?

    Hi, i need to add some native android elements to stage. Is it real?
    Thanks in advance.

    Yes.
    Check this http://lancelotmobile.com/blog/admob-ane. The code is available in github.
    Best regards,
    Emil
    Lancelotmobile Ltd.

  • Building the ActionScript library of a native extension

    This question was posted in response to the following article: http://help.adobe.com/en_US/air/extensions/WS99209310cacd98cc2d13931c1300f2c84c7-8000.html

    Is it:  "-swf-version 17" or "-swf-version=17" ? Both are listed...

  • AIR for Android Captive Runtime

    Is it possible to package android apps with AIR (or will it be) using Flash CS5.5? I don't see anything on the web about. Just how to do it with Flex and ADT etc...

    Hi,
    I've made a complete working example for publishing an application with captive runtime, assets and native extensions starting from Flash CS5.5
    I was able to make it thanks to hints and suggestions I found in this thread.
    Note: english is not my native tongue so I hope you understand what I've written also if sometime it sounds "engrish".
    Here it is the link to the zip file:
        http://www.genereavventura.com/hosted/Air3NativeExtensions/AirVibrate.zip
    Requirements:
    - You must have Flash cs5.5 pro (obviously)
    - You must have installed the overlay for Air3.0 sdk on your Flash cs5.5 pro
    Here it is a link that explain how to accomplish it: http://forums.adobe.com/message/3939712
    Here the steps I made.
    1) Open Flash CS5.5 and create a new AIR for Android application
    2) Add the swc to the libraries used by your FLA (open Actionscript 3.0 settings and add "VibrationActionScriptLibrary.swc")
       Btw, you can find this "ready to use" native extension inside the zipfile that you can download from here: http://www.adobe.com/devnet/air/native-extensions-for-air/extensions/vibration.html
       However in my example you will find also a directory named "extension" that contains it.
    3) Open and then close the "air for android settings": by doing this Flash will create yourapp-app.xml file in the directory where your FLA resides.
       For example my fla is named "vibrate.fla" so Flash created for me a "vibrate-app.xml" file.
    4) Make a copy of this "vibrate-app.xml" file by naming it "real-vibrate-app.xml" (or choose whatever name you want)
       I've done this because after modyfing the original one by adding the <extension> tag (see below) I wasn't able to test my app from within Flash IDE (when I compile it it simply doesn't start)
       Instead by doing this all worked fine.
    5) Edit the "real-vibrate-app.xml" file by adding somewhere these lines (I added it just before the <initialWindow> tag)
        <extensions>
          <extensionID>com.adobe.Vibration</extensionID>
        </extensions>
    6) Add <uses-permission android:name="android.permission.VIBRATE"/> in the <android> <manifestAdditions> part in "real-vibrate-app.xml" file.
       You should do something like this:
       <android>
          <manifestAdditions>
            <![CDATA[<manifest>
              <uses-permission android:name="android.permission.VIBRATE"/>
            </manifest>]]>
          </manifestAdditions>
       </android>
    7) Develop your application
       I made a simple one that loads an external jpg and shows it on the stage: then the user can tap on it to make the phone vibrate.
       The function "doVibration" is called only when the app is running on Android Device so I do not get any executions error when I run the app from within Flash Ide
    8) Publish and test it to your USB connected device by launching the "publish.bat" file I have created
       Open a dos prompt and move to your project directory then type publish.bat and press enter.
       Note: it can be that you have to edit the bat file in order to change the path to the ADT tool that comes with Air3.0 sdk
       It should be in [your adobe flash cs5.5 directory]\AIR2.6\bin\adt (rememeber, you must have installed the Air3.0 sdk overlying the old Air2.6/2.7 in the AIR2.6 directory)
       Inside the bat file you can change easily the target type (captive or not) simply by commenting/decommenting the right line.
       Captive version is about 8Mb more than the normal one but the big deal is that the user that installs it do not need the air runtime installed on his phone!
       The "big line" that creates the package is the following one:
       call %ADT_LINK% -package -target %TARGET_TYPE% -storetype pkcs12 -keystore certificate/vibrate.p12 -storepass android AirVibrate.apk real-vibrate-app.xml -extdir extensions vibrate.swf icons assets
       where:
       call %ADT_LINK%          it's just the path to the ADT tool
       -package                 it's the command that we want ADT to execute
       -target %TARGET_TYPE%    captive/non captive version
       -storetype pkcs12        certificate related
       -keystore certificate/vibrate.p12  path to your self signed certificate
       -storepass android       certificate related, I created the example certificate with "android" password and this parameters tell ADT to always use it without prompting
       AirVibrate.apk           the name of the Apk
       real-vibrate-app.xml     the apk-xml to use that is the one we modified manually above
       -extdir extensions       it's the path to the directory that contains the native extension
       vibrate.swf              the main swf
       icons                    the icons directory
       assets                   the assets directory (where I put the external jpg)
    That's all.
    If everything is correct, the batch file creates the AirVibrate.apk then installs it on your attached usb device and run it.
    When you tap over the Android image that will appear, your phone should vibrate.
    Now.. does someone wants to develop a Native Extension to show Admob banners in our Android Air Applications?
    If I missed something, please let me know.
    Thanks

  • How to use single ant build script to package the application with and without native extensions

    Hi,
    I am using iOS native extensions for Adobe air. For this I am listing the extensions in the application descriptor file. Since the package with native extensions are meant to run only on device, I want my build script to work without native extensions too to be able to run on simulator. Is this manadatory that I need two separate application descriptors/basically two build scripts to compile and package them? Please suggest and let me know if more explanation is needed.
    Thanks,
    Swathi.

    Hi
    This is a known issue addressed by CR205204
    As you said, IBM actually does not have rt.jar in its JDK - they have moved contents of rt.jar into various jars.
    IBM is not using org/apache/crimson/tree/ in their JDK at all.So the error shows up in the end of build even if it succeeds
    You may need to add crimson.jar to wlwBuild classpath, since it is not part of IBMs JDK.
    Note: the build will work even w/o crimson.jar giving a non build related IDE exception in the very end.
    Thanks
    Vimala

  • How to use single ant build to package with and without native extensions

    Hi,
    I am using iOS native extensions for Adobe air. For this I am listing the extensionid in the application descriptor file. Since the package with native extensions are meant to run only on device, I want my build script to work without native extensions too to be able to run on simulator. Is this manadatory that I need two separate application descriptors/basically two build scripts to compile and package them? Please suggest and let me know if more explanation is needed.
    Thanks,
    Swathi.

    why are you wanting to use single frames?
    They allow having the initial frame address stay in the
    address bar, and not
    show the linked page's address. The problems they cause
    usually override any
    value.
    Or- if we aren't using the same words the same way, please
    give an example
    site of what you want to do.
    Alan
    Adobe Community Expert, dreamweaver
    http://www.adobe.com/communities/experts/

  • Native extensions and captive runtime

    I'm trying to use native extensions and captive runtime. When I try to create a release, the IDE shows this message "Native extensions are being used in the project but are not supported by the CAPTIVE_RUNTIME_BUNDLE package type. Runtime issues can occur." and I can't continue.
    I've been able to compile it using the command-line, but I'm worried about the "runtime issues" that can occur.

    Hi,
    Sorry, just verified that export release build, with Native Extensions and Captive Runtime bundled for Desktop projects has been fixed and is available in the final release of Flash Builder 4.7.
    Thanks,
    Hari

  • Slow(er) startup when using captive runtime on windows

    I  just converted two AIR apps from native exe installers (requiring AIR installed) to Captive Runtime relases (just a folder structure).
    One difference i see is that my applications now load a little slower (because of the packaged instead of installed runtime?).
    When using flex 4 sdk the white and centered flex4-loadbar now appears for a few seconds before the splash screen of the app. appears. The same happens when using flex 3 sdk (in compatibility mode) but instead the "initializing" text appears.
    Is this slowdown a known effect of the captive runtime packaging?

    I responded to your other thread in the bugs forum but wanted to also respond here.
    I'm not aware of any slower performance implications when using the captive runtime but I'm going to investigate further.  In the meantime, would you mind opening a new bug over at bugbase.adobe.com regarding the startup performance hit?  It would be great if you could also provide us with a sample application that illustrates the slower startup time.  If you'd like to keep it private, please email me directly at [email protected]
    Thanks,
    Chris

Maybe you are looking for