Problem with Command Line Installs

Sorry if this is an idiotic response but just throwing it out there. Could you not use composer, do your install on the system, and then create a pkg from that, and then deploy it that way, rather than command line?

For giggles things I would try would be if in domain, take out and try install. Or try in safemode boot? That's just based on googling.

As you are getting an Authorization error I am guessing your command is not being run via sudo or with root privileges.

nm... I missed the uid=0 euid=0 line. File permissions maybe?

How long has the Xcode.app been on the system in question? New install or was it deployed some time ago?
Although I'm nearly certain command line installer would report it correctly, I'm wondering if you're running into some kind of expired/bad certificate issue. You could try throwing in the -allowUntrusted flag to the command to see what happens. Not very confident that's the issue, but its always worth a try during troubleshooting.

This is a fresh install of xcode. The purpose of the command line installs is to prevent the prompt that happens when you launch for the first time. The install command does not work from a root shell either. We are in an active directory environment, I will try on an unbound / stock machine for giggles. Someone else produces our system images so I am not sure exactly what changes have been made during that process. I dug around in /etc/authorization but honestly couldn't figure much of it out.

The reason I want to figure out the cause is that I had this same error earlier in the week trying to install a cs6 pkg through casper.

Do you need to install MobileDevice.pkg first? We have an Xcode 4.6.2 package which is working right now. Postinstall script runs: /usr/sbin/installer -package /Applications/Xcode.app/Contents/Resources/Packages/MobileDevice.pkg -target /
Then installs the MobileDeviceDevelopment.pkg with basically the same command.

Another item to verify is GateKeeper, make sure its not set to App Store only.

I have discovered a bit more here: gatekeeper is not set to app store only via policy.
My command line installs work fine on Snow Leopard, fail miserably on Lion and Mountain Lion. It doesn't matter
what pkg I am trying to install, I get the same thing when going through command line.

What OS is the system you are on?
pre 10.7.5 and 10.8.2 systems cannot install packages that have been signed after the new keys were generated.

Ok just did some more tests, it is only workstations that are bound to AD that are failing. I wish I understood /etc/authorization .

Its only Lion and Mountain Lion systems that are bound to AD. Grumble.