AppIsComing

A missing iOS purpose string is a specific launch problem, and AppIsComing makes it the center of its public demo. The sample connects a camera API signal in source to the missing NSCameraUsageDescription entry in app.json. From there, the workspace can prepare a purpose string, a correction and a draft pull request. The point is to carry evidence into a change a builder can review, rather than stop at a warning.

That demo uses fictional apps. Its declaration, store, merge and device-check states are labeled sample data, so they should not be read as completed submissions or proof that an arbitrary app will pass review.

The paid workspace combines source checks with privacy declaration drafts, store-copy drafts and reviewer-response preparation. Privacy answers depend on both source or SDK findings and the data use the builder confirms. A source scan alone cannot establish every fact a store asks for.

The listed US$79 price is a one-time purchase for one app, one version and 30 days from verified payment. iOS and Android editions of that app count together. Store account and build-service fees are separate, and the owner remains responsible for testing, merging and submitting. Store approval is not included.

Sign-in and repository connection are free, but imports require a personal GitHub account and an authorized GitHub App installation. Organization installations are not supported. That rules out some team repositories before the release checklist even begins.

The privacy page says import retains configuration paths, hashes and release records, rather than raw source bodies or GitHub access tokens. Optional artifact uploads and connected store credentials are handled separately. Expiring a package does not delete its release records, and workspace deletion requires a support request. For a solo Expo builder, those access and retention details are worth checking before connecting a real release.