One command checks signing, SDK levels, privacy manifests, push and login setup, permissions and your build scripts on both platforms. Another one fixes what it can. When a build still fails, paste the log and get the cause and the steps.
$ npx shipdoctor scanSee it run$ npx shipdoctor scan ANDROID ✖ Release build is signed with the DEBUG keystore ✖ applicationId "com.helloworld" is a template default ✔ targetSdkVersion 36 IOS ✖ Bundle ID is still the React Native template default ✖ No DEVELOPMENT_TEAM set on any target → Archive will fail with "Signing requires a development team" ✖ App icon set is empty (no images in AppIcon) ▲ NSLocationWhenInUseUsageDescription is empty 5 errors 2 warnings 3 passed
Every screen below was captured from the tool itself.
$ npx shipdoctor scan ./my-app ANDROID ✖ targetSdkVersion 34 — Play requires 36+ since 2026-08-31 ✖ Release build is signed with the DEBUG keystore ▲ Keystore passwords stored in android/gradle.properties IOS ✖ No PrivacyInfo.xcprivacy for the app ✖ Missing Info.plist purpose strings: NSCameraUsageDescription (react-native-vision-camera) SCRIPTS ✖ build_ios.sh: Windows line endings (CRLF) ✖ .github/workflows/ios.yml: iOS build steps on a ubuntu runner … excerpt
Reads your Gradle files, Xcode project, Info.plist, privacy manifest, Podfile, build scripts and CI files. Each problem the stores would reject is listed with its fix. In CI it fails the job, so a broken release never reaches review.
$ npx shipdoctor fix --bundle-id com.acme.app --team ABCDE12345 ShipDoctor fix — 5 fix(es) ready, 3 need you ✔ Sign release builds with an upload key ✔ Set Android applicationId to com.acme.app ✔ Set development team ABCDE12345 on every target ✔ Set iOS bundle ID to com.acme.app ✔ Remove unused empty NSLocationWhenInUseUsageDescription edit: android/app/build.gradle - applicationId "com.helloworld" + applicationId "com.acme.app" - signingConfig signingConfigs.debug + signingConfig signingConfigs.release Applied. Backup saved — undo anytime: shipdoctor undo Errors: 5 → 1 (left: add your app icon — your design, your call)
You don’t need to find the right line in Xcode or Gradle. ShipDoctor shows exactly what it will change. You approve it, it backs up your files first, and shipdoctor undo puts everything back. Things a tool shouldn’t decide for you, like your keystore password, come with exact step-by-step instructions instead.
Free shows every fix and the first change in full. Pro shows and applies all of them. Fixes are prepared on shipdoctor.dev from config files only — passwords and keys are removed before anything is sent.
$ npx shipdoctor aab app-release.aab ✖ 1/3 native libs are NOT 16 KB aligned: libimagepipeline.so (4 KB) ✖ base/lib/arm64-v8a/libimagepipeline.so align 4096 ✔ base/lib/arm64-v8a/libreactnative.so align 16384 ✔ base/lib/arm64-v8a/libhermes.so align 16384
Opens your .aab or .apk and reads every 64-bit native library, then names exactly which one breaks the 16 KB rule (Play blocks these updates from 1 Feb 2027). It also lists every policy-restricted permission your libraries quietly added to the final manifest.
$ npx shipdoctor ipa Acme.ipa IOS ✖ Built with Xcode 16.2 / iOS SDK 18 — App Store Connect requires Xcode 26 / iOS 26 SDK ✖ Frameworks contain simulator/Intel slices: Charts ✖ SDKs on Apple's list without a privacy manifest: FirebaseCore ✖ Signed with a Development profile ("Acme Dev") ▲ Possibly missing purpose strings: NSLocationWhenInUseUsageDescription (links CoreLocation) ✔ App binary is code signed … excerpt from the test suite's broken builds
The 16 KB rule is Android-only, and iOS has no page-size check. What fails on iOS is checked by App Store Connect after you upload: the Xcode/SDK version (Xcode 26 since 28 Apr 2026), simulator slices inside frameworks, development or expired provisioning profiles, SDKs missing privacy manifests, icons and iPad settings. ipa checks all of it on your computer first.
$ npx shipdoctor log xcode-archive.log 1. Provisioning profile does not contain your signing certificate Why: the profile was made for a different (often expired or revoked) certificate than the one in your keychain. 1. developer.apple.com › Profiles: tick the current certificate, regenerate and download. 2. Double-click the new .mobileprovision. 3. fastlane match: fastlane match appstore --force 4. Use the same signing style on every target.
Paste a failed Gradle, Xcode, fastlane or EAS log, or the App Store / Google Play rejection email. It recognises 58 common failures, collected from real developer reports. It explains the cause in plain words and starts from the first real error, not the last line.
Before: “signed in debug mode”, then “use a different package name”, then “Version code 1 has already been used” — one rejection at a time.
With ShipDoctor: scan lists them all at once. fix --bundle-id sets up release signing and a unique package name, and tells you the one keytool command to run.
Before: running from Xcode uses development signing. An App Store archive needs a distribution certificate, a team on every target and a profile per extension.
With ShipDoctor: fix --team sets the team on every target. log explains certificate/profile errors step by step.
Before: an email with ITMS-91053 or ITMS-90683 and a guideline number.
With ShipDoctor: scan catches missing privacy manifests and purpose strings before you upload, and fix adds them. Already waiting in review? No tool can speed up Apple’s queue, but you can make sure it doesn’t come back rejected.
Before: the warning names no library.
With ShipDoctor: aab names the unaligned .so file, so you upgrade the one dependency that ships it.
Before: “bad interpreter: ^M”, “No such module”, or an iOS job on a Linux runner.
With ShipDoctor: scan checks your .sh and CI files. fix repairs line endings, adds set -e, switches to the .xcworkspace and moves iOS jobs to macOS. Hard-coded passwords are flagged for you to rotate, never silently edited.
These don’t break the build. They break on a real phone: no notifications, a crash on “Sign in with Google”, a silent camera. ShipDoctor reads which libraries you use and checks the config each one needs.
shipdoctor scan in your project folder. Red means the store will reject it.shipdoctor fix shows the changes. --apply makes them, with a backup. Steps that need you (keystore, team ID) are spelled out.shipdoctor aab on the bundle.shipdoctor log on the output, fix, and go again.# .github/workflows/release.yml — stop broken releases in CI
- run: npx shipdoctor scan --md shipdoctor-report.mdEvery change runs against real project templates, deliberately broken copies of them, real compiled binaries and real error messages.
If ShipDoctor’s fixes don’t get your release through, run shipdoctor refund --log build.log within 14 days. Your failing log shows us what we missed — and you get your money back.
$ npx shipdoctor scanReport a bug, tell us it isn’t working, or ask for a feature. Screenshots and code welcome.