profile doesn’t match Application Identifier

[comtek]

Hi,

Just upgraded to OS Beta 5, and my project which worked fine in V2.2.1 will not install on Ipod device. “Can’r un “Xxx” on the Ipod” error. Basically does not have provisioning profile. (currently leaving device at V2.2.1, but don’t think that is the problem)

So went into Xcode and found under “project >> Edit Project Settings >> build” settings. Under code singing identity section, the previous working code signing entries, which match the AppID are now greyed out!!!

And it Says “profile doesn’t match Application Identifier ‘xccssf.fasf.sfa.sf’

So went to ADC and downloaded profile again, after deleting it, etc. Still greyed out.

WHY??? Any ideas….

They do match…

Those guys at apple really make me smile!

[Pepper]

Hi there,
I have a similar problem. Building my app in XCode 3.1.3 I get the following error: "Sign error: The identity 'iPhone Developer: xxx' doesn't match any valid certificate/private key pair in the default keychain". It doesn't matter if I build for 2.2.1 or 3.0.

Any ideas?

Thanks
Karin

[umundoinc]

Hi,
I updated my iphone os with 3.0 from 2.2.1, but i created my new developer profile and provisioning profile, but now when i used build and go/ build and debug then i am getting error "Code Sign error: The identity 'iPhone Developer:xxxxxxx doesn't match any valid certificate/private key pair in the default keychain".
Can anyone please help me to solve this problem.





Thanks in advance
UmundoInc

[Pepper]

Originally Posted by umundoinc

Hi,
I updated my iphone os with 3.0 from 2.2.1, but i created my new developer profile and provisioning profile, but now when i used build and go/ build and debug then i am getting error "Code Sign error: The identity 'iPhone Developer:xxxxxxx doesn't match any valid certificate/private key pair in the default keychain".
Can anyone please help me to solve this problem.

Thanks in advance
UmundoInc

Check your certificates in keychain. I my case the certificates was gone invalid, so xCode can't find a valid certificate.

[comtek]

Still not got anywhere with this. Just deleted my developer certificate from the key chain thing. And reinstalled. Still all grayed out!!!

Their must be some files I could delete, and reinstall to get the correct entries somewhere...?

[comtek]

Here's another strange thing after the upgrade. Xcode keeps installing and starting a VERY old copy of the app in the simulator!!

If I reboot Xcode all is well again. VERY STRANGE did not do this before, and cannot understand how it uses such and copy copy. My be my only bet is to format the hard disk. Thought this kind of thing never happened on MAC...s

[Pepper]

Originally Posted by comtek

Still not got anywhere with this. Just deleted my developer certificate from the key chain thing. And reinstalled. Still all grayed out!!!

Their must be some files I could delete, and reinstall to get the correct entries somewhere...?

If you open keychain and click on your certificate, does it say that the certificate is valid or invalid?

[kilobytedump]

Originally Posted by Pepper

If you open keychain and click on your certificate, does it say that the certificate is valid or invalid?

Aha....

Nice one Sherlock. Just had this problem and cert was indeed invalid.

Needed to create a new one online and bingo..up and running.

Ta.

[comtek]

My developer certificate is valid... But I cannot see any other certificates for each app.

[comtek]

Just tried to create a new App ID and Profile for testing on IPod. The new certificate appeared in the list, within Xcode build settings, but grayed out!

Saying "profile does not match Application Identifier ..." but it does... everything should be OK Man this is driving me MAD

[Pepper]

Originally Posted by comtek

Just tried to create a new App ID and Profile for testing on IPod. The new certificate appeared in the list, within Xcode build settings, but grayed out!

Saying "profile does not match Application Identifier ..." but it does... everything should be OK Man this is driving me MAD

If you create a new certificate you also have to create an new provisioning profile with this certificate. Then you have to remove the old provisioning profile from you test device and from Home/Library/MobieDevice/Provisioning Profiles/. Copy the new one on the device and into Home/Library/MobieDevice/Provisioning Profiles/ and restart xCode again. Now try again.

[comtek]

Are yes a good try.... Deleted all profiles. Create new ones and downloaded for one specific AppID. Now at least I only have ONE grayed out option which does not make sense.

Also Organiser has now decided to say "Could not support development" on IPod! but that is another issue. I cannot understand why I'm getting so many illogical errors. The coding was the easy bit!

[comtek]

Just tried a * wild card app ID and it works!!!

I guess they have made the list gray out id the App ID is invlaid. Which is good, but I cannot see anything wrong with App ID which was in the Bundle ID. And they worked before!!!

Think will give 24 hrs and try the AppID again

[tvalleau]

Faced with this too. If I choose Project Info, I'm able to set the Code signing without any trouble. If I choose target, I get "profile doesn't match Application Identifier" in the popup.

I'd sure love some clues on why it's OK in one place, but not the other...

[comtek]

I ran up an old backup in a different location, and it works. Nearly fell of the chair!!!

The profiles are still gray, but it had selected "Iphone Developer", which I'm sure was not an option on previous version of XCode.

But then again the wind was very low at the time. Blowing in from the North east.

