Scan your iOS build before App Review, from the terminal

Point the CLI at a build and it reads the details App Review cares about: Info.plist, entitlements, privacy manifests and frameworks. The binary stays on your Mac.

app.appsium.io
Pre-Review report produced from a build scan, with a readiness score and findings
npminstall with one command
3build types: .ipa, .app, .xcarchive
0 bytesof your binary uploaded
MITlicensed client

Start in under a minute

Install it, sign in through your browser, and point it at a build. The review opens in the portal with answers already filled in from your build.

  • macOS, with your token kept in the Keychain
  • Needs a connected App Store Connect account
  • Bundle ID is checked against your team
# install
npm i -g appsium

# sign in through your browser
appsium login

# scan a build
appsium review ./YourApp.ipa

Block a release on real problems

Add it to CI with a token and fail the job when a finding reaches the severity you choose.

  • Exit code 1 at or above your threshold
  • --json for machine-readable output
  • Revoke tokens from Settings
# in your pipeline
APPSIUM_TOKEN=aps_… appsium review \
  build/App.ipa \
  --analyze --yes \
  --fail-on must_fix

# exit codes
# 0 ok, 1 finding, 2 error

Frequently asked questions

Does my app binary get uploaded?

No. The build is read on your Mac and only the extracted details are sent to Appsium.

Does it use credits?

Scanning and opening the review in the portal does not. Running the analysis uses your normal Pre-Review Check credits.

Is there an MCP server?

Yes. The Appsium MCP server is separate from the CLI and connects with a browser sign-in. See the MCP server page.

What do I need?

An Appsium account and a connected App Store Connect account, which proves the bundle ID belongs to your team.

Find it before App Review does.

Install the CLI and scan your next build.