Jump To Topic
The key improvements in this new certificate wizard are:
• Fewer Steps: A single form with checkboxes to select which items you want to generate, and then a login prompt. That’s it.
• Much Faster: Generate all your certs in 60 seconds. Give or take a few.
• More Reliable: We’ve taken steps to avoid network failures, which sometimes occurred due to the long-running back-end generation process.
Launching The Wizard
The Certicate Wizard can be accessed in the same way as usual. Open Codename One Settings, and select Device Settings > iOS > Certificate Wizard.
Select items to generate
Log in with Apple Developer credentials
Certificate generation process
Results and instructions
The certificates, profiles, and instructions will be saved in the iosCerts directory of your Codename One project. If you are using a Maven project structure this means they will be in common/iosCerts.
You can also see the results in the Device Settings > iOS > Signing section as shown below.
Hello, it’s great with this kind of improvements, the certificate wizard is a huge help. However, I just tried this new version to regenerate my certificates and the first steps work fine, I confirm the access with the 6 digit code and it’s running, but then I get an error “Certification generation failed. null”. First I thought it was because my credit card had expired, but it’s fixed and I still can’t generate. Any suggestions for what may be going wrong?
(Sorry just posted this on an unrelated issue in reddit, it should be here:) I connected to my account and noticed I needed to approve the new license conditions (hadn’t see that on my last connect). After approving it, the error message is different: now it says I need to update to Xcode 7.3. I wonder if that is on my side (I guess not)? As a side note, the Certificate error window is too small to show the entire error message and it’s not possible to copy the text which would have been nice.
I have opened an issue for this. https://github.com/codenameone/CodenameOne/issues/3571
I cannot reproduce this issue myself, so it would be helpful if you would update that issue with some more details that might help to reproduce the issue.