For founders shipping Expo and React Native apps. AppIsComing finds missing iOS permission descriptions in your source and, for supported cases, turns them into a correction and a draft pull request. It also prepares privacy declaration drafts and reviewer replies for you to review.
Choose a repository and bring your app into one workspace.
✓Source repositoryExample record
✓App configurationExample record
✦Connected to your workspace
ATLAS
ATLAS · 1.0.0Made for
the journey.Explore somewhere new ↗
✦ Made by you
One step closer to launch
Click the app logo to switch between three apps across two businesses. These apps and businesses are fictional. Submission, reviewer responses and publishing remain owner actions; approval is decided by each store.
The tools you build with. The stores you launch on.
GitHub
Expo
React Native
Android
TypeScript
App Store
Google Play
GitHub
Expo
React Native
Android
TypeScript
App Store
Google Play
Across your development and release workflow
Checks that lead to concrete work.
Not just a list of problems: a permission correction, privacy declaration drafts, and a reviewer reply for you to review.
Source connection
Find the blocker in your source.
Compare permission APIs with app configuration to identify missing descriptions and the file to correct.
Privacy declarations
Generate declarations with their evidence.
Combine source and SDK findings with confirmed data use to prepare store declaration drafts.
Review preparation
Carry the correction through review.
Prepare permission corrections, draft PRs, new-build checks and reviewer responses.
See what the automation produces.
Try the sample app: inspect a missing iOS permission description, generate the correction, and see the reviewer reply drafted from it.
The source contains camera API signals. The app configuration has no camera purpose description.
Source evidence
src/receipt-camera.tsx:1 · CameraView
Correction target
app.json → ios.infoPlist.NSCameraUsageDescription
A sample app. The permission fix is made by the same generator the product uses; the declaration, store, merge, and device checks shown here are sample data.
From an upload error to a recorded correction.
Even an app without a photo feature can hit a photo-permission error. Follow one real, anonymized record from the cause to the correction.
ANONYMIZED CASE · SEPTEMBER 2026
Real release preparation · anonymized
iOS-01
From a blocker to a verified correction.
01
Failure
No photo feature. A photo-permission error.
An iOS upload was refused with ITMS-90683. The file-storage dependency expo-file-system included a photo-library API, even though the app did not use the photo library.
02
Correction
A declaration that describes the actual app.
A truthful purpose string explained the bundled API and the absence of photo-library use. A regression check protected that declaration.
03
Observed outcome
Upload accepted after correction.
A later build was recorded as VALID in App Store Connect, resolving the recorded upload issue.
Evidence and scope
Source: release preparation record iOS-01. It does not establish App Review approval or public availability. It pairs the dated code review of the cause and fix with a later check that the upload was accepted. App identifiers are removed. This is a past record, not a current customer status, and not a demo of automatic fixing or submission.
What the release package includes.
Sign-in and repository connection are free. The package covers one app, one version and 30 days, paid once.
What you get
Source checks that find release blockers, like missing permission strings
Permission corrections and draft pull requests
Privacy declaration drafts, with their source evidence
Store listing drafts and reviewer responses
A release record for each version, with completion emails
Help from an expert, answered by email within 2 business days (Korea time)Free
Not included
Store submission, which you run in App Store Connect and Google Play Console
App Review approval, which each store decides
Apple, Google and build-service account fees
Full refund within 7 days of payment, whether or not you have used it.
Release preparation. US$79 per app.
One app, one version, 30 days of preparation, paid once. The same app on iOS and Android counts once. Sign in and connect for free, then purchase once you have chosen the release.
Founders building iOS and Android apps with Expo and React Native. Bring a working app and use the workspace to understand the preparation still needed before store review.
What does GitHub sign-in give you access to?+
Sign-in reads your GitHub login and numeric account ID. Repository access is a separate step: you choose which personal-account repositories the read-only GitHub App can access. Organization installations are not supported at this time.
Which review problems can AppIsComing fix?+
Automatic corrections cover missing iOS permission descriptions in Expo app.json, for the permissions AppIsComing supports. Dynamic or native configuration needs a manual change. A draft pull request needs the separate Fix GitHub App. After you merge the change and test a new build, AppIsComing drafts your reply to the reviewer. Store submission and approval are not included.
Can I explore before connecting my app?+
Yes. The product preview uses clearly labelled, made-up app records. You can explore it without granting repository access. Your own workspace stays separate from the examples.
How do I know what to do next?+
Open your app and it shows the single next action to take. If an account or permission is missing, expand the inline help. App settings shows whether completion emails are available; when they are, turn them on and confirm your address to get recorded check results and review requests by email.
Can I get help from an expert?+
Yes, and it is free. Sign in, open your release, go to Expert support, and send your question. An expert replies by email within 2 business days (Korea time).
What does it cost?+
The release package is US$79 per app and version, for 30 days of preparation, paid once. iOS and Android editions of the same app count once; separate apps count separately. Sign-in and repository connection are free; purchase from your app’s billing page.
What we read and store
Read data handling and support details
Sign-in uses your GitHub login and numeric account ID, with a signed session cookie that expires after seven days. Repository access requires a separate GitHub App installation for repositories you select. AppIsComing supports personal-account installations; organization installations are not supported.
Google sign-in uses a separate Google-issued account identifier in a signed session cookie that expires after seven days. We do not link accounts by email or name, or store Google tokens. Google and GitHub workspaces are separate; repository import requires GitHub sign-in.
Import reads app configuration at your selected commit and stores workspace ownership, repository and commit details, configuration path and hash, and release records. Import does not store raw file bodies, credentials.json, or GitHub access tokens. Declarations and reviewer-preparation answers you enter are stored with release records.
Optional store and build-service credentials connected in Settings are stored separately with encryption. Signing out or uninstalling the GitHub App does not delete existing release records. AppIsComing does not provide a self-service workspace deletion feature.
Operated by PROJECT82 LLC. For support and data deletion requests: jin@project82.kr. Do not include credentials or private source files in your request.
AppIsComing — Release prep for Expo and React Native apps