[joni]

After updating to iPhone OS 3.0 beta 5 (from beta 4) I could not build anything, it says:

"Code Sign error: The identity 'iPhone Developer' doesn't match any valid certificate/private key pair in the default keychain"

And in the Organizer it says:

"A valid signing identity matching this profile could not be found in your keychain."

So then I tried creating a new provisioning profile, which didn't help. I tried reinstalling the developer certificates, no joy.

I then tried creating new developer certificates, but the Keychain Access app stalled forever while finalizing the request.

Then I tried to move the certificates and private and public keys from the login chain to the system chain using drag and drop, but this caused my keys to disappear entirely! They left the login chain but never made it to the system chain!

Now I'm looking at having to restore my entire system from a Time Machine backup I did earlier today and starting over

[tvalleau]

Well, here's what worked for me: turned out that the project file was messed up. (I'd attribute this to myself, but I'm not so sure now. I've been testing it for a while, and ... well... just check this out and see if it's happening with you too.)

The project file is a package, including project.pbxproj. At the end of that file is where you'll find the provisions listed. Compare those -names and numbers- to those in ~/Library/mobiledevice/provisioning profiles. (You'll have to open the profiles to see which is which.)

What I found was that they were mis-matched. in some cases the ones labeled distribution had debug provisions listed, or some other mismatch.

I just replaced the incorrect names and numbers with the correct ones, and things worked fine for me.

I'm going to submit this as a bug to Apple, once I'm positive it's not me fumbling around.

OH... and make a copy of your project file before you go hacking around in it.

This could just be me, but if it's true for you too, will you please post back here?

Good luck!

[comtek]

Originally Posted by tvalleau

What I found was that they were mis-matched. in some cases the ones labeled distribution had debug provisions listed, or some other mismatch.

I just replaced the incorrect names and numbers with the correct ones, and things worked fine for me.

Good luck!

Sorry forgive me, but how did you edit the file... I tried to open it in textpad, but failed... I presume it is in XML.

[tvalleau]

Originally Posted by comtek

Sorry forgive me, but how did you edit the file... I tried to open it in textpad, but failed... I presume it is in XML.

XML is just text, so anything should edit it. I think I used TextMate, but even TextEdit should work.

[comtek]

Sorry did't understand the package bit... Are at least you can see whats happening...

I think in the morning I may set up a new project, then copy all files into it (which are many) then start from scratch... Will post out come... Off down pub to drown sorrows.

Thanks for all help

[tvalleau]

Originally Posted by comtek

Sorry did't understand the package bit... Are at least you can see whats happening...

Ahh... a true newbie. :-) On the Mac many things, (including applications) are in fact just folders of many files, cleverly disguised as a "package." The way you got to see their contents is to control click on them, and then choose "show contents" from the resulting menu.

If you do that with your project file/package, you'll find three files inside, including the one I mentioned.

Good luck!

[Sjakelien]

I went through the whole procedure of getting a new certificate etc, but that didn't help.
After lots of other experiments, I took a look in my ~/Library/MobileDevice/Provisioning Profiles/ and noticed that my most recently generated profile was just not sitting there. I then manually copied it in there, selected it in the build tab of my target properties, and it all starte to work again.
I hope this helps some of you out.

[joni]

Originally Posted by tvalleau

Well, here's what worked for me: turned out that the project file was messed up. (I'd attribute this to myself, but I'm not so sure now. I've been testing it for a while, and ... well... just check this out and see if it's happening with you too.)

I tried creating a new project but that had the same problem. Also the Organizer error is independent of any project anyway.

So today I restored my entire system using Time Machine back to before I installed beta 5, and I still have the same problem! But beta 4 used to work for me, so this is odd. Right before I upgraded I was getting a problem where both my ipod and iphone wouldn't be recognized by xcode or iTunes, so maybe this is related.

This is so frustrating! I can't work at all right now, except in the simulator, which is no good for what I'm doing. No reply yet from Apple. I will try yet again to create completely new keys, certificate, and signing identity...

[joni]

There were so many steps, I'm not sure I remember them all, but here are the parts I do remember, in case this helps anybody:

- I had two "System" keychains, so I deleted one of them
- I set the "login" keychain to be the default, so that new keys would be added there (it should show up bold when it's the default)
- deleted the old public and private keys for my developer identity, and the wwdr and iphone developer certificates (in both the login and system keychains)
- quit keychain access and restarted it
- generated completely new keys, certificates, app id, provisioning profile
- made sure everything got added to the login keychain, not the system keychain
- in xcode deleted the old provisioning profiles from the Organizer and the device
- added the new profile to xcode and the device
- updated the info.plist (since I'd changed the com.yourcompany part of the app id in the new profile)

After verifying it worked with beta 4, I upgraded again to beta 5, did a clean rebuild, and everything still works fine.

[husoft]

I had the same problem as joni

"A valid signing identity matching this profile could not be found in your keychain."

Solved it with just this step:

in Keychain Access right clicked "login" keychain and set it to default.

Restarted Xcode and all is good again. Have no idea what caused the problem.