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.

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]

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

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 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?

Insecure JNLP java_vm_args cannot avoid security alerts even with a signed JNLP

I am using a signed JNLP launch file that is validated against JNLP-INF/APPLICATION_TEMPLATE.JNLP in my main resource JAR (which I know works because if I change the JNLP in an invalid way the Java Plugin JNLP Client complains as expected). The main resource JAR is also properly signed with a real code signing certificate, marked as a Trusted-Library in the Manifest, and has "all-permissions" in the JNLP.
In my JNLP launch file, I have some java_vm_args that are considered insecure. For example, --XX:+PrintGC. Despite the fact that the JNLP is signed, I get two security alerts:
1) A yellow exclamation mark alert which when More Information are examined asserts that the JNLP file is NOT signed.
2) If I accept and run anyway, then I get another alert saying:
"This application is going to perform an insecure operation. Do you want to continue?"
Is there any way to avoid these issues while still being able to specify arbitrary VM arguments for the applet?

Found the answer in your link. :-)
If the Application-Library-Allowable-Codebase attribute is present and matches the location from which the RIA is started, then a single host is listed in the Location field for the prompt and the option to hide future prompts is provided. If this attribute is present and the files are accessed from a location not included for the attribute, then the RIA is blocked. If this attribute is not present, then multiple hosts that correspond to the locations of the JAR file and the JNLP file or HTML page are listed in the Location field for the prompt. When multiple hosts are shown, the user is not given the option to hide future prompts. Use of this attribute is recommended so the files for the RIA are accessed only from known locations.

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!

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.

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

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.

Why is the file size very big when I add captive runtime?

I have a game that is 2.56 MB. When I package it up for a captive runtime apk it becomes 12.2 MB. This is very reasonable, but my problem is that when I add this apk on my phone through debugging, the size of the game jumps from 12.2 MB to 30.7 MB! I am using Air 3.9 and I don't understand why it is that big, can anyone help me please!

IPA and APK are .zip files in disguise. Your app is simply unzipping all or a portion of itself when it is installed, depending on OS. For example one of mine is 35MB (APK) and it goes to 50.2MB after install every time.
The captive runtime has little to do with it besides it's just one more compressed item. If you added any other random ~10MB of assets instead of captive runtime, depending on the content you'd end up with around the same size app anyhow.

Command line arguments to Captive Runtime Air App

I am having problems passing command line arguments to my Captive Runtime Air App on Mac OS X. Argument handling occurs perfectly when running in ADL, via the InvokeEvent.INVOKE event. However, when running the native executable, it seems that no command line arguments are getting passed through.
How do I pass command line arguments into my Captive Runtime Air App?

See:
http://javafx-jira.kenai.com/browse/RT-24993
"Native packaging: native launcher should pass command line parameters to the app"
fixed for jdk7u10
jdk7u10 is downloadable from here:
http://jdk7.java.net/download.html
It may take a week or two for the fix to propagate into there.

Captive runtime -target bundle does not create the package fails after creating a .tmp folder

Hi Adobe Team, Experts,
I cannot create a captive runtime package successfully on windows.
This is the command I am using to create a captive runtime package for windows
adt -package -keystore CodeSigning.pfx -storetype pkcs12 -storepass password -target bundle TestPackage Test-app.xml Test.swf
The issue is the above command creates a .tmp directory "adt5072057577475387637.tmp" but does not create a directory by name "TestPackage" .
Another observation is the above command works in-consistently it seems to create the directory sometimes but fails for the most.
Funny enough !! It worked when I was creating a POC but now when I am trying to release it stops working on me.
It is the same machine I did POC on.
The application descriptor has
<supportedProfiles>desktop extendedDesktop</supportedProfiles>
I have also tried
adt -package -keystore CodeSigning.pfx -storetype pkcs12 -storepass password -target bundle TestPackage.exe Test-app.xml Test.swf
as mentioned here - http://www.riaspace.com/2011/08/bundling-air-3-runtime-in-air-desktop-applications/
Flex SDK version - 4.6.0
AIR SDK version - 3.1
JDK version - jdk1.6.0_18
Please advise as to how to fix this issue.
Thanks,
vshare

Hi vshare,
did you ever find a solution to this? I'm running into the same problem with no apparent solution.
Thanks!

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

Similar Messages

Maybe you are looking for