Getting Started

Go from source code to App Store review or Google Play — in a single command. This guide walks you through installing the CLI, connecting your Apple and Google accounts, and shipping your first build.

Works with any mobile framework: MySigner auto-detects your project type — native Swift/Kotlin, React Native, Flutter, Ionic/Capacitor, Expo, or .NET MAUI. Just run commands from your project root.

Prerequisites

iOS

• macOS with Xcode installed
• An Apple Developer account with Admin access
• A mobile project that builds to iOS

Android

• Java 11+ (JDK) installed
• Android SDK installed with ANDROID_HOME configured
• A Google Play Developer account
• A mobile project that builds to Android

CLI

• Ruby 3.2+ (check with ruby -v)

Step 1: Install the CLI

gem install mysigner

Verify it's working:

mysigner version

If you use rbenv, run rbenv rehash after installing.

Step 2: Set Up Your Account

You'll need three things before connecting the CLI: a MySigner account, an organization, and an API token. If you already have these, skip to Step 3.

Create an account

1. Visit the MySigner Dashboard and sign up
2. You can use email, Google, GitHub, or Apple to authenticate
3. Verify your email if you signed up with email

You're auto-enrolled in a 14-day Pro trial — no card required. Every new account gets full Pro features (store uploads, AI translate / rewrite, screenshot studio quotas, etc.) for 14 days. After day 14 your account drops to Free unless you subscribe — nothing is deleted. See 14-Day Pro Trial for the full breakdown.

Create an organization

Organizations hold your apps, credentials, and team members.

1. After signing in, click New Organization in the sidebar
2. Enter a name (e.g., "Acme Inc")
3. Click Create Organization

Plan note: Organization limits depend on your current plan. Early-access upgrades are still handled manually rather than through self-serve checkout.

Generate an API token

The CLI uses API tokens to authenticate with your MySigner account.

1. Go to API Tokens in the sidebar
2. Click Create Token
3. Give it a descriptive name (e.g., "MacBook Pro CLI")
4. Select the read and write scopes (Admin scope is also available — only Admin / Owner roles can create it; see the Permissions matrix)
5. Click Create and copy the token immediately — you won't be able to see it again

Keep your API token secret. Never commit it to version control or share it publicly. In CI/CD, store it as an encrypted secret.

Step 3: Connect the CLI

Run the onboarding wizard — it walks you through connecting your CLI to MySigner step by step:

mysigner onboard

The wizard guides you through:

1. Account setup — confirms you have a MySigner account (or helps you create one)
2. Organization setup — confirms you have an organization ready
3. API token — walks you through generating a token if you haven't yet
4. CLI login — enter your email and paste the token to authenticate
5. Store credentials — optionally configure App Store Connect right away

Your API token is stored encrypted at rest in ~/.mysigner/config.yml using AES-256-GCM:

• macOS — the encryption key lives in the system Keychain (com.mysigner.cli / config_encryption_key). Tokens are never on disk in plaintext.
• Linux / Windows — the encryption key falls back to a file at ~/.mysigner/.encryption_key (mode 0600, owner-only). This is roughly equivalent in security to the config file itself; for the strongest posture, prefer the env-var path described below in CI/CD.

