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.

Similar Messages

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?

[Windows] Captive runtime bundle package certificate signing don't work when icons included

Here is the bugbase ticked: Bug#3949990 - [Windows] Captive runtime bundle package certificate signing don't work when icons included
Application signing don't work when you build captive runtime bundle package which include icons. Don't matter application icons or associated file types icons. It works fine when you build application bundle without icons.
It's a very critical issue, please fix it ASAP.
Also application signing don't work if you using AIR SDK beta: Bug#3950022 - [Windows] Application signing don't work with AIR SDK beta
I'd like to ask everyone affected by this issue to take a minute and vote for the following bugs.
Thanks.

I received feedback from our QA team this morning that they were able to reproduce the bugs but they are requesting access to the .as code if possible. If you'd like to keep this private, please feel free to email it to me directly at [email protected]

How do I create a 64-bit Captive Runtime Bundle?

Hello,
I've been trying to get my head around memory usage in Windows, which led me down a rabbit hole to this question.
As I understand it, applications in 32-bit Windows are allocated 2GB (which can be increased to 3GB with the 4GT setting), but a 64-bit application can make use of a lot more (depending on the version of Windows).
So my main question is how do I create a 64-bit Captive Runtime Bundle (where the whole AIR executable files are packaged in the build folder).
And for bonus points, will this application then make use of the extra memory available?
Thanks

Most likely MAX is and remains a 32 Bit App, even on 64 Bit Windows. And as such it has to continue to accesses a 32 bit VISA installation. But why are you musing about MAX using 32 Bit VISA when you try to run a 64 Bit DLL under 64 Bit Windows? They should be able to run along each other just fine, with no other influence to each other than that you likely won't be able to open an interface in one, while the other has it already open, but that is independent on bitness and will happen even if both processes are the same bitness.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

How to target a minimum OSX version in Mac captive runtime bundle.

Greetings,
I'm working on an Adobe AIR for Desktop project that needs to require OSX 10.5 or greater on the Mac captive runtime bundle. I can't seem to find any way to force this requirement with the adt packaging options or application.xml options. Does anyone know of a way I might be able to accomplish this?
Thanks,
~Mike Z.

Greetings,
I'm working on an Adobe AIR for Desktop project that needs to require OSX 10.5 or greater on the Mac captive runtime bundle. I can't seem to find any way to force this requirement with the adt packaging options or application.xml options. Does anyone know of a way I might be able to accomplish this?
Thanks,
~Mike Z.

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 failure in release build

I have an actionscipt desktop project. in Flash Builder 4.7 i thought i installed AIR 4.0sdk correctly. it certainly works in debug and run mode.
when i export release build with signed application with captive runtime it builds the project in the release-temp folder. i then click finish and it gives me this error "Error creating file:Copy failed"
I'm guessing this isn't something to do with my project and more to do with my install/air4.0sdk. any ideas?

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.

Air runtime bundled with exe installation issue

Hello,
I am sorry if my question is not relevent but i am facing an installation issue with air bundlled with my exe app.
I have created my air app as myApp.exe with flash cs5.5.Air 2.6 has been embeded with the package.If i try to install the package on a system without having internet connection, its asking "Air runtime not found, please download or contact app provider".if net connected,then it will install fine.Actually my app requires no internet acces and purely its an offline desktop app.
Actually is there any background checking / updation is going with the bundled air ?
i have stucked in between this.any help would be appreciated.
thanks,
Arunraj

Is this problem with the installer, or your application at first launch? Would it be possible to send this to me at [email protected] so I can give it a try?
Thanks,
Chris

Packaging a captive runtime bundle for desktop computers

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

Thx for your quick answer.
I found the problem, it wasn't really the temp-Directory:
This one works with the CD-Rom:
var theDatatoCopy:File = File.applicationDirectory.resolvePath("data");
This one works with USB-Stick and on HDD, but not on CD-ROM:
var theDatatoCopy:File = File.applicationDirectory;
So the problem was not the temporary path, but the
theDatatoCopy.copyToAsync(tempFile, true); call.
I don't know why it's different on CD-ROM and USB, but maybe the problem has to do with, that I shoulnd't copy all the stuff in the appDirectory, since some of the content is used.
That would have been easier with relative path names, but that's ok to handle.
"IOError —.... On Windows, you cannot copy a file that is open or a directory that contains a file that is open."
Thank You!

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

Running a Captive Runtime debug build through flash builder

Is there a way to launch a debug configuration through Flash Builder that has the captive run time built in?
I am developing and testing an app for android devices that do not have the newest version of the Air Runtime, some of the devices require captive runtime because they cannot upgrade. I need to be able to launch the app on these devices AND get debug/console information from flash builder for identifying defects.
any ideas?

Hey Wright,
Captive Runtime can only be used at export release build time.
Hence you cannot debug the application with captive runtime bundled.
Thanks,
Hari

How do you publish AIR captive runtime for Windows from OSX in Flash Pro CS6?

Is this possible? If I move the app from a Mac to Windows it isn't looking like an app anymore. It's looking like a set of folders instead. Do I need to change publish options? changeing the extension to .exe didn't fix it. Help appreciated!
Thanks,
Dave

Hi Dave ,
The published AIR captive runtime in Flash from Windows and Mac will have the following structure -
Windows -
MyApp/
    META-INF/
    Adobe AIR/         // The captive runtime minus irrelevant files
    mimetype
    MyApp.swf          // Assets
    MyApp.exe          // An entrypoint that loads the captive runtime
