Certificate Wizard
Code signing without the portal maze
The standalone Certificate Wizard creates and installs the signing assets your Codename One project needs. Start it from Maven, use the recommended Auto Setup flow, and keep the generated credentials backed up.
Quick start
Run it from your project
The wizard is a standalone desktop app bound to the current Codename One Maven project.
$ mvn cn1:certificatewizardCurrent workflows
One tool, the signing paths we support today
Use these maintained paths for mobile and desktop distribution.
Apple platforms
Create or reuse iOS development and distribution certificates, provisioning profiles, bundle IDs, devices, push capability, and Mac signing assets.
Apple setupAndroid
Generate a self-signed keystore locally with the JDK's keytool and install its path, alias, and password into the project.
Windows
Configure an Authenticode certificate issued by a certificate authority or managed signing provider. The wizard explains the required project settings.
Desktop signingApple setup
Use an App Store Connect API key, not your Apple ID password
The new wizard uses Apple's documented machine-to-machine API and avoids the fragile login and two-factor-authentication flow used by the old wizard.
- 1
Join the Apple Developer Program
An active team membership is required for device testing and App Store distribution.
- 2
Create a Team API key
In App Store Connect, open Users and Access → Integrations → App Store Connect API. Generate a Team Key with Admin access.
- 3
Import the three key values
Copy the Key ID and Issuer ID, then import the downloaded
.p8private key. Apple lets you download that file only once, so store a secure backup. - 4
Choose Auto Setup
The wizard reads your package name, creates or reuses the bundle ID, certificates, and profiles, then writes the debug and release signing settings into the current project.
Android
Generate locally, then back it up
The Android page runs the JDK's keytool on your computer. By default the keystore is stored under androidCerts/KeyChain.ks, and the wizard writes the corresponding project properties.
Do not lose this keystore or its password. A published Android app must continue to use the same signing identity for updates.
Desktop
Mac and Windows use different trust models
macOS: use the same App Store Connect key to create Mac App Store profiles or Developer ID certificates for direct distribution and notarization.
Windows: obtain an Authenticode .pfx or .p12 from a recognized code-signing provider, then configure the certificate, password, and timestamp service shown by the wizard.
Need a hand?
Bring the error to the community
Include the target platform, the wizard step that failed, the exact error text, and whether you were creating new assets or reusing existing ones. Never post private keys, certificate passwords, or tokens.