AppIsComing — workspace overview
English — change workspace language
Language
AppIsComing
Menu

Morrow

Release status: Waiting on store
Release journeyReview

Follow the current step first. Completed work remains available to review.

  1. ConnectionDone
  2. PreparationDone
  3. RemediationNot needed
  4. VerificationDone
  5. ApprovalDone
  6. SubmissionDone
  7. ReviewCurrent
  8. ResolutionAhead

These links open related work. Only recorded check results update your release stage.

Working onNext task

Morrow

Preview data

Release preparation · Waiting on store

Version1.0.0

Nothing outstanding

Every required requirement passes or carries a disclosed exemption for build build-morrow-current, and both chapter conditions are satisfied. There is no next step for this run.

YOU DO ONE THING

AppIsComing handles

  • Checks your connected source and store setup
  • Prepares permission corrections and draft pull requests
  • Prepares privacy declarations and reviewer materials
a.Northstar Lab / AtlasInteractive preview · sample

AUTOMATION OUTPUT · SAMPLE APP

From an error to the file to correct.

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.

View all 8 stages and check results

Your release journey · 8 stages

Current stage Review

The same journey as the homepage. Preparation checklists sit within this journey; submission and store review follow later.

9 of 9 checks passed

  • Passed 9
  • Needs a fix 0
  • Still to check 0
Release evidenceBuild, checks and approval records

Build build-morrow-current

Blockers

Nothing is holding this release

Every required requirement passes or carries a disclosed exemption for build build-morrow-current, and both chapter conditions are satisfied.

Agent activity

Waiting on the store

The store holds this build. No further action is available here.

Store

Submission and review

Submission
preview-submission-morrow · build build-morrow-current · 2026-08-25T06:00:00Z
Store review
In review
Public availability
Not confirmed. Store approval and public availability are separate states, and this product never implies one from the other.

Store coverage

Platform readiness

  • Android

    No release runs here until this target is connected.

    Not connected
  • iOS

    1.0.0 · Release complete

    Waiting on store

What we can prove

Readiness evidence

  • Store account prerequisites

    Connect

    Passed
  • Identifiers configured

    Configure

    Passed
  • Build signing

    Configure

    Passed
  • Launch stability

    Test

    Passed
  • Critical journeys

    Test

    Passed
  • Account deletion

    Test

    Passed
  • Listing metadata and screenshots

    Store Prep

    Passed
  • Privacy declarations

    Store Prep

    Passed
  • Reviewer credentials

    Store Prep

    Passed

Every required requirement passes or carries a disclosed exemption.

Owner decision

Review the evidence for this exact release before approving. Store execution is a separate step; approval does not itself submit the app.

Owner checkpoint

Final approval

Approval is already recorded for this build, and every required requirement passes. Nothing is outstanding at this checkpoint.

Approval is bound to build build-morrow-current.

This internal slice demonstrates the checkpoint but does not record approval.

Workspace data status

Sample data

This snapshot is 46 days old. Anything that could have changed is now stated as an observation with a date rather than as a present-tense status.

7 apps with real records are not shown. Sign in to view your apps

Data details
Record reference
project82-2026-08-29-01
Content hash
sha256:6af6ae2273581c61c01bbff4e3fb1bfe533e81516a08f6fad5bd1b0cc8579baa

Compiled from the release ledger and one reviewed provider-record file. Nothing on this page contacts Apple, Google, RevenueCat, GitHub, or Expo.

The hash detects an accidental edit to the file. It is not tamper protection — anyone who can edit the file can recompute it.