Mac -
MyApp.app/
    Contents/
        Frameworks/
            Adobe AIR.framework/ // The captive runtime
        Info.plist
        MacOS/
            MyApp                // An entrypoint that loads the captive runtime
        PkgInfo
        Resources/
            META-INF/
            mimetype
            MyApp.swf            // Assets
The entry point that loads the Captive runtime is different in the above cases.
Hence we need to explicitly publish from the required platform.
You can even check this link : http://help.adobe.com/en_US/air/build/WSfffb011ac560372f709e16db131e43659b9-8000.html
To create a captive runtime bundle for Windows, you must package the application while running under the Windows operating system.
Thanks and regards,
Sudeshna Sarkar
Adobe Flash Professional Team.

Problem with ANE in Captive Runtime

Hi,
this is my first post to the community so I am not really sure if this is the right forum ... i hope so.
I built an ANE for Android based on the zbar library to scan bar- and qr-codes ... it works pretty fine in debug mode and also works great when I release the app using it with the "Shared Runtime" option.
But I need the captive runtime as our customer wants the app to be as easy as possible for the users and so an additional download of the AIR-Runtime (if its not installed) is not the way we want it to be.
I really hope someone can help me out and point me to the right direction what could be wrong with the ANE.
Basically it is just one function called from ActionScript to the native code and this one starts an activity with a camera view and the zbar listener. When it recognizes the bar/qr code the activity dispatches the status event to ActionScript and exits.
When i build the app with captive runtime nothing happens when i hit the button which should start the native code ... as i dont have flash builder debug information available within the release build i really dont know what the problem is. Also general android LogCat doesnt report any error.
As i stated before, with the shared runtime and in debug-mode everything works as expected and the content of the bar/qr code is returned correctly.
That's why I think the error must be somewhere in the as3 code - but i have no clue where ... i read something about external linkage of the ANE but dont really understand what was meant and if this could be the problem.
Please help, thanks in advance ... and if this is the wrong forum for that topic please point me to the right one.

Hi Carlos,
1) Cross check the below :
a)Ensure that the required JDK is being used in the client system
b)Try clearing the Web Start cache and try downloading again.
c)Start>Programs>Java Web Start>File>Preferences>Advanced>Clear Folder
2) XI TST Check whethere you have enough TABLE space.
3)Refresh the Cache :
a)Start transaction SXI_CACHE.
b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
And also try this :
Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
Regards
Agasthuri Doss

SDK component Runtime.apk is out of date export captive build for Kindle Fire

Hello
Kindle fire only supports AIR 2.7 and I'm trying to export a build release in Flash Builder 4.7 with the AIR runtime included (captive build). Whenever I build I get the following error:
SDK component at air/android/device/Runtime.apk is out of date
I tried running the updater and it said I'm up to date. I did download the SDK and put it in my home folder but I can't seem to change the SDK reference in the preferences.
(I had another java out of memory error including my ANE file but I turned it off just to get a build out. Not the focus of this discussion)
It would be nice if flash builder just let me reference my freshly downloaded SDK but instead I have to sift through their document structure guessing where I should be updating the Runtime.apk that SHOULD be up to date already.
I have had to go in to the package itself and modify the ini files and over-write the adb files from the fresh download of the SDK before.
I'm guessing there is a way to update the Runtime.apk but i have so many bin executables spread all of my computer it's hard to tell what flash builder wants!!!
There is always one problem after another developing with Flash Builder ... Please help.

Just be sure you've downloaded the correct AIR 3.6 SDK specific to Flash Builder! On this page: http://www.adobe.com/devnet/air/air-sdk-download.html in small print is this note:
Note : Flex users will need to download the original AIR SDK without the new compiler. Mac Windows.
Be sure to install the appropriate sdk if you're using Flex in your mobile project. Otherwise the main download will work with ActionScript only projects in Flash Builder 4.7
Can you confirm you installed the correct SDK? Also with ANEs, it's important to identify what version of AIR the ANE supports.
If you still run into trouble with your current configuration, try building a new mobile project and export release build with captive runtime and see if it compiles correctly. If it does, then it's going to be a problem with your current project, and I'd look at how the ANE is packaged. See if there's documentation on how to include the ANE, etc. If you still can't compile a blank mobile project, then your AIR installation is incorrect.
iBrent

How do I associate a captive-runtime AIR app with a filetype on OSX, without breaking codesigning?

The documentation from both Adobe and Apple says that it is required to change the Info.plist file in order to associate an app with a filetype
However, one is also required to codesign the app in order to pass through OSX's Gatekeeper security restrictions.
How can I get pass this problem? If I codesign from within AIR, and then change the Info.plist in the exported bundle, won't it break the codesigning?

Have you tried using NativeApplication.nativeApplication.setAsDefaultApplication(extension:String) method?
According to the documentation:
"Sets this application as the default application for opening files with the specified extension.
Note: This method can only be used with file types declared in the fileTypes statement in the application descriptor."
I used it successfully in the past when creating a video player app for Mac/Windows that became the default for FLVs and F4Vs, but it was before captive runtime was available so Im not sure if that makes a difference or not. Also not sure how this affects code-signing but might as well give it a shot if you havent tried it or if you know it wont break anything. If you are using Flash CS6 or CC, just remember to add the file extension(s) you want to associate under AIR Settings -> Advance -> Associated file types. Not sure how Flash Builder handles those settings.
NativeApplication - Adobe ActionScript® 3 (AS3 ) API Reference

Export Captive Runtime Bundle with ANE

Similar Messages

Maybe you are looking for