40

I updated my provisioning profile to include some more devices for Ad-Hoc testing,I added this new profile and removed the old and now I am getting this error:

Code Sign error: Provisioning profile 'Floors2Go' specifies the Application Identifier 'com.reapptive.Floors2Go' which doesn't match the current setting 'com.reapptive.Floors2Go'

Which if you look they are both exactly the same, I have removed, re-added a new profile, deleted and re-entered the bundle name in my plist and for the life of me I cant figure this out.

I have also tried cleaning all and rebuild but to no avail.

Any ideas?

Minakshi
  • 1,437
  • 1
  • 11
  • 19
Jonny Heald
  • 849
  • 7
  • 11

7 Answers7

42

Seems to be a bug in Xcode GM Seed, I had to kill Xcode and reopen it every time I change a profile.

ssedano
  • 8,322
  • 9
  • 60
  • 98
Jonny Heald
  • 849
  • 7
  • 11
  • 18
    I had to Clean, remove the profile, set everything to "Don't code sign," relaunch Xcode and re-add the profile and set code signing again before it worked. Probably not all necessary, but I'll treat it like voodoo until I know what the specific steps are. – Tim R. Oct 16 '12 at 07:17
  • 1
    Same here, still buggy with XCode 4.5.1. – gilm Oct 21 '12 at 15:14
  • 1
    I had to double check and reassign all my Debug & Release Code Signing Identities (between my Project-level settings and my Target-level settings). One of the profiles I had added a device to was stale, but still somehow associated with the Release setting. – Ben Kreeger Oct 24 '12 at 18:49
  • @TimR. your solutions seems to be working.. Atleast to me killing xcode doesn't worked for me. – Krishnabhadra Nov 30 '12 at 05:22
  • Still buggy on 4.6.1. This provisioning adventure has gone on way to long – Mark Molina Mar 26 '13 at 14:08
  • 3
    and on 4.6.2. I'm sick of this. – Adam Waite Jun 05 '13 at 16:07
19

I also had this problem while trying to replace a dev provisioning profile with an updated version. Looks like a bug.

Running XCode clean, then setting the code signing identity (for dev, in my case) to "don't code sign", then setting the code sign identity back to the relevant development provisioning profile resolved the build error.

dtgallant
  • 311
  • 1
  • 4
7

In Xcode (I am using 4.5.2) > Build Settings > Code Signing section:

  1. Change everything to Don't Code Sign
  2. Change individual setting to appropriate developer/distribution profiles.

For example:

enter image description here

ohho
  • 50,879
  • 75
  • 256
  • 383
1

In my case, deleting a duplicate and invalid certificate in keychain fixed this problem..

torutoru
  • 131
  • 1
  • 5
0

It should be problem with the Application Identifier in the plist file.Check that. Did you install the new Provisioning Profile?

SRI
  • 1,514
  • 21
  • 39
  • hi, i have checked the application identifier and it is correct and yes i installed the new provisioning profile but still nothing. what i dont understand is they are both the same when it is showing me the error – Jonny Heald Sep 13 '12 at 12:29
  • ok cool check the codesign identity in the project and targets individually. Check for debug,release also in the code sign identity – SRI Sep 13 '12 at 12:31
0
  • 1- Clean (Product --> Clean)
  • 2- Remove Prov. Profile (Window --> Organizer ) remove unused and expired prov. profile
  • 3- Set everything to dont code sign in your project and target (press on your project under build settings under code sign set everything to dont code sign and do it again on you target)
  • 4- Relaunch Xcode
  • 5- Re-add prov. profile
  • 6- Go to code sign again and set them to your prov. profile.
  • 7- Do step 6 again for code sign in your target. If it didnt work try to make the next step
  • 8- Any iOS SDK under debug set it to iPhone or iPad developer under automatic profile selector.
Robert
  • 5,278
  • 43
  • 65
  • 115
0
  1. Remove all Prov. Profile from Organizer
  2. From Menu Select Editor -> Refresh From Developer Center
  3. Enter your apple id and password and wait
  4. Go to Buit Settings of App select development profile for debug and ad-Hoc profile for release

Note It is Advice to create two different profile for development and testing

  • For Development - > Create Development Profile -> Use
  • For Distribution -> Create Ad Hoc Profile
Kirit Vaghela
  • 12,572
  • 4
  • 76
  • 80