Skip to main content
Every command is run as tappify <command>. Add --help to any command to see its options:
Most commands require you to be signed in — run tappify login first.

​
login

Authenticate the CLI with your Tappify account via a browser-based device flow.
Your session is stored locally and reused by every other command. If you’re already logged in, this is a no-op.

​
logout

Clear the stored session from this machine.

​
upgrade

Update the CLI to the latest version.
For a binary install (curl), this downloads and swaps in the latest release in place. For a package-manager install (Homebrew, Scoop, Chocolatey, winget, npm), it prints the command to run for that manager instead.

​
init

Create a tap.config.json in the current directory. The command prompts for your app name, slug, type, and base URL.
Run this in your project root before publish. It writes a config like:
tap.config.json
Run tappify link to connect this directory to a Tappify app so commands like deployments configure pick it up automatically — no --app flag needed.
Connect the current directory to a Tappify project and its app(s). Writes a git-ignored .tappify/project.json so later commands (like deployments configure) know which app to act on.
Pick a project, then the app(s) this directory ships. A React Native repo that ships both an iOS and an Android app can select multiple; single-platform apps resolve to one.
​
string
Link a specific project without prompting.
​
string
Link a specific app without prompting.

​
publish

Bundle your built app (dist/, tap.config.json, and icons) and upload it to Tappify.
Requires a tap.config.json (run tappify init first) and an authenticated session.

​
deployments configure

Set up CI code signing for an app. The command walks you through it interactively — see the signing guide for the full walkthrough.
​
string
The app to configure signing for. If omitted, the CLI uses the app linked to this directory (run tappify link first). You can also copy the exact command (with your app id) from the signing page in the dashboard.
Prerequisites: git on your PATH (plus gh, the GitHub CLI, if you choose to create the certs repo with it). The command checks for everything it needs and tells you what’s missing.

​
create-deployment

Create a deployment for a project.
​
string
required
The project to deploy.
​
string
default:"production"
Target environment (e.g. production, staging).
​
string
The branch to deploy.
​
boolean
Print what would happen without making changes.