AIR Installers fail to install on Lion 10.7

This happens every time, including trying to install the older versions. I've removed everything, tried chmod 777 my app folders, etc. nothing works. Ideas?
1/30/12 4:27:00.445 PM Adobe AIR Installer: Runtime Installer begin with version 3.1.0.4880 on Mac OS 10.7.2 x86
1/30/12 4:27:00.445 PM Adobe AIR Installer: Commandline is: -psn_0_1470823
1/30/12 4:27:00.445 PM Adobe AIR Installer: No installed runtime detected
1/30/12 4:27:05.099 PM Adobe AIR Installer: Relaunching with elevation
1/30/12 4:27:05.100 PM Adobe AIR Installer: Launching subprocess with commandline /Volumes/Adobe AIR 1/Adobe AIR Installer.app -ei
1/30/12 4:27:07.147 PM authexec: executing /Volumes/Adobe AIR 1/Adobe AIR Installer.app/Contents/MacOS/Adobe AIR Installer
1/30/12 4:27:07.393 PM [0x0-0x167167].com.adobe.air.Installer: 2012-01-30 16:27:07.391 Adobe AIR Installer[11948:20b] In modifyShouldRestoreOnRelaunchCounter, _LSSetApplicationInformationItem(_kLSPersistenceSuppressRelaunchAtLoginKey) returned error 268435459
1/30/12 4:27:08.052 PM Adobe AIR Installer: Runtime Installer begin with version 3.1.0.4880 on Mac OS 10.7.2 x86
1/30/12 4:27:08.052 PM Adobe AIR Installer: Commandline is: -ei
1/30/12 4:27:08.052 PM Adobe AIR Installer: No installed runtime detected
1/30/12 4:27:08.071 PM Adobe AIR Installer: Error 0xfffffda8 (-600): CGSSetHideOnDeact: error retrieving current process
1/30/12 4:27:08.071 PM Adobe AIR Installer: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
1/30/12 4:27:08.107 PM Adobe AIR Installer: Launching subprocess with commandline /usr/sbin/chown -hfRP duane "/Users/duane/Library/Application Support/Adobe"
1/30/12 4:27:08.107 PM Adobe AIR Installer: Launching subprocess with commandline /bin/chmod -fRP +rw "/Users/duane/Library/Application Support/Adobe"
1/30/12 4:27:08.107 PM Adobe AIR Installer: Launching subprocess with commandline /usr/sbin/chown -hfRP duane "/Users/duane/Library/Preferences/Macromedia/Flash Player/www.macromedia.com/bin"
1/30/12 4:27:08.110 PM Adobe AIR Installer: Starting silent runtime install. Installing runtime version 3.1.0.4880
1/30/12 4:27:25.753 PM Adobe AIR Installer: Registering /Applications/Utilities/Adobe AIR Application Installer.app/Contents/Info.plist
1/30/12 4:27:25.766 PM Adobe AIR Installer: Got an unexpected fatal error while modifying plist: Error: Failed to register application (-10822)
1/30/12 4:27:25.767 PM Adobe AIR Installer: Error occurred during register filetype operation; beginning rollback: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="Failed to register application (-10822)" errorID=0]
1/30/12 4:27:37.214 PM Adobe AIR Installer: Rollback complete

Sorry you're running into this problem.  After searching for this error (10822) it appears that it might be related to OSX's launchd service.  See these discussion threads:
Error code 10822
Are you able to install other software besides AIR?
Chris

