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!

Similar Messages

[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 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.

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.

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

Adobe AIR with Captive Runtime Support for Mobile | ADC Presents | Adobe TV

In this video, Technical Evangelist Andrew Trice covers Adobe AIR with captive runtime support for mobile application development, which will benefit your Flash Builder projects for the Android OS.
http://adobe.ly/wyNYjD

Witch version of flash builder is this?

AIR captive runtime application for MacOS

Hi!
I create application with captive runtime for Windows and MacOS. I have some problem connected with MacOS specific, cause I'm newbie in this OS.
I dont want to publish my app in appstore, cause the app have problems with appstore rules.
1) How I should to sign my application? I just pack my app as described in manual http://help.adobe.com/en_US/air/build/WSfffb011ac560372f709e16db131e43659b9-8000.html but I don't see any track of code sign in my .app. I thought that it isn't a problem, before I download my app from network - it don't want to run because dveloper unidentified.
2) My application require update system. I Realize it simply for Windows: my AIR application download updates if it necessary (resources, air lib, main swf file, and exe) and then I replace files with other program. There is no problems with updates, cause codesign is only spread on exe file.
But as I understood I can't use same way to update my .app cause it destroy my codesign, as I know. So, how I should update my MAC app?
UPD1: I found a bit information about 1st here: How to sign your Mac OS X App for Gatekeeper | Successful Software. So, I can't use not apple's sign certificate?

It's a good idea to add :tumbleweed: smile to this forum
I spent 3 days for searching answer and making experiments. So, as a result:
1) To pass MacOS Gatekeeper I should use apple developer certificate.
2) I could change content of signed .app file as I wish. I don't try it with my own app because my certificate is not ready yet, but I successfully change contents of few other signed apps - no issues with running was detected. Maybe there is any problem with my understanding of signature..
Helpful links:
osx mountain lion - Non-Apple Issued Code Signing Certificate: Can it Work with Mac OS 10.8 Gatekeeper? - Stack Overflow
How to sign your Mac OS X App for Gatekeeper | Successful Software

Splash screen when application packaged with captive runtime (Windows)

Is there any way to show your applications splash-screen while the Captive Runtime loads?
After packaging my air app with captive runtime on windows the app takes a few seconds extra before showing on the screen. The taskbar-entry appears fast, but the application main window appears much slower than when packaging as native installer without runtime included.

HI DHL83,
Not that I know of but I'll ask around. I've seen at least one other report that startup is slower so I'll try to get to the bottom of this. 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

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.

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

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.

Is it possible to share assets between a windows and a mac AIR app build with captive runtime on one dvd-rom?

Hi there,
I have a question about burning two builds of an AIR desktop app with captive runtime, one for Windows and one for Mac, on a single hybrid DVD-rom that can be played on both Windows computers and Macs.
I've tried sharing the assets (video's and pdf's mostly) between the two builds, but I can't seem to get it to work. The only way I have been able to work around this, is to have the assets in both builds, which results in the double the amount of space on the DVD-Rom.
Is there a way to have the two builds use a single location to find the files? Or do I need to have two builds that both contain all the assets?
Thanks in advance!
Kinds regards,
Maarten

Gotcha!!
I am done with mounting a secondary HDD (thanks to ifixit) and installing Windows 8 Pro 64 bit on it without a worry. Charm, charm!!
Boot Camp 5 guide prescribes all needed steps and when read and used correctly, installation must be an easy task. And all the existing apple hardwares work so good in the Windows environment too.
I am going to help out a friend of mine in doing a similar thing on his mac too. If you got specific questions, please do shoot up here and i should be able to get a reply to it (if at all).
Thanks everyone.
~ Narey

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

AIR 4.0 captive runtime won't run: "requires a version of Adobe AIR" alert

I'm creating an AIR captive runtime application, and it won't run on a target Windows* machine. It displays the following alert instead:
This application requires a version of Adobe AIR which cannot be found. Please download the latest version of this runtime from http://www.adobe.com/go/getair, or contact the application author for an updated version.
How can I package the captive runtime differently so it won't display this message? The application is a pure ActionScript app compiled with the adt binary from the standalone SDK (this is not Flex).
In addition, I'm disturbed that a captive runtime AIR application pings Adobe in any way. I am seeing occasional pings to an adobe site upon launch of the app (something like airdownload2.adobe.com, if I remember correctly). No I'm not using any service calls in my app at this point in development, it's very simple, and should not be pinging the net at all. Why is this happening? I need to disable this too.
* Problem occurring only on a particular Windows 7 Home Premium 64-bit machine. Unfortunately, this is the end client's machine so I can't tinker with it.

Do you have access to the problematic machine? If so, maybe you could try to install Sysinternal's Process Monitor http://technet.microsoft.com/en-us/sysinternals/bb896645
Run the tool, create filter to see just events containing your app name and try to find in the result any issue... you could also compare the log with same log from not problematic machine or with app made with older SDK which was working.
That's all what I can do... it's a shame that nobody from Adobe is interested yet... maybe you could also submit a bug.

Publishing to Captive Runtime

Flash Pro 6, Mac OS10.6.8 Is it true that on a MAC can only create a captive runtime export for a MAC and I need a windows computer and Flash 6 for Windows to Create a .EXE file? I have been working on Flash 5.5 and was excited to see the Captive Runtime option. Very surprised to be told by tech support that I could not create the Captive runtime .exe on a MAC!

Thanks for the response. Talked with my boss and his solution was simpler: Fall back to AIR 3.5 and stay there for the forseeable future.
Perhaps Adobe will fix the AIR captive runtime problem in a future release.
I'll try to update this post if I learn anything new.
Thanks.

Packaging a captive runtime bundle for desktop computers

Similar Messages

Maybe you are looking for