Skip to main content
August 31, 2011
Question

Mac Permissions issue when Runtime already installed

  • August 31, 2011
  • 1 reply
  • 806 views

Situation...

I am writing an Adobe AIR Application using CS5.5 and AIR 2.6. I use the NativeProcess.start() to call a program which handles our licensing. NativeProcess supported requires the NativeInstaller. On the Mac (10.6.3 Snow Leopard), this is a DMG files produced on the command line with adt and the air file generated by CS5.5.

This all seems to work just fine when I install completely from scratch (Adobe AIR Runtime NOT yet installed on the target machine). The installation process requires my admin password, everything installs just fine, and everything works just fine.

The problem begins when I install to a target machine which already has Adobe AIR Runtime installed. I note that no password is requested by the OS during installation, and during runtime, the NativeProcess.start() call throws exception Error: #3219. I took a look at the permissions of the program which handles our licensing. Our license supports says to expect the following: -rwxr-xr-x (3 x's). However, I only see -rw-r--r-- (no x's).

Is there a way to require an Adobe AIR Application, which is being installed on a machine that already has AIR Runtime, to require the password from the user during installation? Or at very least, to have the right executable permissions?

Thanks!

This topic has been closed for replies.

1 reply

chris.campbell
Legend
September 1, 2011

Hi,

Thanks for bringing this to our attention.  The brief explanation for the authentication is that when you're installing the full deal, we elevate the permissions to install portions of the AIR runtime, this carries over to the application install.  However, when installing a stand alone app, anyone with admin privileges is allowed to install into /Applications, so there is no need to elevate. 

We're a bit confused to what file has the improper permissions.  Is this the executable that native process is trying to execute?  Would you mind sending me the installer so I can test this out internally?  Feel free to contact me at ccampbel@adobe.com and I'll investigate further.

Thanks,

Chris

September 2, 2011

Our application uses a licensing service to prevent illegal copies being run. The licensing service is realized through an executable which pings a server in order to activate the serial code entered by the user. In the AS3 code, we use Adobe AIR 2.6's NativeProcess support to call NativeProcess.start(), trigging that executable to perform said ping. The executable is included in the AIR file, which is converted into a Native Installer (DMG) via the adt command provided by the Adobe AIR SDK for Mac.

While I'm not able to provide you with a build at this time, I'm confident that if you simply attempt to launch an executable from a Mac via an Adobe AIR Application, you will easily reproduce this issue. Just to be sure, here are my specifics again:

Original AIR File:

Windows XP

Adobe Flash CS5.5

Adobe AIR 2.6

Generate the AIR file

Native Installer:

Mac Snow Leopard 10.6.3

Adobe AIR SDK for Mac

Use the AIR file to generate the DMG file

September 2, 2011

This Adobe Forums thread has a similar (if not identical) problem.

http://forums.adobe.com/message/3896265#3896265

I found a work-around and posted it here. It involved using the chmod command to manually adjust the executables permissions.