Similar Messages

  • AIR Applications fail to install (Acer Aspire One, Linux)

    I've successfully installed the latest version of AIR for Linux on my Aspire One, although it took a few attempts.
    I am, however, not succeeding in installing any apps.
    1. My system believes that .air files are actually ZIP files and offers to unpack them: there seems to be nothing I can point them at to be opened by AIR itself.AIR does not appear in any menus, app lists etc
    2. If I go to a site that offers a "badge" install, the install system correctly recognises that AIR 1.5 is installed (checked box in the installer) and doesn't try to install it again. However, the apps do not install successfully - all fail with an Error #2004 and ask me to try again, which always fails.
    I can't seem to find any information whatsoever on this anywhere and I'm a bit surprised. It is surely not impossible to achieve, and I equally don't believe nobody else has had any trouble.
    Suggestions anyone?
    Thanks!
    --Richard E

    Right! "rpmbuild" was the answer to installing AIR successfully on this machine.
    Assuming that you have somewhat unlocked the machine as described in http://macles.blogspot.com/ and elsewhere, this simplest way of getting rpmbuild installed is to open a terminal and, as root, do "yum install rpm-build" - note the hyphen in the package name. If you aren't subscribed to a suitable repository, you can find it pretty easily with a Google for "fedora8 rpm-build".
    With rpm-build in place, AIR installed successfully using "./AdobeAIRInstaller.bin".
    ".air" applications are now correctly identified as belonging to AIR and badge installs also work.
    My intention in doing all this was to get a suitable Twitter etc app running on the machine, so I first tried the current version of Seesmic Desktop. It opened normally and allowed me to enter account details… and lo! it downloaded tweets! Unfortunately I never managed to get it to do that again. A bunch of small authorisation windows opened up, one for each installed account, requiring confirmation of password, and I couldn't enter anything in the field with the main window open. Minimising the main window I could now enter passwords, and OK dismissed the window, but it didn't seem to do any good. I have not seen a tweet since and all the panels in the main window are empty. A pity.
    My other favourite Twitter app is Tweetdeck - in fact I think it's superior to Seesmic Desktop if you just run a single Twitter account. Here the main window opens somewhat off-screen and blank (black) with control buttons at the top. Unfortunately although the buttons reveal their tooltips on mouseover, you can't actually access any of them, notably the account setup button. Thus the app is not usable.
    Third attempt was Twhirl, also from Seesmic (http://www.twhirl.org/). The version I had previously downloaded, 0.8.6, opened an account setup window but when you entered a password it just sat there. Luckily behind it was a window offering an update. Updating the package installed 0.9.2. This time the account window allowed the entering of an account name and password and duly displayed a window of tweets! And I was also able to write and send tweets successfully. Success! You can enter details for multiple accounts, and each has its own resizable window that contains messages pertaining to the account. Not as useful for me as Tweetdeck or Seesmic Desktop, but entirely usable (Desktop is actually a bit big for this machine's display anyway). However closing and reopening Twhirl I discovered that the application is not remembering passwords even when you tell it to - though it does remember the account names. Although I would like a fully-functioning app (and preferably one or both of the other two) this will do for the time being.
    I notice that issues regarding passwords and authorisation are the common factors in these misbehaviours: if anyone can shed any light on this, please let me know.
    Thanks to GauravKhurana for the key to solving this issue and the support in discovering it.
    --Richard E

  • Purchased MacBood Air. Want to install Mountain Lion to our MAC. How do you do that?

    I purchased a MAcBook Air, and want to install the OSX Mountain Lion that came with it to my MAC.  How do I do that?

    You have to purchase Mountain Lion for the other Mac. That's because the Mountain Lion license that comes with the MacBook Air only allows you to install it in this MacBook Air.
    In your other Mac, follow these steps to upgrade to Mountain Lion > http://www.apple.com/osx/how-to-upgrade Note that, if you have 10.5 or 10.4, you will have to upgrade to Snow Leopard if it's supported > http://support.apple.com/kb/sp575
    Before upgrading, make a backup of your files and check that your apps are compatible > http://www.roaringapps.com

  • XCODE 4 fails to install in LION

    I did a fresh install of Lion using the rescue usb disk and it seemed to be going well until I downloaded XCODE 4 from the App Store.  The program fails stating I need to contact the Developer.
    I'd appreciate some help understanding what I need to do to get XCODE working.
    Here's the output from /var/log/install.log
    Aug 30 17:36:18 Horsts-MacBook-Pro installd[898]: PackageKit: Extracting file://localhost/Applications/Install%20Xcode.app/Contents/Resources/Packages/D eveloperTools.pkg (destination=/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/Cleanup At Startup/PKInstallSandbox-tmp/Root, uid=0)
    Aug 30 17:36:27 Horsts-MacBook-Pro installd[898]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=110 "An error occurred while extracting files from the package “OpenGLApps.pkg”." UserInfo=0x7faf0b453690 {NSLocalizedDescription=An error occurred while extracting files from the package “OpenGLApps.pkg”., NSFilePath=/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/Cleanup At Startup/PKInstallSandbox-tmp/Root, NSURL=file://localhost/Applications/Install%20Xcode.app/Contents/Resources/Pack ages/OpenGLApps.pkg, PKInstallPackageIdentifier=com.apple.pkg.OpenGLAppsLeo, NSUnderlyingError=0x7faf0b439810 "The file couldn’t be opened because it isn’t in the correct format."} {
                NSFilePath = "/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/Cleanup At Startup/PKInstallSandbox-tmp/Root";
                NSLocalizedDescription = "An error occurred while extracting files from the package \U201cOpenGLApps.pkg\U201d.";
                NSURL = "file://localhost/Applications/Install%20Xcode.app/Contents/Resources/Packages/ OpenGLApps.pkg";
                NSUnderlyingError = "Error Domain=NSCocoaErrorDomain Code=259 \"The file couldn\U2019t be opened because it isn\U2019t in the correct format.\"";
                PKInstallPackageIdentifier = "com.apple.pkg.OpenGLAppsLeo";
    Aug 30 17:36:27 Horsts-MacBook-Pro installer[895]: install:didFailWithError:Error Domain=PKInstallErrorDomain Code=110 "An error occurred while extracting files from the package “OpenGLApps.pkg”." UserInfo=0x7f9f734b3840 {NSUnderlyingError=0x7f9f734b3880 "The file couldn’t be opened because it isn’t in the correct format.", NSFilePath=/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/Cleanup At Startup/PKInstallSandbox-tmp/Root, NSURL=file://localhost/Applications/Install%20Xcode.app/Contents/Resources/Pack ages/OpenGLApps.pkg, PKInstallPackageIdentifier=com.apple.pkg.OpenGLAppsLeo, NSLocalizedDescription=An error occurred while extracting files from the package “OpenGLApps.pkg”.}
    Aug 30 17:36:28 Horsts-MacBook-Pro installer[895]: Install failed: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.

    I deleted "Install XCode" from /Applications then opened App Store and downloaded XCode4.1.1 again.  I tried the install process again and it completed successfully.  Why the download from 2 days ago failed to install properly, I haven't a clue?  Nevertheless, I have a working XCode and for that I am grateful.

  • AIR app failed to install in ipad

    Hi friends,
                 I have developed AIR application using Flash Builder 4.6. Its working fine with emulator. When i tried to install it into my iPad, it shows the error "App failed to install". I have recreated the Provisioning file many times, but no luck. my iPad version is 6.0.1. Any one know about this issue? how to slove this? please help me.
    Thanks

    this is from provisioning profile
    <key>Entitlements</key>
              <dict>
                        <key>application-identifier</key>
                        <string>XXXXXXXXXX.com.niran.*</string>
                        <key>get-task-allow</key>
                        <false/>
                        <key>keychain-access-groups</key>
                        <array>
                                  <string>XXXXXXXXXX.*</string>
                        </array>
              </dict>
    this is from my application
    <id>com.niran.Main</id>
    any mistake here?

  • RoboHelp's air installers no longer install with AIR 4.0 update?

    Has anyone else encountered this issue?
    After updating to AIR 4.0.0.1390, our RH air help installers no longer work. This includes .air help from 2 - 3 years ago, which have installed fine all these years, all the way up to a recent .air file we created for an upcoming release. This problem occurs on both Mac and Win, with the US version of AIR and the Chinese version of AIR, and it's a critical problem for us. Now when you double-click the .air file to install the help, you get this message:
    "Sorry, an error has occurred. The application could not be installed because the installer file is damaged. Try obtaining a new installer file from the application author."
    Well, the application author is us. But this isn't a problem that we can fix, because it happened with the AIR 4.0 update.
    Version 3.8 of AIR works fine. Version 3.9 broke our context-sensitive help on the Mac (bug 3648177, filed in Oct, not that it did us any good). Now version 4.0 has broken our air help completely. We are transitioning to HTML5 help but not quickly enough, it seems.
    Can anyone confirm that the same thing happens?
    Thank you,
    Alexandra

    Here is the current status of this problem. I am going into detail in case this helps anyone else in a similar situation.
    Five years ago, I created my first AIR help file and I used a self-signed certificate without a timestamp. Had I read Peter Grainge's info, I would have used a timestamp, but Adobe's help says "Select to include a timestamp on the digital certificate. The timestamp provides information on how long the certificate is valid." Since I thought the certificate would always be valid, I didn't know this was important.
    Fast forward five years. I've created many, many .air help files in many languages, all using the same certificate that I originally created. Thousands of customers have these help files installed, and their certificates have all expired. No one can install or reinstall these help files now.
    Our installer engineer worked hard to find a way to extend the certificates. However, it appears that even though I have the latest version of AIR (4.0) on my system, RoboHelp *may* be using AIR 1.5 to create the .air files, even in RH 11 (this is not confirmed by Adobe but in the output, the HelpViewer-app.xml file indicates that this is true). This is important, because apparently AIR certificates after AIR 1.5.3 have a grace period which allows them to be extended. Certificates from AIR earlier than that cannot be extended.
    I can create new output with a new certificate and a timestamp (I have archives of all my help projects). But, the new certificate and timestamp causes AIR to treat the updated help as if it were new help. It won't install automatically over the old help, and our context-sensitive help is broken.Our engineer tried hard to find a way to prevent the updated help with the new certificate to be treated as a new help, but he says that for older versions of AIR (like 1.5), the "publisher ID" is not separate from the certificate. A new publisher ID is required with a new certificate.
    This is a bad situation, to say the least.
    Vikas has tried to help but what we were able to determine is that my context-sensitive help is functioning properly. I know this anyway, because when the engineer updates the publisher ID for our software to connect to the updated help, all works as expected. But we are not going to re-issue previous versions of our software so that the context-sensitive help functions correctly. All customers with older help who need to reinstall it for any reason, will no longer have context-sensitive help.
    I am still hoping to learn something from an Adobe engineer that will help us be able to re-issue our help and have it not be viewed as a different help installation, or extend our certificates. Vikas does not have this information, though I appreciate that he tried to assist us.
    In my research on this, I also found one person who used a certified, signed, certificate and had it expire after five years. And someone else who used a timestamp but still had the help expire. On the AIR support site, it definitely states that self-signed certificates expire after five years - now I know this. But not a word about this in RoboHelp help.
    In hindsight, I am sorry that I created my help files with AIR.
    Alexandra

  • Itunes 10.4 fails to install on lion

    After I installed Lion on my MacBook Pro, I tried to install itunes, Software updates, or iwork updates nothing works, any help is appreciated

    I have the same F***ing problem!!

  • Lion Problem, failed to install mountain lion

    Hello guys, i'm using Macbook Unibody late 2008  with intel core2 duo 2.4 Ghz
    Currently i'm running on LION OSX, and i want to upgrade my OS to Mount Lion.
    In the middle of the installation i found a trouble, after the macbook restart. The installation process still goin well, until 2/10 of the installation bar progress a notification shown up. It say installation failed, no - recovery blah blah blah found. I'm confused how to solved this problem, is there anyone can solve the problem yet? i'm already try all kind of the solution posted in the discussion first, but still it fails.
    My macbook using a 250Gb harddisk, with arround 200 Gb for Macintosh HD and 45 Gb for Windows XP Bootcamp.
    oh yeah, this is the result of diskutil list command in terminal
    r********s-macbook:~ riz*******ru$ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *250.1 GB   disk0
       1:                        EFI                         209.7 MB   disk0s1
       2:                  Apple_HFS Mac HD                  203.5 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
       4:       Microsoft Basic Data BOOTCAMP                45.7 GB    disk0s4
    ri**********s-macbook:~ ri******ru$
    Thank you

    OS X Lion: Installer reports "This disk cannot be used to start up your computer"

  • OSX Mountain Lion fails to install on 2009/2010 MacPro

    I have a Dual Xeon dual cores MACPro and just got the new OS however it fails to install on the MACPro with the error message  "Mountain Lion is not compatible with this computer"
    My current OS is 10.7.4, does anyone have any imput on this issue has this been seen by anyone else?
    Any help would be apreciated.

    Macs that can be upgraded to OS X Mountain Lion
    iMac (Mid 2007 or newer)
    MacBook (Late 2008 Aluminum, or Early 2009 or newer)
    MacBook Pro (Mid/Late 2007 or newer)
    MacBook Air (Late 2008 or newer)
    Mac mini (Early 2009 or newer)
    Mac Pro (Early 2008 or newer)
    Xserve (Early 2009)
    I'm guessing that you have a Mac Pro 1,1 or 2,1 model from 2006/7. They cannot run Mountain Lion.

  • I recently attempted to re-install Mountain Lion on my MacBook Pro late 2012 model and the internet recovery is failing.

    I recently attempted to re-install Mountain Lion on my MacBook Pro late 2012 model and the internet recovery is failing. I have absolutely no clue what to do here. Any help is greatly appreciated. Thank you.
    - Currently if I boot it up there is a flashing folder icon with a question mark in it. I am assuming this means there is no OS because I wiped the SSD and tried to reinstall Mountain Lion
    - When I hold Command+R, it prompts me to Choose Network... the problem with this is the wifi constantly is disconnecting. The Retina 2012 does not have an ethernet port so i have considered buying the attachment then returning when done.
    Once again Thank you in advance.
    Best.

    There is nothing to do if you don't have a reliable Internet connection unless you have a copy of the Mountain Lion installer application from when you first installed it.
    Install or Reinstall Mavericks or Mountain Lion from Scratch
    Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
    OS X Mavericks- Erase and reinstall OS X
    OS X Mountain Lion- Erase and reinstall OS X
    OS X Lion- Erase and reinstall Mac OS X
    Note: You will need an active Internet connection. I suggest using Ethernet if possible
                because it is three times faster than wireless.

  • Installing Mountain Lion from Snow Leopard, Install failed and HD write-locked

    I recently downloaded the mountain lion installer from the App Store and I ran the installer. Stupid person as I am, I did not have any backups for my file and I naively assumed that an apple OS installer would be without flaws. Boy, was I wrong. I need every bytes of my data (or close to every bytes) but the installer failed.
    Mid installation, the installer stopped and said that the installation failed and that I need to repair my disk. So I restarted the computer and I ran disk utilities (my start up disk was the OS installer and the installer allows me to run several programs, including terminal, disk utilities, and by the way, when I held option while starting up to see which start up disks I have, I only had the OS installer as the start up disk. Also, the installer allows me to run a program called "Startup Disk" when I click on the apple logo on the top left corner, but it doesn't allow me to startup my computer using Macintosh HD) and noticed that when I highlighted Macintosh HD, my "Repair Disk" button was grayed out. So first things first, I ran the "Verify Disk" button but after a minute or so, Disk Utilities said that verification failed and that Macintosh HD needs to be repaired. But the "repair disk" button is grayed out! So I went to the Mountain Lion installer again and ran it. Of course, it failed again so I restarted the computer.
    So I tried to first back up all files in Macintosh HD to an external hard drive using Disk Utilities, and I used features such as "New Image" and "Restore" but they both ended up in "Input/Output error". I tried many methods with Disk Utilities but they resulted in errors.
    After some research, I noticed that some people's computers worked after they reset their PRAM. So that's what I did. I held command+option+P+R when computer started up and I reset the PRAM. When the start up disk (which is the OS installer, not the normal operating system) loaded, I was greeted with choose languages option and then I was back in the Mountain Lion installer state. I again ran the installer again, hoping something would be different, but then it was different. But not in a good way. When I was told to choose where I would like to install Mountain Lion, I noticed that Macintosh HD was grayed out. Last time, I was at least able to run the installer but this time, Macintosh HD was grayed out. The installer said that my Macintosh HD was locked. After some research, I learned that apparently, the Mountain Lion installer write-locks Macintosh HD mid installation.
    So now I am stuck and I am thinking of two things (plus some questions)
    1. I am wondering if there is a way to unlock Macintosh HD. But even if I can unlock Macintosh HD, there is no guarantee that the installer will successfully install Mountain Lion, am I right?
    a. so how can I un-write-lock Macintosh HD?
    2. More realistically, I am thinking of borrowing someone else's macintosh computer and use it as the backup center. I have a firewire cable and a terrabyte external hard drive. So what I'm thinking is that I'll hook my computer in target mode to my friend's computer and I will also plug in my external hard drive to my friend's computer and then I can download and run Carbon Copy Cloner from my friend's computer to copy all data from my Macintosh HD to my external hard drive. And then I will erase my Macintosh HD, freshly install Mountain Lion onto it and then copy all data back from my external hard drive. But I am not sure about few things.
    a. it looks like my Macintosh HD is write-locked. Can I still use Carbon Copy Cloner to copy all data from Macintosh HD (in target mode) to my external hard drive?
    b. will my computer allow me to erase (or format) Macintosh HD?
    c. will my erased/formatted Macintosh HD able to install + be installed Mountain Lion OS?
    If you are here, then you have read my long long problem. Thank you very much and I would really really really appreciate your answers and opinions. Thanks

    I'm not sure where you read that about the disk being "write-locked." That doesn't make much sense, given that the major task an installer like this must achieve is writing a whole bunch of files to the hard drive. I think your source was mistaken.
    As to what happened, it sounds like your hard drive was badly corrupt to start with, or possibly was on the edge of failing and is now in the process of dying entirely. If you don't have backups of your data, that does not bode well for you, unfortunately. If you can manage to use target mode to copy your data, do that.
    Once you're sure you've got all your data, you need to start up from your Snow Leopard install disk and repair the hard drive. (Since it sounds like the Mountain Lion installer didn't work, I wouldn't trust the recovery partition that Mountain Lion installs.) Or, even better, just erase the hard drive entirely and reinstall Snow Leopard. Then, once you're back up and running, with all your data back on the system and with Snow Leopard updated to the most recent version, try installing Mountain Lion again. If any of that fails again, the problem is likely to be a dying hard drive, and you'll need to replace it.

  • I get an "install failed" message. "Recovery system can't be created-click restart to return to previous version of OS X." This doesn't work. My Mac continues to try to install Mountain Lion. What is the elegant way to get my system back?

    I get an "install failed" message. "Recovery system can't be created—click restart to return to previous version of OS X." This doesn't work. My Mac continues to try to install Mountain Lion. What is the elegant way to get my system back?

    The first time I attempted to install ML was on a late 2011 MBP.  It ran for three minutes then gave me the error message: Could not install OSX due to an unexpected error.  I was using the original ML install app, not a USB or other drive.  
    After a couple of restarts wiht the same result I saw a message to the effect that the install was trying to close open apps.  I closed apps  manually a few times to no avail.  I shut down instead of restarting then booted into Safe mode (hold down the shift key when starting) and that did it.  The install went smoothly after that. 
    I since installed ML in two iMacs using a cloned copy of the install app on a USB drive.  This time I shut down the computers and booted into Safe Mode first and there were no problems. 
    I don't know if this issue is the one causing you these problems but it is a simple enough solution to try.
    Jay

  • Air project works in test but fails when installed.

    I have a little project I'm trying to put together as a stand-alone widget.  It loads some sounds that are set up in sets and saved in a subdirectory of the application directory.  I have a movie clip in the library that appears when the "Config" button is pressed.
    Works great in test mode.  The sounds are loaded and play.  The config screen shows up when the button is pressed.  The components (two sliders) work and their listeners fire.  Wonderful!
    But when I pack it up as an installable AIR file and then actually install it on my poncuter, epic fail.  The sliders don't appear, the config button doesn't call up the configure movieClip and no sounds are played.  The buttons that I placed on the stage at design time appear but don't appear to function.  Nothing I added programmatically appears.
    Is this an Adobe CS3 problem or did I miss something in the security sandbox?  No files are being written to,  I'm getting a directory listing of ./sets and then opening the files in that directory where .isDirectory comes up false.  The files are XML and point to a folder off the ./sets folder and the files in that set.
    I could probably track this but I have no experience debugging an AIR project.  Trace is not working in development.  How do people debug the final?  Output to a dynamic text field?

    Sorry to hear you are having a tough go of it...
    there should be no reasons that your application functions differently debugging than when you install the application so the behavior you are seeing is likely something easy to fix (as opposed to having to re-write a bunch of AS code :D).
    Couple of Questions:
    1.) Are you using CS3 as-is out of the box - or did you manually upgrade your AIR SDK inside Flash Professional to target a later version?
    2.) What version of AIR are you targeting?
    3.) What version of AIR do you have installed on your system?
    4.) What OS are you running on?
    5.) Can you install any AIR applications on your machine and have them run properly? (Bunch of AIR apps here: http://www.adobe.com/go/airmarketplace)
    6.) It sounds like you are likely using CS3 and not the command line tools - but if you are using the command line tools (ADT) to create your AIR package what command line do you use to create it?
    That should help get things rolling...but likely the best course of action is for you to send us your project so we can take a look. You can send your project to cthilgen at adobe.com - please do not send a zip as our mail system will auto-reject it.
    Also, you should be able to get trace output. If you are using CS3 the trace output goes to the output panel. (Windows->Output) If you are using the AIR command line tools (ADL) - debug output is enabled by default (you have to manually pass -nodebug to turn it off).
    Hope this helps.
    Thanks,
    Chris Thilgen
    AIR Engineering

  • Adobe AIR fails to install

    As above AIR fails to install & I have been told by adobe to disable automatic graphics switching under energy saver, but I cannot find automatic graphics switching. Where can I find it?

    I did not find automatic graphics switching, but after several failed attempts of trying to install it, it eventually installed.

  • WebOS Doctor 3.0.2 68 fails to install on Mac Lion (10.7.1)

    For what it's worth, the Doctor fails to install on the latest version of the Mac operating system.  From the install.log:
    Aug 26 20:51:24 Daves-iMac installd[1217]: ./postflight: launchctl: Dubious file. Not of type .plist (skipping): /Library/LaunchDaemons/com.palm.novacomd
    Aug 26 20:51:24 Daves-iMac installd[1217]: ./postflight: nothing found to load
    Aug 26 20:51:24 Daves-iMac installd[1217]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “NovacomInstaller.pkg”." UserInfo=0x7fc1b312c820 {NSFilePath=./postflight, NSURL=file://localhost/var/folders/_z/nm7khw8n3wx9​9vjgf72ly_3h0000gn/T/NovacomInstaller.pkg, PKInstallPackageIdentifier=palm.novaInstaller.macn​ovainstaller.pkg, NSLocalizedDescription=An error occurred while running scripts from the package “NovacomInstaller.pkg”.} {
    NSFilePath = "./postflight";
    NSLocalizedDescription = "An error occurred while running scripts from the package \U201cNovacomInstaller.pkg\U201d.";
    NSURL = "file://localhost/var/folders/_z/nm7khw8n3wx99vjgf​72ly_3h0000gn/T/NovacomInstaller.pkg";
    PKInstallPackageIdentifier = "palm.novaInstaller.macnovainstaller.pkg";
    Aug 26 20:51:24 Daves-iMac Installer[1206]: install:didFailWithError:Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “NovacomInstaller.pkg”." UserInfo=0x7fd6241a6ed0 {NSFilePath=./postflight, NSURL=file://localhost/var/folders/_z/nm7khw8n3wx9​9vjgf72ly_3h0000gn/T/NovacomInstaller.pkg, PKInstallPackageIdentifier=palm.novaInstaller.macn​ovainstaller.pkg, NSLocalizedDescription=An error occurred while running scripts from the package “NovacomInstaller.pkg”.}
    Aug 26 20:51:25 Daves-iMac Installer[1206]: Install failed: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
    Aug 26 20:51:25 Daves-iMac Installer[1206]: IFDInstallController 22D45FC0 state = 7
    Aug 26 20:51:25 Daves-iMac Installer[1206]: Displaying 'Install Failed' UI.
    Aug 26 20:51:25 Daves-iMac Installer[1206]: 'Install Failed' UI displayed message:'The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.'.
    Don't know if this is a Lion only issue or what.  I've sent the full log to palmlevel3.  Hope this keeps someone from ripping their hair out, like I did...
    Post relates to: HP TouchPad (WiFi)

    this issue was particularly upsetting today, as my phone was at 100% last night, during the night Irene knocked our power out, and apparently something about this drained by battery to only 40% when I woke up. Luckily my laptop is charged, so I can usb charge my phone, but I had hoped to use that later in the day, not first thing in the morning.
    hopefully a resolution to this is being worked on.

Maybe you are looking for