Cannot create an iOS development certificate

Others are reporting similar no joy issues today.

Confirm your process against TN 2250 ~ iOS Code Signing Setup, Process & Troubleshooting and if still no luck, use Report a Bug against the tools.

Good luck in any case.

Similar trouble. I'd thought I'd bring my situation to light in case it helps.

I'm building from Unity3d on Unity 3.5 iOS 5.1 and xCode 3.0 for Lion. The unfortunate reason for this trouble for me was that I allowed my iPad to upgrade to 5.1, thereby making it impossible (?) to build from a previous version of Xcode, then I had to upgrade to Lion (shoulda done it long ago I suppose). I saw that there was a code signing issue and that the newest versions of xCode have automatic signing. I think the signing error was something to do with a duplicate provision or something or other, so I just decided to delete all provisions and start over from scratch. Having gone through the provisioning portal to delete the old version of my provision and deleting related keys, I then went to get new keys and a new certificate. No joy, as K T eloquently put it. Anyway, moving along into other stuff, hoping this problem ... fixes itself...

Thanks 🙂

Same problem here, I'm glad I found this post to find I'm not the only one 🙂

Upload -> Pending Issueance -> Refresh -> Gone

In fact, prior to trying to issue a new certificate, I was trying to upload a certificate for push notifications. I get errors there too:

Your request for a Certificate cannot be completed.

We were unable to generate your APNs SSL Certificate.

Please try again or visit the Provisioning section of the Provisioning Portal.

I'm hoping it's just a hiccup on Apple's side just today (Sunday being Sunday).

Same here; thanks to all for posting. Hopefully it will be working again tomorrow...

same same trying to create a distribution cert. glad i found this post, so i can at least stop beating my head against a wall.

Today, I could not create my certificate in Developer portal. I successfully did this step so many time before, I'm sure that I have done all of steps in Keychain Access correctly. So, what happed with Apple Cetificate Generator.

I'm using Lion 10.7.3 with Xcode 4.3.1 for Lion.

Does anyone try it on Snow?

Also having the same problem when using Automatic Device Provisioning through Xcode. It tries to submit a CSR which ultimately fails with message. "A certificate request has been submitted on your behalf, but has not yet been approved. An Agent or Admin must approve this request before you can download your certificate." Even though I'm a admin.

Same here, I am lucky to find I am not only one who meet this.

Same here...T.T

I tried it on two different Mac and still encountering the same problem. I wished that I knew what kind of error it is so that I can fix it. This is very frustrating.

Having this same issue. I've spent the better part of the last few hours deleting all my other profiles and certificates, pulling my hair out and messing up my other app installs only to find this. Very distressing. I'm on Snow Leopard and also need to update to Lion as well, after not realizing that you can't build for 5.1 without it.

I'm glad I found this so at least I can get some sleep and hope this certificate issue gets fixed overnight. Just finished a new app and can't play with it! 😟

me2

i should read this post 3 hours ago.

I am having a similar issue.

Trying to generate a new Production Push SSL Certificate and getting the following error message.

Generating your Apple Push Notifiaction service SSL Certificate

Certificate Name: Your request for a Certificate cannot be completed.

Your APNs SSL Certificate is being generated...

(This can take up to one minute.)

We were unable to generate your APNs SSL Certificate.

Please try again or visit the Provisioning section of the Provisioning Portal.

Hello,

i have the same problem :-(

Does anyone can suggest a email adress at Apple support the send them this link :

https://discussions.apple.com/thread/3799289?answerId=17832763022#17832763022

Best regards

Dietmar

Same here 😟 1:50AM PST Monday 2012/03/12. I guess I'll try again later...