Benches macOS

14

.app file not installing in Applications folder | Official Apple Support Communities

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Hi. I have created a package installer using Xcode's PackageMaker. I want to install a .app file into the applications folder, but when i am running installer package, it's showing that the software is installed succesfully. When i checked the applications folder, the application i m installing is not there. Can anybody help me to solve this?

14 replies

Sign in or join Beachball Help to reply.

  1. 0

    etresoft

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    shaktirsg wrote:
    Can anybody help me to solve this?

    Not without more details. PackageMaker is just quirky, cantankerous, and downright buggy. There is no good answer for it. You just have to play around with it. There is no easy solution. Start simple - really simple. Create a single text file and play around with installing it. Then move up to a full application. Be very careful with setting all of those "interesting" PackageMaker options. Some of them are incompatible or just plain don't work. Did I mention starting simple?

  2. 0

    Lewis Francis

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I'm having the same problem, ever figure it out?

    I suspect the installer "thinks" that the app is already there and silently skips that part of the install. I can't figure out how OS X keeps track of installed apps and whether or not a given app is flagged as downgradable; shouldn't be this difficult...

  3. 0

    etresoft

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Lewis Francis wrote:
    I'm having the same problem, ever figure it out?

    How do you know? The original poster never explained it.

    I suspect the installer "thinks" that the app is already there and silently skips that part of the install. I can't figure out how OS X keeps track of installed apps and whether or not a given app is flagged as downgradable; shouldn't be this difficult...

    Take a look in /Library/Receipts

  4. 0

    Lewis Francis

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    How do you know? The original poster never explained it.

    Thanks etresoft, well, it sure seems like we're having the same problem.

    For instance, while I can install to /Applications/killme successfully, changing the destination path back to /Applications fails to work though the installer claims success; Console messaging doesn't appear to be any different for either working or non-working test.

    Take a look in /Library/Receipts

    First place I looked, didn't see anything. Perhaps my original installers from 2006 didn't leave receipts?

  5. 0

    Lewis Francis

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Oh good grief, I realized I could look at the more detailed install.log and am now really confused -- the same installer, pointed at /Applications, seems to be installing at varying places in the system:

    Applications/MacNikto.app relocated to Users/lfrancis/MacNikto 1.1/build/MacNikto.app

    Applications/MacNikto.app relocated to Users/Shared/from lfrancis/MacNiktu/build/Deployment/MacNikto.app

    Applications/MacNikto.app relocated to Users/Shared/from lfrancis/MacNiktu 2.15.2007/build/Deployment/MacNikto.app

    As soon as I remove the installed version from the unexpected location that the app has been "relocated" to, it finds another spot.

    ***?

  6. 0

    Lewis Francis

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Wow, PackageMaker really is buggy.

    I disabled Custom location and allow relocation, and that seems to have stopped the pseudo-random install destinations.

    However, my now working installer fails when placed in a meta installer.

    Angst.

    This has always been a breeze up to the last time I did this in 2008... whats changed? Sigh.

  7. 0

    Lewis Francis

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I've given up. Using PackageMaker 3.0.4, I can create a standalone installer for my app and have it installed in /Applications, but I can't get it to work when inside a meta installer.

    So... [super-ugly-hack-warning] I've taken an older meta installer and replaced its old packages with my new packages, edited the plist to update filenames, and voila.

    Really disappointing that I have to resort to such hackery, but life is short. That said, any gotchas I might run into using such an ugly hack?

    Thanks much.

  8. 0

    etresoft

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    PackageMaker is certainly buggy, but it will work. You just have to learn how it is supposed to work and do not deviate from that.

    In particular, keep the following in mind:
    1) Keep default settings. Change them only one at a time and test. Change them only if you have very good reason to.
    2) Don't turn on too many options. Most PackageMaker options only work in very specific situations.
    3) Items to install into non-user locations must be owned by root and have all their permissions set before you add them into PackageMaker. I use a script to copy my items to a temp location and then do chown on them (via sudo, of couse).
    4) Don't get fancy with the install location. Are you installing an application? It is "/Applications". Are you installing an application and some app support files, your root is "/".
    5) Keep your root in mind when adding items into PackageMaker. They will be installed relative to root. PackageMaker is not smart.
    6) Create a package with some text files and try installing them first to just get the feel of it.

  9. 0

    Lewis Francis

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks for the tips. I really don't recall having any trouble the last time I did this, admittedly several years ago. I suspect the weird shuffling of actual install destinations was due to the Relocatable flag, the purpose of which I apparently do not understand. Doc is surprisingly and disappointingly light on this.

    No clue why the meta installer didn't work -- both packages bundled in the meta work as stand-alones, but only one worked in the meta.

    Hope I'm done with this for a while...

  10. 0

    fyysh

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi,

    I was having the same issue. The Installer reported successfull installation, but the app was not placed in /Applications.

    The problem was that i forgot to check the "Include root in package" check box in the Contents tab of the component.

    After checking that checkbox it worked fine. Even with relocation.

    Greetz
    Alex

  11. 0

    robiwano

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I have a similar issue. I have a PM installation which installed my .app nicely into /Applications. Then suddenly it stopped. I didn't do anything to the package containing the .app. Now I can't get it to work again. PM buggy ? Kind of...

  12. 0

    ncraike

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I'm also having this problem with Package Maker (3.0.4, in Mac OS X 10.6) but I think I've discovered the solution.

    First, when you test the installer, open the "Installer Log" window (select "Installer Log" from the Window menu, or press command+L). Then, proceed with the installation as normal, and check the Installation Log window once you reach the end of the installer. You should see a message in the logs which is something like:

    Dec 16 15:48:57 yourhostname installd[16558]: correct/path/Applications/YourApp.app relocated to incorrect/path/Applications/YourApp.app

    In my case the relocated path was actually build/Debug/MyApp.app inside my Xcode project directory.

    The cause for this is, I think, a slightly hidden option in Package Maker. Under the Components tab in Package Maker (with your app selected in the left-hand "Contents" pane), select your app from the list of components, and click the "Relocation..." button in the bottom-right of the window.

    This should open up a modal dialog with a list of options titled "Finding Component to Upgrade". The default option Package Maker seems to insert is "Combination search for <your app's identifier>". Under the configuration for this option, there is the description "Will succeed if an application is found at the specified path, by LaunchServices or by doing an exhaustive search".

    From what I can tell, these options configure the installer to search the system for an existing version of the app to upgrade. If an existing version is found, the installer tries to replace it, in the location the existing app is in, rather than installing the app in the location you may have configured in Package Maker.

    The search uses the application identifier string (eg "com.yourcompany.yourapp"), so it may find any version of your app just about anywhere on your system. In my case, I think, the installer is actually finding the copy of my app in my Xcode project's build directory, and trying to upgrade/replace that version.

    The solution may be:

    a) clean out all your build directories, and remove any other versions of the app you may have on your system, after you've built your installer with Package Maker and before you actually test the installer (you'll need a copy of your app to build the installer). If I do this with my build directories, the app is installed to the expected location.

    b) change the "Relocation..." options for your components in Package Maker to not use Combination Search or Exhaustive Search. Instead use one of the other options, such as "Check Specific Path" (only upgrade existing versions if they're in an expected location like /Applications/yourapp.app). Exhaustive Search may be suitable if you include and exclude specific directories.

    Read through the different options available and decide what's best for your app. You may like to use different options during development, as upgrading existing versions may be useful functionality for the end user of your app.

  13. 0

    bishopthom

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    had the same issue.... installer completed just fine, log shows .app file being relocated....

     

    ended up having to delete the /Users/<youname>/Library/Developer/Xcode/DerivedData/<your project-xxxblahblahblahxxxxxx> directory.  re-opening xcode 4, cleaning, re-archiving and building new package from organizer seemed to do the trick.

     

    since i had to sudo rm -rf the directory, i suspect that there was a file in the cache that xcode couldn't overwrite, but i don't know that for certain. its possible that the 'Installation Directory' option in the projects build settings couldn't be properly applied.

     

    too bad there is no warning that this problem exists. i'm glad that i didn't send this package out to any of my customers.  yet another reason why testing your apps all the way through installation is always a good idea.

     

    -t

  14. 0

    seapple

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks for your thorough explanation, I followed it and understood what didn't work with

    my packagemaker script.

     

    This software needs some better user feedback and guidance, for sure,

    but it's cool to see someone took the time to explain a real solution.

     

    Often, it feels this forum has some people trying to max out their 'points' score, rather than actually help.

     

    Thanks again!