Bug 45839
Summary: | Cannot request new iPhone provisioning cert from Apple in Webkit | ||
---|---|---|---|
Product: | WebKit | Reporter: | allspamgoeshere |
Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED WORKSFORME | ||
Severity: | Normal | CC: | ap |
Priority: | P2 | Keywords: | InRadar |
Version: | 528+ (Nightly build) | ||
Hardware: | Mac (Intel) | ||
OS: | OS X 10.6 |
allspamgoeshere
Overview: Needed to create a new dev certificate for my iPhone. Created certificate signing request through KeyChain Access app and then tried to submit the file to Apple through their Provisioning Portal. Tried several times but it would always come back to the submission page with the "Browse for File" box blank. Tried the same file in Firefox 3.6.9 and it worked fine.
Steps to reproduce: Follow Apple's recommended procedures (http://developer.apple.com/ios/manage/certificates/team/howto.action) to generate an iPhone (and perhaps iPod Touch/iPad) developer certificate. After you create the certificate in KeyChain Access app attempt to submit it to Apple. It will reload the submission page.
Expected Result: It should send the certificate to Apple and show a different page that confirms the certificate was received and that it is "Pending" issuance.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
When you said that this doesn't work in WebKit, did you mean a WebKit nightly from <http://nightly.webkit.org>? Did you try shipping Safari/WebKit 5.0.2?
allspamgoeshere
At the time of the attempt to provision (2010-09-15) it was the latest nightly build of WebKit. I did not try the shipping Safari 5.0.2 but did use Firefox 3.6.9 (sorry, didn't think to try it in Safari).
-R
(In reply to comment #1)
> When you said that this doesn't work in WebKit, did you mean a WebKit nightly from <http://nightly.webkit.org>? Did you try shipping Safari/WebKit 5.0.2?
Alexey Proskuryakov
<rdar://problem/8463793>
Alexey Proskuryakov
Could you please check if this works now? There is a good chance that this was fixed in r74427.
Alexey Proskuryakov
Resolving as WORKSFORME pending answer.