← MWM AICONTENT HISTORY
WHAT CHANGED
Update to MWM AI
Snapshot Nov 16, 2026 · 18:15 UTC · version 0.32.2
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save MWM AI and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Getting a version out on both stores: where the app stands, builds and TestFlight, the App Review submission, release types and phased releases, Google Play tracks and rollouts, and what a rejection means. Use when the person says things like \"where is my update?\", \"submit my app for review\", \"why was my app rejected?\", \"release the approved version\" or \"push this bundle to internal testing\". Not for the listing's words (store-copy) or privacy answers (privacy-and-legal).",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 361
}
],
"name": "shipping",
"skill_md_contents": "---\nname: shipping\ndescription: \"Getting a version out on both stores: where the app stands, builds and TestFlight, the App Review submission, release types and phased releases, Google Play tracks and rollouts, and what a rejection means. Use when the person says things like \\\"where is my update?\\\", \\\"submit my app for review\\\", \\\"why was my app rejected?\\\", \\\"release the approved version\\\" or \\\"push this bundle to internal testing\\\". Not for the listing's words (store-copy) or privacy answers (privacy-and-legal).\"\n---\n\n# Shipping\n\n## When this applies\n\nMoving a version from preparation to the public on either store: its number and build, testers, the submission to App Review, the release after review, Google Play's tracks and rollouts, and reading a rejection. The listing's words belong to store-copy; privacy answers and the policy to privacy-and-legal.\n\n## The job and what good looks like\n\nThe person knows in one sentence where the app stands: which version, which build, what Apple or Google holds and what is left to them. Every public step happens after they saw its full content: what the submission carries, which build goes out, which release action follows. Statuses come from a fresh read of the app, and an older one is given with the time it was read. Nothing about a release is guessed.\n\n## How a pro decides\n\n- **Risky or routine.** Offer a phased release for an update that touches purchases, sign-in or a new SDK; the person chooses.\n- **Which track.** An Android build starts on internal testing unless the person named another track.\n- **What App Review needs to know.** Rewrite the review notes for each version: what changed and how to test it, with a demo account when sign-in is needed.\n- **Why it was rejected.** Read this app's rejection and the guideline it cites before answering; a general reason is not this app's reason.\n- **Wait or act.** A store that is processing or reviewing needs time, not another attempt.\n\n## Do\n\n- Say how a store wants builds signed before the person goes looking for a file.\n- Give the share of users a rollout has reached, since that is what people want to know.\n- Ask which build when several could go and none is attached.\n- Show the open advice on the version, such as stale notes or a link on another site, before a submission.\n- Name the SDKs you see in readable code when export compliance or privacy needs an answer.\n\n## Don't\n\n- Don't add a language to a version unless the person asks.\n- Don't guess a version code, a build or an export compliance answer.\n- Don't record a check the person has not confirmed in their own words.\n- Don't retry a publish or a submission in a loop: each attempt can be real and irreversible.\n- Don't answer \"why was it rejected?\" before reading this app's rejection.\n\n## Pitfalls\n\n- A submission takes everything waiting with it, not just the version.\n- Withdrawing from review takes the whole submission back.\n- A first release on Google Play can have its own requirements, for new developer accounts and for the target level.\n- A build still processing is not missing; it needs minutes, not a new upload.\n\n## Store facts\n\nTool results carry the store rules and limits they depend on, each with its source and the date it was checked. `get_publishing_knowledge` answers questions on this skill's topics the same way (topics: `app-store/versions-and-mutability`, `app-store/submission-and-app-review`, `app-store/release-options`, `app-store/builds-and-testflight`, `app-store/rejections-and-guidelines`, `google-play/tracks-and-rollouts`, `google-play/target-api-level`, `google-play/new-account-testing`, `google-play/policy-and-appeals`). When you use one of these facts, give its source and date.\n"
}SHA-256 of public snapshot: ee891ffa044b9082fc355a24fe9b8967ea3fc89f8b2a32720caaddb7aed7432b