I still do not agree with your installer policy, but it’s good to know why it is as it is.

First: apologies for not coming back to this thread sooner.

Second: Please try the beta 3 installer, now available from http://www.adobe.com/go/getair. We believe it’s much improved, but would appreciate your putting it through the ringer. (Which I’m sure you will!)

Let me try and respond quickly to a few points in this thread. I’m sure I’m leaving some out, but here it goes:

1) We really do listen to customer feedback. Unfortunately that doesn’t mean we can address all of it, for a variety of reasons–including not enough hours in the day.

2) The AIR installers, for both the runtime and applications, will now perform logging. See http://blogs.adobe.com/simplicity/2007/10/air_installer_logging.html. Yes, we should have done this sooner.

3) Yes, on Windows we use MSI under the covers, but we still display our own UI on top–same UI as on the Mac. Just to clarify.

4) We didn’t use packages under the covers on Mac because (a) we couldn’t find a supported way to do that and (b) when we asked Mac admins (yes, we asked first!), they said they didn’t care anyway. (Apparently none of those Mac admins have posted to this thread…)

5) We of course do test these things before we let them out the door, but the whole point of betas is to get the feedback we can’t get any other way. So while I am truly sorry the beta experience wasn’t better for you folks, I’m glad the beta releases are working to improve the product.

Thanks again for your feedback.

regards, Oliver Goldman Adobe AIR Engineering

before install sudo chmod 777 /Library/Frameworks sudo chmod 777 /Applications

after install redo the same lines, with chmod 755

Best, Alex

“So, basically just sudo chmod 777 /Application and /Library/Frameworks, then run the installer, and sudo chmod back to 755.”

NO “~”

Worked for me with B2 in Mac 10.4.11

“Installation of both Adobe AIR itself and AIR applications is done via Windows Installer–more commonly referred to as MSI. Using MSI is the doing the “right thing”, but it certainly isn’t the easy thing.”

Which is very odd since they don’t want to use the installer on Mac OS X (which is quite simple to work with). What rationale is there behind this? Don’t use the simple installer on Mac, but use the hard-to-use installer on Windows, because that’s “the right thing”. Come on Adobe, you can do better than this nonsense.

http://blogs.adobe.com/simplicity/2007/10/air_installer_logging.html

Also, according to Oliver at Adobe AIR beta 3 will ask for admin privileges when starting.

All according to this thread:

http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?catid=641&threadid=1252784&forumid=72

What an incredible drag. I upgrade the Flex Builder 3 beta2 at the same time and this whole process has been categorically unfun.

Maybe it is easier on the PC. Makes sense. Adobe doesn’t have a lot of following in the Mac community.

And Boston is not really a college town. ;)

What I’ve found (will post this over at Adobe to see if it might trigger something useful there) is that the installer is generating an error on a file copy command, apparently having to do with extended file attributes in the file system. From my /private/var/root/system.log:

Oct 11 14:54:00 Mike-Mac /bin/cp: error processing extended attributes: Operation not permitted

I get that error inserted in the log each time I run the installer, and with watching via ‘tail -f system.log’ it’s clear this is a clue to the problem. Doing some research on that error message didn’t turn up any quick answers (#$#&^$#!), but links like this suggest there’s just some outdated code in the Adobe installer that cannot handle certain copy operations for the file system configurations of some Macs (like mine, of course!):

Link

This is not a fix, but just an observation, maybe someone else can use this to unravel the details for this problem.

-M