views:

310

answers:

9

In the provisioning portal, the "renew" button for my team provisioning profile is grayed out. And said profile is expired.

How can I renew it?

EDIT: I found the "automatic device provisioning" checkbox and "refresh" button in the organizer in Xcode. But when I select the team profile, check the checkbox, and push the refresh button, I get this message:

An unexpected error occurred. Please try again. If the problem persists, please contact Apple Developer Support (http://developer.apple.com/support).

I suppose I can go to support, but it would still be better to figure out what the problem is without involving them.

A: 

Is the certificate it is based on expired? Did you delete the device it was for?

CBGraham
No to both questions
William Jockusch
A: 

Try deleting the profile and click Refresh so Xcode re-adds it. Just a guess. I don't know why this would work, but it's worth a try.

Alexsander Akers
Tried that. Still the same error.
William Jockusch
A: 

Are you pressing the renew button from within Organizer in the latest Xcode version, 3.2.5 beta 3?

kubi
Good question. I'll update and see if it helps.
William Jockusch
Have now tried it. Same problem. Additionally, my device doesn't have iOS4.2 (would that even be possible yet?) -- but it doesn't get that far.
William Jockusch
A: 

Here's the answer to compiling question, however, if anyone else has the answer to the team provisioning profile please post.

You can still compile apps for your device/simulator by creating a developer profile and downloading it to your device.

The key to getting it to work is to make sure the profile is selected in both the Edit Project and Edit Target Settings from the Project Menu. The Target Setting is more specific and usually screws people up. Making sure they are both in sync will help you get things up and running.

From these two menus, check the Build tab and make sure the developer profile is displayed. The default is iPhone Developer and should point to your downloaded profile.

Jordan
Did that. No luck. :(
William Jockusch
A: 

Is there a problem using a different mobileprovision file? I believe you are getting the error on using a different provision file because your Target might be using the older one.

Try this

  • Get the new mobileprovision file and in Project's Build properties, set the mobileprovision to this one
  • Select the active target and in the target's Build properties, ensure that the same mobileprovision is being used
  • Compile the app.

See if that helps.

lostInTransit
Did that. No luck.
William Jockusch
Ok once again, what is the app id you have used for your mobileprovision file (in the Developer portal) and is it the same as the Bundle Identifier in your plist while trying to sign the app with this mobileprovision?
lostInTransit
A: 

As far as the Team Provisioning profile goes:

Does your console say anything? Are you using Xcode 3.2.5? I'd file a radar at http://bugreport.apple.com. Do you see the Team Provisioning file in the iOS Provisioning Portal? Does it have a green light?

You might try revoking it and letting Xcode create a new one.

As far as getting your app to work

You can always create an app-specific development profile. Choose your certificate and the app you are working on. Also make sure to select your device in the checkbox list.

Then download the profile (once it is ready) and double click on it to import it into Xcode.

If you look at the Xcode organizer, you should see your development profile in the list.

  • If it's red, that means your certificate has expired
  • If it's yellow, that means you don't have the private key present to sign using the selected certificate

In the project's Get Info window, under code signing, choose iPhone Developer for both pickers. Take a look at see which one is automatically selected (sometimes you have to manually choose the right one).

Then do a Clean & Build and you should be good to go.

Ben Scheirman
+2  A: 

I had the same "unexpected error" issue with the Team Provisioning Profile when it expired. I fixed it by deleting it in the Xcode Organizer AND in the ADC Provisioning Portal, then hitting renew in Organizer.

Simon Windmill
Thanks. I had been deleting it in just Xcode. That didn't do the trick. But when I also deleted it in the Portal, presto!
William Jockusch
A: 

Do these things if you want to really solve the problem:

(1) Are you using the certificate for which you made provisional profile from your mac? Or you are using the certificate from other mac machine. If that is the thing then please get .p12 file from there and install in your keychain.

(2) If your certificate in the keychain is the same for which you made the provisional profile then it's fine. Otherwise you have to create new provisional profile for the certificate.

(3) Please make sure that you have set the app id in the target > properties > identifier. If no then please set and choose the provisional profile from the target > build > code signing identity.

(4) Then clean and build your project.

If you find any problem then please let me know. I would like to solve this problem.

Tech Guru
+1  A: 

Posting this again here..

OK, I had the same problem with the disabled 'Renew' button against my Team Provisioning Profile.

This worked for me.

1) Deleted the expired Team Provisioning Profile from the Xcode Organizer.

2) Deleted the same thing from the developer provisioning portal.

3) Again from Xcode organizer check marked the auto provision and clicked 'Refresh'. it asked for the credentials and in a few seconds added the renewed Team Provisioning Profile.

4) It also added the new profile in the developer provisioning portal.

Sree