I am trying to archive an app in Xcode 4.4 and I receive an error that says "Package Operation Failed". This is the first app I am trying to archive after downloading Mountain Lion. I had a hard drive crash and updated to Mountain Lion when Apple replaced the hard drive. Any suggestions of what the error could be. I have downloaded a new Source Code and tried it again. I have been getting a number of warnings that I did not have in the previous Xcode version. Erros are:"Data argument not used by format string". These are found in the following code lines of each of the Self Hosted plugins: [BT_debugger showIt:self:[NSString stringWithFormat:@"Attachment not found in cache: @", [self saveAsFileName]]];

I'm thinking there are two things going on here. 1) It's nearly impossible to know why you're getting a "package operation failed." This is very ambiguous and literally could be anything. There isn't anyway for most folks (including us) to figure out how Xcode packages apps when you use the archive function. This process is proprietary to Apple and I'm not sure how to recommend debugging it. The archiver should work, if it doesn't, could it be related to Mountain Lion? 2) Warnings: It's pretty common to see a new set of warnings, and possible errors, when OSX is updated with a major release. Oftentimes these OSX releases are updated very very quickly (a few days or a week sometimes) after getting a few million machines updated, users commenting, feedback, etc. It's this reason we don't to the "first release" of a major OSX update. We generally wait a few weeks before updating our machines. Not sure if this has anything to do with what you're experiencing but it's an important thing to understand. So...Archiver issues, not sure how to advise. Warnings, lets see if there easily fixable? You should not compile / archive if you have any warnings or errors in Xcode. It's important to figure them out and fix them. These didn't exist before Mountain Lion and the Objective C delivered with your project didn't change. So...not sure what's wrong. I don't see anything wrong with this: [BT_debugger showIt:self:[NSString stringWithFormat:@"Attachment not found in cache: @", [self saveAsFileName]]]; And, like you said, it's a super common line used in lots and lots of places throughout the project. Code like this is used to print some debugging output the console. If you want, before figuring out the OSX Mountain Lion questions, you could easily comment all of these out to see if it compiles without warnings. Heck, if it does, you could also try the archiver. Maybe the archiver won't run with compiler warnings. Not sure. We'll get the latest Mountain Lion update installed on a bunch of machines and see where it takes us sometime next week? Guessing a bit here. Lastly, if it matters, I'm guessing there are thousands of folks using buzztouch source code that have already upgraded to Mountain Lion and this is the first report of this type of behavior. My comments and idea here may be mute if there is something else wrong with your machine ;-)

Thanks for the response. I figured out my problems. I downloaded the "Command Line Tools" in the preferences tab. I then was able to begin the archive and how a few errors. The icon files were renamed with a capital "I" in the info.plist file so I had to rename the icons in the plist to a lower case "i". Thanks again.

Just to update this post for future visitors, I had this issue and resolved it by add % in front of the @ ... cache: %@ ... see below: [BT_debugger showIt:self:[NSString stringWithFormat:@"Attachment not found in cache: %@", [self saveAsFileName]]]; not exactly sure why but fixed many errors :-)