Getting “A valid signing identity matching this pr

Question

I hope to test my app on iPod Touch

I created development provisioning profile.

I dragged downloaded .mobileprovision file to Organizer

There is a yellow triangle warned that "A valid signing identity matching this profile could not be found in your keychain"

The others distribution provisioning profiles have no any problem.

I checked my connected iPod Touch. Organizer also said that:

OS Installed on "interdev"'s iPod 3.1.3 (7E18)

Xcode Supported iPhone OS Versions

• 3.1.1 (7C146)
• 3.1.1 (7C145)
• 3.1 (7C144)
• 3.0.1 (7A400)
• 3.0
• 2.2.1
• 2.2
• 2.1.1
• 2.1
• 2.0.2 (5C1)
• 2.0.1 (5B108)
• 2.0 (5A347)
• 2.0 (5A345)

iOS 3.1.3

Xcode 3.1

Do I need to upgrade Xcode?

Answer 1

If you know (for sure) that your key/pair and provisioning profiles are installed properly but you're STILL getting the infamous error, this simple solution worked for me (for good measure, clean your target first).

Go into build settings and locate the code signing area. If it's not already selected, choose the profile type in the "Automatic Profile Selector" section at the top. Try toggling between direct selecting and the automatic profile selector if it was already there.

Worked for me!

Answer 2

For the iOS Provisioning Profile error -

Valid signing identity not found

see Apple's published steps to resolve this problem, titled What does 'Valid Signing Identity Not Found' mean and how do I resolve it?.

Answer 3

I had a working iPad provisioning profile installed with XCode 4, then added an iPhone and found that the newly downloaded provisioning profile wouldn't work with either device. Checking the certificate and the link in the keychain did not help for me.

Turns out that after re-adding my certificates, and trying to close and reopen xcode, I needed a reboot before I could add the provisioning profile back into xcode and make it happy. Perhaps there is some underlying problem about needing to refresh values cached by keychain in RAM?

It is possible it may have worked by just logging out and logging back in too.