Other credentials (App Store Connect .p8 private keys, Google Play service-account JSON, keystore passwords) are not stored locally — they live on the MySigner server, encrypted at rest in the database, and are fetched on demand or brokered through the server during uploads. Android keystore files cached at ~/.mysigner/keystores/*.jks are plaintext binaries with a 24-hour TTL and 0600 perms; running mysigner logout wipes them.

CI/CD tip: in pipelines, set MYSIGNER_API_TOKEN (and optionally MYSIGNER_ORG_ID, MYSIGNER_EMAIL, MYSIGNER_API_URL) as encrypted secrets. The CLI uses env vars directly without touching config.yml.

Already have your token? You can skip the wizard and log in directly with mysigner login.

Step 4: Connect Your Store Accounts

MySigner needs API access to the stores you want to ship to. Set up one or both depending on your platforms.

App Store Connect (iOS)

Create an API Key in Apple

1. Go to App Store Connect > Users and Access > Integrations > App Store Connect API
2. Click the + button to generate a new key
3. Name it (e.g., "MySigner") and select Admin access
4. Click Generate
5. Download the .p8 file — you can only download it once
6. Note the Key ID and Issuer ID shown on the page

Add to MySigner

1. In the MySigner dashboard, go to App Store Connect in the sidebar
2. Click Add Credential
3. Fill in:
   • Key ID — the 10-character key ID from Apple
   • Issuer ID — the UUID from Apple
   • Private Key — open your .p8 file and paste its contents
4. Click Save

MySigner will verify the connection and sync your certificates, provisioning profiles, and registered devices.

Google Play (Android)

Create a Service Account

1. Go to Google Cloud Console
2. Create a new project or select an existing one
3. Enable the Google Play Android Developer API
4. Create a Service Account and download the JSON key

Grant Access in Google Play

1. Open Google Play Console → Users and permissions
2. Invite the service account email with Release Manager access (this is the minimum required — Admin works too but grants more than needed)

Add to MySigner

1. In the MySigner dashboard, go to Google Play in the sidebar and upload the JSON key
2. MySigner will validate the credentials and test the connection

Upload Your Keystore

1. Go to Keystores in the sidebar
2. Click Upload Keystore and upload your .jks or .keystore file
3. Enter the keystore password, key alias, and key password
4. Click Activate to set it as the default signing key

You can set up either or both platforms later by running mysigner doctor — it detects missing credentials and walks you through the setup interactively.

Step 5: Ship Your First Build

Navigate to your project's root directory and run one command. MySigner handles everything else — detecting your framework, building, signing, and uploading.

iOS to TestFlight

mysigner ship testflight

The CLI will detect your project, run any necessary pre-build steps (e.g., expo prebuild, cap sync, flutter pub get), build an Xcode archive, sign and export to IPA, and upload to TestFlight. Once Apple finishes processing (usually 5-15 minutes), the build appears in TestFlight for your testers.

iOS to App Store Review

mysigner ship appstore

This does everything testflight does, plus it automatically waits for Apple to process your build (polling every 3 minutes) and then submits it for App Store review — no manual steps needed. One command takes you from source code to "Waiting for Review".

Android to Google Play

mysigner ship internal --platform android

The CLI detects your framework, builds an AAB (Android App Bundle), fetches your keystore from MySigner, signs the build, and uploads to Google Play. Version codes are auto-incremented — if the Play Store already has version code 42, MySigner bumps to 43 automatically, so you never hit "version code already exists" errors.

Ship to any track by changing the target:

Add --release-notes "Bug fixes and improvements" to include release notes with your Android upload.

Step 6: Verify Your Setup

Run the doctor command to make sure everything is configured correctly:

mysigner doctor

Doctor validates your entire environment across both platforms:

If anything is missing or misconfigured, doctor will suggest a fix or offer to resolve it automatically.

Quick Reference

What's Next

Learn More Commands

• Ship Command Reference — All shipping options and flags
• Submit Command — Submit existing builds for review
• Doctor Command — Diagnose and fix issues

Follow Guides

• iOS to App Store — Submit for App Store review
• Android to Play Store — Production releases
• GitHub Actions CI/CD — Automate with CI/CD

Explore the Dashboard

Setup & resources: - Managing Credentials — ASC and Google Play setup - iOS Resources — Certificates, profiles, devices - Android Resources — Keystores, apps, tracks - API Tokens — Manage scopes (Read / Write / Admin) - Notifications — Email alerts for expiry, sync failures, revocations, team activity

Publish & ASO: - Releases — Store listings, release notes, AI translate / rewrite, release checklists, phased releases - Screenshot Studio — Canvas editor for App Store / Play Store screenshots - Keywords & ASO (Pro+) — Edit App Store keywords per locale, track ranks - Reviews & Ratings — Unified inbox for both stores with response templates (Pro+) - Analytics — Acquisition, retention, stability, monetisation - Custom Product Pages (Pro+) — iOS CPP variants

Billing: - 14-Day Pro Trial — How the auto-trial works - Pricing & Plans — Free vs Pro vs Team

Team plan features: - Permissions — RBAC matrix - Audit Log — Immutable record of sensitive actions - SSO (SAML 2.0) — Single sign-on with Okta / Entra / Google Workspace

Troubleshooting

Having issues? Try these in order:

1. Run doctor — mysigner doctor diagnoses and auto-fixes most problems
2. Check status — mysigner status verifies your connection and credentials
3. Force sync — mysigner sync --force refreshes data from Apple and Google
4. Enable debug — DEBUG=1 mysigner ship testflight for detailed error output

See the Troubleshooting Guide for solutions to specific error messages.