You do not have the required file permissions

We exchange project files over a shared git repo on remote server and somehow I just lost write access to some files:

Error cleaning build folder

You do not have the required file permissions

Application Failed Codesign Verification

Submission to App Store wasn't as easy as I thought in previous blog. Not really surprised, but this problem was tough to solve. Not tough as in hard to fix, but as hard to figure out:

Application failed codesign verification.  The signature was invalid, or it was not signed with an Apple submission certificate. (-19011)

How to Clear Project Build Results

You have a project with several targets, of which at least one fails. You can see this at Xcode4 iTunes-styled toolbar info window at top.

Except that The Target that you just build was just fine. No warnings, no errors. Xcode4 still tells something went wrong!

How to Control Which iPhone Simulator Starts

Been debugging application, verified several fixes were ok in simulator. Installed application on real device, just to find out bugs were still there!

What's going on?

How to Update CFBundleVersion Before Building Application

Used to update application version number in appDelegate.m during startup. The problem was that user has to run the application at least once to update version number in system Settings application.

Before that moment version number was either missing or wrong, depending on what the default value was. Not good.

Xcode 3.2.5 Base SDK Missing

Downloaded Xcode 3.2.5 and iOS SDK 4.2, installed and opened an old project. Got error note Base SDK Missing, as expected. Nothing to worry about!

Select project, press Command-i to view project info, find Build - Architectures - Base SDK and select the new "Latest iOS (currently set to iOS 4.2)". Close info - and nothing happens!

Select Targets and your application, press Command-i to view target info. You might have overwritten default project settings by mistake earlier. Check what is Build - Architectures - Base SDK. Should be same as you just defined for project. Close info - and nothing happens!

Close Xcode, reopen your project - and Base SDK is set! Didn't really expect this kind of new features with the update...

Update: No need to close Xcode, just toggle some settings via "Overview" popup at top left corner. For example change "Active Configuration" to Release and back to Debug. Usually that's enough, though sometimes target device has changed, too. Verify all "Overview" selections after you've done this.

Everything That Can Go Wrong With Xcode Build and Release

Right now I'm in the middle of serious mess up of my Xcode development environment, can't create ad hoc builds. No idea what triggered it, thus no idea what or how to fix. Since same error notes keep popping up time after time, I start documenting each. Maybe I'll slowly gather enough info to fix something.

Xcode error notes:

• The executable was signed with invalid entitlements (Xcode)
• The executable was signed with invalid entitlements (install) OPEN
• Command /usr/bin/codesign failed with exit code 1
• Build & Archive - Share Application - nothing happens
• Build & Archive - Share Application - unable to find user OPEN
  
• Build & Archive - Share Application - Email - missing plugin OPEN
  
• Team Provisioning Profile - Invalid. Renew button disabled.
• Code Sign error: The identity 'iPhone Developer' doesn't match any identity in any profile
• Code Sign error: Provisioning profile can't be found

Useful articles:

• Apple Technical Note TN2242: Resolving "0xE800003A", applications not launching and "missing entitlement"
• Cocoanetics: A signing identity matching this profile could not be found in your keychain
  

Useful sites:

• Apple Developer Forums
• Stack overflow

Have patience, try again, just keep bumbing your head into wall, no pain no gain, good luck, it works for me, wave the rubber chicken above monitor... yep, I know: none of it helps.

You have sympathy. It won't help either.

Build & Archive - Share Application - CSSMERR_TP_NOT_TRUSTED

Build & Archive - Share Application and both Email and Save fail without any visible error note. You seem to have been simply ignored. Try again to be totally ignored.

Possible error notes you can find from Console application - Databases searches - Console Messages:

•     Command /usr/bin/codesign failed with exit code 1
•     CSSMERR_TP_NOT_TRUSTED

Open Keychain Access, go to "login" keychain "Certificates" catogory. Open each development related certificate (Apple WorldWide Developer Relations Certification Authority, iPhone Developer, iPhone Distribution) and make sure their Trust details are "Use System Defaults". 

How to Solve Ad Hoc release "value not permitted by a provisioning profile"

Ever since I submitted an application to App Store I've had lots of problems creating Ad Hoc release. Though first fix was simple, it's not a complete solution.

Error messages are:

Thu Jul 22 11:46:34 jouni-iDevice installd[643] : entitlement 'keychain-access-groups' has value not permitted by a provisioning profile

Thu Jul 22 11:46:34 jouni-iDevice installd[643] : entitlement 'application-identifier' has value not permitted by a provisioning profile
...
Thu Jul 22 11:47:06 jouni-iDevice SpringBoard[28] : Application 'Zattr' exited abnormally with signal 11: Segmentation fault

This time the solution was found in TUAW article "devsugar: A better way to share ad-hoc builds".

Summary: instead of normal Build use Build and Archive, find your application, find the last date, press Share Application button and - The Critical Phase - verify your identity is your Ad Hoc Distribution Provisioning Profile. Save locally and install e.g. via iPhone Configuration Utility.

...suspect Ad Hoc release problem is caused by having two different provisioning profile files using same application id. I generate three applications (development, release test, public) from same sources with some compile time flags and different provisioning profiles and app ids. Guess code signing identities got mixed.

Entitlement 'keychain-access-groups' has value not permitted by a provisioning profile

You build and install application you are developing and fail with a flash without any obvious error note. Using iPhone Configuration Utility you're device's Console contain something like this:

Fri Jul 2 10:26:23 jouni-iDevice installd[6313] : entitlement 'keychain-access-groups' has value not permitted by a provisioning profile
Fri Jul 2 10:26:23 jouni-iDevice installd[6313] : entitlement 'application-identifier' has value not permitted by a provisioning profile

The reason is that you have previously installed your application from App Store and overwriting app binary with a developer version is not enough.

Quick fix is to delete the application from device, then build and install again.

Another reason for "Undefined symbols referenced from"

Failed to add a static library into my iPhone application. Doing everything I've done earlier, searching for new tips on internet, recreating static library project dozens of times - and still:

Undefined symbols:
"_xmlDocSetRootElement", referenced from:
+[CXMLNode(CXMLNode_CreationExtensions) documentWithRootElement:] in libTouchXML.a
ld: symbol(s) not found
collect2: ld returned 1 exit status

Finally found out that even though my version of TouchXML links to dynamic libxml2, I need to link libxml2 with application, too! Expected that once would be enough. Now wondering whether it really will be linked twice.

Unexpected File Type 'wrapper.pb-project' in Frameworks & Libraries build phase

This is a XCode project dependency analysis warning and most likely means your project is missing something you expected to be there. There are similar warning notes for both build and link phases. More info at "Xcode's Plugin Interface".

warning: skipping file '/Users/jounimiettunen/svn_iphone/project/trunk/protobuf/ProtocolBuffers.xcodeproj' (unexpected file type 'wrapper.pb-project' in Frameworks & Libraries build phase)

It means that building or linking something failed, in this case ProtocolBuffers static library. Possible reasons are missing "Linked Libraries" and/or "Direct Dependencies" definitions or that building those failed.

Possible Fix: make sure your target (Info - General) has correct setup. If you're using Apple SDK 4.0 add -ObjC into "Other Linker Flags" and also -all_load to force loading of everything. Make sure you do this for both project and target. More info at Mac OS X Reference Library "Technical Q&A QA1490": Building Objective-C static libraries with categories.