iOS代码签名错误

Question

I'm trying to install and run a basic iOS application on my iPhone. The error I am getting when I try to build and install is:

CodeSign /Users/jacob/Library/Developer/Xcode/DerivedData/newProject-bttbyexujwyetreshrllqrqmpouw/Build/Products/Debug-iphoneos/newProject.app
cd /Users/jacob/code/iphone/newProject
setenv PATH "/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/opt/local/bin:/usr/local/git/bin"
setenv _CODESIGN_ALLOCATE_ /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/codesign_allocate
/usr/bin/codesign -f -s "iPhone Developer: Jacob LYLES (P4AAK856G5)" --resource-rules=/Users/jacob/Library/Developer/Xcode/DerivedData/newProject-bttbyexujwyetreshrllqrqmpouw/Build/Products/Debug-iphoneos/newProject.app/ResourceRules.plist --entitlements /Users/jacob/Library/Developer/Xcode/DerivedData/newProject-bttbyexujwyetreshrllqrqmpouw/Build/Intermediates/newProject.build/Debug-iphoneos/newProject.build/newProject.xcent /Users/jacob/Library/Developer/Xcode/DerivedData/newProject-bttbyexujwyetreshrllqrqmpouw/Build/Products/Debug-iphoneos/newProject.app

/Users/jacob/Library/Developer/Xcode/DerivedData/newProject-bttbyexujwyetreshrllqrqmpouw/Build/Products/Debug-iphoneos/newProject.app: The operation was cancelled by the user.
Command /usr/bin/codesign failed with exit code 1

I've deleted and redownloaded all my provisioning profiles and certificates and whatnot a million times. Any help is much appreciated. I can provide more information as needed. I am using iOS 4.3 SDK on XCode 4.0.

edit: Please keep in mind that the project compiles, installs, and runs perfectly on the simulator where no code signing is needed.

Answer 1

请在info.plist中检查您的捆绑包标识符，如果还正确，请重新启动设备和机器，然后进行构建，并选择正确版本的SDK，它可能会起作用。

Answer 2

I had been having this problem each time I change to a new computer, this is my solution:

1. Go to your keychain Access, under Login | Certificates and delete those certificates.
2. Login on developer.apple.com
3. Go to Provisioning Portal.
4. Go to Certificates and REVOKE your profile.
5. Create a new one (using the guide on site).
6. Download and Open your new Certificate.
7. Download and Install your Provisioning Profile.
8. Go to Xcode, Clean and Build.
9. Assign your certificates to the code sign in sections again...

And voila! That's it!

Answer 3

Have you checked your deployment target? Alot of people confuse the term Base SDK strangely represents the highest version of OS your app will run on, therefor, the lower it is, the greater the chances of compatibility are.

Answer 4

Use your provisioning profile for build. set it in info of project as well as in target (get info + build tab + code signing identity)and also set bundle identifier in yourApp-Info.pList.

Answer 5

Had some rather incomprehensible problems with CodeSign in Xcode 4 today. The problem started when I installed Xcode 4.2 beta to try and resolve some iOS 5.0 issues with my apps. I ended up uninstalling it and going back to Xcode 4.1 and thats when my problems started. I got the following error when building my apps:

... object file format invalid or unsuitable
Command /usr/bin/codesign failed with exit code 1

I tried everything, re-downloading certificates, provisioning profiles, code signing build settings, the lot. Nothing seemed to help. A lot of googling revealed no definitive answer.

In the end it turned out to be something quite obscure. There is supposed to be a symlink /usr/bin/codesign_allocate . It must have been deleted during an uninstall. So I ran the following to recreate it:

sudo ln -s /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/codesign_allocate /usr/bin

Xcode, clean and build and everything was fine.

Hope this information proves useful and saves you time.

Answer 6

Another thing that causes this error is changing your login keychain password. Maybe you work at a place that forces you to change your password every so often. Next time you do so, you could possibly start getting this error. Simply logging out then back in will fix it.