site_archiver@lists.apple.com Delivered-To: Installer-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=ywBjEgJQY3Wc0LVbvrqmCA3KoKXMj8+4lgAATh2H/HM=; b=qcbO9EIKtwQCXAOeocVP15SSOx5840O41esx4Ix7sMCwbbpIw9gFZRT3olpQodd8xB 1jSW9ZuWChrJwECkAw/AFWBKSnhOXGL2M2QHN86TYezeVRcRl3z0GsbbP54AlB8eEImI WDZzOU2eyRj1nZIACCes0rkVoq0U7oMQT4Pik= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=nXeKyxU+J52mwewE0tk3EGvgQQELTL0cZICFuA231U+R51//sgnntLnz64ixpfgIMn Rm0N1gn+kcnfGRtjgOF9vMlENbGwgG6asdhD5TWg+0+UNPxPLzBpdJTICdCzr75q1Jza D44rwjuzHnn61lHxOxrhPXooFQx8Rsw6bNOYE= On Thu, Mar 31, 2011 at 5:30 PM, Andy O'Meara <andrew.omeara@soundspectrum.com> wrote:
Hey everyone,
I've been trying to get insight into what appears to be an inane bug either within the OS X package installer or the Finder.
We use a build script that builds all our .bundles and .apps and then calls package maker via the command line to make our .pkg. Our package creates a new dir in the Applications dir (if it doesn't already exist), and expands the .app into this directory. What's happening is that after the installer runs our package, our .app fails to load our bundle. Yet if I run the .app that the package was given (ie. if I run the app before it gets sucked into the pkg), the app runs fine -- it's as if somehow the .app created by the installer is somehow not right.
Hi Andy, Not sure I follow what you mean by the app failing to load the bundle, but it could be that launchservices is not properly registering the app. I've seen this behavior when installing apps into a subdirectory of /Applications. I've been able to fix it by dropping a symlink in /Applications, or even simply navigating to the parent directory of the app itself and launching it from there. But it sounds like even that's not working for you. Also, since you can get it to work by launching the App before packaging it, have you tried trapping for what changes when you launch it on your build machine? Sounds like this problem exists even before it's being packaged. If I were you, I'd reduce the complexity of your package to its simplest state. Package just your App (after triple-checking the permissions) to install only into /Applications. Does that work? Include your pre-install script. Does that work? Add the subdirectory. Etc, etc. Perhaps this process will lay bare the problem. Best regards, --joe _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com