updated to 3.0, now "Provisioning profile can't be found"
Here we go again...
When I try to build to the device I get "Code Sign error: Provisioning Profile '5AG39DDX-....." can't be found.
In Organizer, the Provisioning Profile there has a Profile Identifier that is completely different from the one Xcode is trying to find, thus the problem. How do I get Xcode to look at my actual Provisioning Profile instead of looking for one of it's imaginary x-girlfriend's profiles?
man I love dealing with this every other day for hours...
When I try to build to the device I get "Code Sign error: Provisioning Profile '5AG39DDX-....." can't be found.
In Organizer, the Provisioning Profile there has a Profile Identifier that is completely different from the one Xcode is trying to find, thus the problem. How do I get Xcode to look at my actual Provisioning Profile instead of looking for one of it's imaginary x-girlfriend's profiles?
man I love dealing with this every other day for hours...
Set it to the correct one in your project properties or re-upload your old provisioning file or something.
Set it to the correct one in your project properties or re-upload your old provisioning file or something.
I'd love to, but I don't see anything that says "Provisioning Profile" when I double click the Target app and click the "Properties" tab. Can you tell me where to find this elusive Provisioning Profile field?
Yeah, the same thing happened to me after I upgraded to SDK 3.0. I had to delete my provisioning certificate and regenerate it from my dev account. You'll need to delete the old and add the new certificate to the keychain and to your iPhone. Afterwards, do a clean-all of your builds and re-build your code. It should work then.
Yeah, that would only be about the 20th time I've had to do that, and that's not an exaggeration (thanks Apple).
If I create a new test project, I can build to the device. It's just this current project that somehow is looking for an old profile. There has to be way to change that in Xcode. Where is that setting?????
I just went through the entire process again (make that 21 times now). Created all new certificates and profiles. Everything is "green" in Organizer, all keys are installed.
Xcode still says "Code Sign Error: Provisioning profile 'blah blah blah' can't be found, yet I can see one clearly in Organizer, with a shiny green circle next to it. It has a different identifier number than the one Xcode is claiming it can't find. I have cleaned. I have deleted the Build folder. I have summoned Bill Gates.
I just went through the entire process again (make that 21 times now). Created all new certificates and profiles. Everything is "green" in Organizer, all keys are installed.
Xcode still says "Code Sign Error: Provisioning profile 'blah blah blah' can't be found, yet I can see one clearly in Organizer, with a shiny green circle next to it. It has a different identifier number than the one Xcode is claiming it can't find. I have cleaned. I have deleted the Build folder. I have summoned Bill Gates.
Any more suggestions?
In your project settings, when you choose the popup for setting the provisioning profile what happens if you select 'other'? I found that I had to somewhat manually force the proper signature a few times.
But I have never, even after upgrading to SDK 3.0 and the new iPhone 3GS had to redo my developer certificate. I can't imagine why that would be necessary. But I did notice that I had several settings in XCode that were not preserved when I upgraded and that has caused me some pain.
In XCode, in the "Groups & Files" pane, expand "Targets" and double-click on your app's target.
This will bring up the Info pane for your target. In the "Build" section, check the "code signing" section for any old profiles. I found that it was building to an old profile there.
In XCode, in the "Groups & Files" pane, expand "Targets" and double-click on your app's target.
This will bring up the Info pane for your target. In the "Build" section, check the "code signing" section for any old profiles. I found that it was building to an old profile there.
Spot on for me as well so many thanks for this Csprocket777.. Everything else was good except for this vital severed part
In XCode, in the "Groups & Files" pane, expand "Targets" and double-click on your app's target.
This will bring up the Info pane for your target. In the "Build" section, check the "code signing" section for any old profiles. I found that it was building to an old profile there.
You helped me so much
I even registered to this forum just to say thanks!
In XCode, in the "Groups & Files" pane, expand "Targets" and double-click on your app's target.
This will bring up the Info pane for your target. In the "Build" section, check the "code signing" section for any old profiles. I found that it was building to an old profile there.
In XCode, in the "Groups & Files" pane, expand "Targets" and double-click on your app's target.
This will bring up the Info pane for your target. In the "Build" section, check the "code signing" section for any old profiles. I found that it was building to an old profile there.
Also from my side: MANY MANY thanks!! This solved an issue that I could nog solve manually in the project file. After a long time it seems to work now! Great...
In XCode, in the "Groups & Files" pane, expand "Targets" and double-click on your app's target.
This will bring up the Info pane for your target. In the "Build" section, check the "code signing" section for any old profiles. I found that it was building to an old profile there.
Strange, this didn't work for me, as it seems to have for everyone else.
For me, the error began when I renewed my provisioning profile. To be sure, I removed all existing provisioning profiles from both my device, and the xCode organizer.
I downloaded my renewed profile, installed to xCode with device plugged in (but still I had to manually drag the new profile to the device).
The project in question is a published app, and hasn't changed a byte since its final distribution build.
I can see the new profile installed in the device, and in the organizer. I can once again run the existing build of the app on the device.
In the target code signing options, I have tried every listed profile,
I can build to the simulator, but not to the device, even when I set the target code-signing options to "Do not code sign", I immediately get the error.
Strange, this didn't work for me, as it seems to have for everyone else.
For me, the error began when I renewed my provisioning profile. To be sure, I removed all existing provisioning profiles from both my device, and the xCode organizer.
I downloaded my renewed profile, installed to xCode with device plugged in (but still I had to manually drag the new profile to the device).
The project in question is a published app, and hasn't changed a byte since its final distribution build.
I can see the new profile installed in the device, and in the organizer. I can once again run the existing build of the app on the device.
In the target code signing options, I have tried every listed profile,
I can build to the simulator, but not to the device, even when I set the target code-signing options to "Do not code sign", I immediately get the error.
In XCode, in the "Groups & Files" pane, expand "Targets" and double-click on your app's target.
This will bring up the Info pane for your target. In the "Build" section, check the "code signing" section for any old profiles. I found that it was building to an old profile there.
Thank you, thank you, thank you!!! This was driving me crazy but now it compiles perfectly...
Thank you, thank you, thank you!!! This was driving me crazy but now it compiles perfectly...
Old thread, I know... just wanted to add... I tried everything in this thread, with no luck. Then, I changed my projects settings to compile with "don't code sign". Cleaned and built the project. (Of course, it wouldn't install on my iphone.) Then I changed it back to the normal dev profile and that fixed it.
I think the problem in my case is that my dev profile expired, so I chose to "renew" it in itunes connect. When you do that, the dev profile name of course does not change. So, when you attempt to build with a renewed profile, I'm guessing xcode gets confused and still thinks it's dealing with the expired profile (even though I deleted the expired profile, cleaned and rebuilt, and updated the project settings.)
None of the above suggestions fixed my problem with Xcode. After a lot of searching, I found the following which worked for me. I thought I'd post it in hopes that it might help someone else:
My assumption was that once Xcode saw that the old profile didn’t exists anymore it would switch over and use the new one. I cleaned all targets and built again. This time I was treated to a different error: ”Code Sign error: Provisioning profile ‘3E6AA725-6534-46F8-B9CE-D19AC9FD854B’ can’t be found”
After a bit of Googling I discovered that Xcode stores the ID of the provisioning profile in its project.pbxproj file. This discovery led me to the fix:
1. Close your Xcode project
2. Navigate to your project folder in the Finder
3. Right click on your .xcodeproj file and ‘Show Package Contents’
4. Drag the project.pbxproj file to Xcode (or any plain text editor)
5. Perform a search for the term ‘provision’ to find the PROVISIONING_PROFILE entry.
6. Copy the existing profile ID and paste it into the find field of a find and a replace dialog.
7. Open up the Organizer window (Window menu > Organizer) and navigate to your new profile under IPHONE DEVELOPMENT > Provisioning Profiles
8. Click on your provisioning profile and copy its Profile Identifier
9. Paste the string into the replace field in your open find and replace dialog.
10. Replace all instances of the identifier, save the file, close it, and reopen your Xcode project.
11. That should do it, build and go to run your app on your new device.
In XCode, in the "Groups & Files" pane, expand "Targets" and double-click on your app's target.
This will bring up the Info pane for your target. In the "Build" section, check the "code signing" section for any old profiles. I found that it was building to an old profile there.
that's it. it's incredibly confusing because if you enter the wrong one (try it), it still WORKS PERFECTLY IN "PROJECT" settings. AND the message in TARGET settings is mindblowingly confusing, poorly worded, making you think you have a perhaps private key error.
(PS do not literally enter "con.whatever.stuff", that is just my example. If you don't know what to enter there, you are buggered, hire a freelancer.)
In XCode, in the "Groups & Files" pane, expand "Targets" and double-click on your app's target.
This will bring up the Info pane for your target. In the "Build" section, check the "code signing" section for any old profiles. I found that it was building to an old profile there.
Csproket777 - I struggled with this on and off for days. The Apple provisioning process and device installation is very difficult. I registered as a member of this forum simply to say thank you for sharing this info!
Anthony
updated to 3.0, now "Provisioning profile can't be found"
SOLVED
Linear Mode
