Skip to main content
Participating Frequently
June 16, 2011
Answered

Have AIR install permissions issues for MacOS X been addressed in v2.7?

  • June 16, 2011
  • 1 reply
  • 649 views

Hello, Adobe team,

My company develops Adobe AIR-dependent software for MacOSX that has been affected by AIR's permissions problems this past couple of years. The script posted by Adobe's Chris Campbell solves most of our client's install issues. To improve our user experience with our upcoming software release, we plan to incorporate those repairs into our installer.

Did versions 2.6 and 2.7 of Adobe AIR already address these problems? We haven't seen newer threads confirming this and want to avoid applying changes that may not be necessary.

Thank you for your feedback

-cpiDeveloper.

This topic has been closed for replies.
Correct answer chris.campbell

Thanks, Chris. It's good to know there aren't many issues. Roughly what percentage of installs are affected?

Let's assume that the issue you mentioned can be replicated under the right conditions (which are still unknown by Adobe.) Although not ideal, it seems that IT installation staff could notice and correct the problem during roll-out campaigns, before the installer causes user-facing issues. But we already force a silent AIR install, so the potential problem won't be triggered / found until days after their installation, when staff and classroom students first run our AIR-dependent program. That would be a difficult burden for our clients.

What can be done to protect an installer against that situation?

Thanks

cpiDeveloper.


This occurs on a miniscule number of machines.  Since I've been monitoring for it, I think I've seen this popup maybe 4 or 5 times tops.

I haven't tried the scenario you mention (you do a silent install, the EULA appears later when the user first launches the app.)  However, you can bypass the EULA by creating a text file with the contents "2" and the name eulaAccepted and save it to the user's ~/Library/Application Support/Adobe/AIR folder.  This will bypass the EULA dialog.

If you ever run accross this case, please have someone post here or email me directly.  I'd be willing to help troubleshoot and I'd like to take a look at the system.

Thanks,

Chris

1 reply

chris.campbell
Legend
June 16, 2011

Hi,

AIR 2.6 and 2.7 runtimes should indeed resolve the problems that my script addressed.  From what I've seen, OS X related issues have dropped dramatically since the release of 2.6.  We still get issues from time to time, but I don't believe they are caused by folder permissions.

Please feel free to post or contact me directly (ccampbel@adobe.com) if you run into installer issues and I'll try and help get them resolved.

Thanks,

Chris

Participating Frequently
June 17, 2011

Thanks for your quick response, Chris! We are thankful that Adobe has taken care of these permissions problems.

You mentioned, that a few remaining MacOSX issues are not permissions related. Could you please confirm that these are replicatable at install-time under the right conditions?

If so, could you please provide some proven workarounds or forum links? We wish to review them and prepare with similar pre-install fixes. My company needs to ensure shield the user from troubleshooting AIR installs.

Thank you in advance!

cpiDeveloper

chris.campbell
Legend
June 17, 2011

The only one that comes to mind is an issue we've had in the past with the runtime's EULA dialog.  We've seen cases were the runtime installer launches, but no window appears.  From our investigation (we haven't reproduced this internally) it appears to be a conflict with the Webkit control that displays the EULA.  We've worked around this by having the user install the runtime via the command line using the silent and auto accept eula parameters.

Please feel free to ping me anytime either here or directly at ccampbel@adobe.com and I'll do what I can to help out.

Thanks,

Chris