A release checklist the Live channel actually waits for
Team
Most teams have a release checklist somewhere: a doc, a wiki page, a message pinned in a channel. It works until a busy Friday, when someone promotes the build and nobody opened the doc.
On AppForShare the checklist lives on each build, every tick has a name and a time, and the Live channel refuses a build until the list is done and the release blockers from tester feedback are resolved. Steps such as "QA sign off" or "Product sign off" can name the person or role who approves them, and those approvals hold the store steps of the same version too.
Example
Shop app 2.5 (121), release checklist
- Smoke test on real devicesSara, Nov 2
- QA sign off (any Admin)Approved by Omar
- Product sign off (Lina)Waiting for approval
- Release blockers1 open
Made for
- Teams where more than one person can promote a build
- Agencies that need a clear sign off before a client sees a build
- Product owners and QA leads who must approve before a version goes to App Review or Google Play production
What it ends
- A checklist in a doc that nobody opens on release day
- Builds promoted to Live while a crash report is still open
- Asking in chat who tested what before a release
- A version sent to App Review before the product owner said yes
How it works
Step 1
Write the checklist
An Admin adds up to 20 steps in Settings, such as a smoke test on real devices or release notes written, and picks the channel it guards: Live by default.
Step 2
Name who signs off
Any step can name an approver: one member, or a role such as the owner, any Admin, any Developer or Admin, or any member. Approval steps are asked in the order of the list.
Step 3
Tick and approve on each build
Developers tick ordinary steps on the build page. When the steps above an approval are done, the approver gets one email and approves, or rejects with a note, signed in to the dashboard.
Step 4
Release when ready
Live takes the build once every step is ticked or approved and no blocker is open. Until then the build page, the CLI and CI get a clear answer about what is missing.
Named approvals
An approval step is not ticked like the others. The person or role it names approves it, or rejects it with a note that says what to fix, and the build page shows who answered and when. The approver gets one email when it is their turn, after every step above theirs is done, and can be asked again at most once every 12 hours.
Approvals are given only in the dashboard, signed in, on the build page or the release page of the version. The CLI, CI tokens and AI tools connected through the MCP server can read where the approvals stand, but they never approve or reject.
Approvals hold the store steps too
While an approval of a version is not given, Google Play production promote and App Store "Send for review" of that version wait in AppForShare as well. AppForShare looks at the AppForShare builds of the same app and version; one build of that version with every approval given is enough. You can turn this part off in Settings and keep the approvals for the channel only.
When a release cannot wait, an Admin can go ahead anyway. The override is recorded with their name, on the channel or with the store action.
Blockers from tester feedback
A tester report marked as a release blocker holds the gate until someone resolves it, also when it was reported on an older build of the same app. You can switch this part off and keep only the checklist.
When you have to ship anyway
An Admin can put a build into Live before the list is done, for example for an urgent fix. The build page then shows who did it. Developers and AI assistants connected through the MCP server cannot override.
The same answer everywhere
Promoting from the build page, appforshare promote in the CLI, the GitHub Action, Fastlane or the MCP server all go through the same gate. An upload with --channel live that is not ready yet lands without the channel, and you promote it once the list is done. appforshare checklist shows the state of a build in the terminal, and the release page shows the checklist and approvals of both platforms of a version together.
Good to know
- Ticks guard the AppForShare channel link. Pending approvals also hold Google Play production and App Store review when they are started from AppForShare; Play Console and App Store Connect themselves are not held.
- Approvals are given only in the dashboard. There is no approve command in the CLI, the CI API or the MCP server.
- One checklist per workspace, the same for every app in it.
- When the workspace leaves Team, the checklist stops holding channels and stores back, and approval steps become ordinary steps. The ticks and approvals are kept.
Questions
- Can I gate a channel other than Live?
- Yes. Pick any channel name in Settings, or leave it empty to use the checklist as a guide only.
- Who can tick a step?
- Anyone with the Developer role or above, for ordinary steps. An approval step is answered only by the person or role it names. Only Admins change the checklist itself.
- Can an approver sign off from the CLI or an AI tool?
- No. Approvals are given signed in to the dashboard, never with an API token, the CLI or the MCP server, so an approval always comes from the person it names.
- Does an approval hold App Store review?
- Yes, unless you turn that off. Send for review of a version and Google Play production promote wait until a build of that version has every approval. An Admin can go ahead anyway, and that is recorded.
- Which plan do I need?
- Team, together with named approvals, release blockers and the full release page.
Read next
Try it on your own app
Free account in a minute. Pro starts with a 7 day free trial.
More features
- Builds on GitHub Actions
- Flutter builds on GitHub Actions
- Flutter facts and checks
- Security scan on every build
- Connect Expo (EAS builds)
- Connect Codemagic
- Send store builds to TestFlight and Google Play
- TestFlight groups and beta review on send
- TestFlight feedback in your inbox
- iOS device registration
- Hands free device setup
- Store listing editor
- App Store submission
- Google Play releases
- TestFlight tester sync
- Tester app with notifications
- Tester groups and status
- Join links for testers
- Beta and Live channels
- Build history page
- Tasks and activity feed
- Feedback to Linear and Jira
- Release page per version
- Install link controls
- Several links per build
- Retire a test build
- TestFlight and APK in one link
- Install page in 13 languages
- In-app update check
- .aab uploads
- MCP server for AI tools
- Tester feedback with screenshots
- In-app feedback link
- AI test plan for each build
- Diawi compatible upload API
- Remember my iPhone
- Install help and why it failed
- Email the install link
- Custom channel address
- Verified publisher
- Daily install email
- Zipped .app upload
- Manage link for guest uploads
- Test accounts on the install page
- Telegram notifications
- Permissions in plain words
- Reply to testers and star ratings
- Follow a channel by email
- Download button for a README
- Store pages
- Check a build before upload
- Token scopes and CLI tools
- Upload from Claude or ChatGPT
- Passkeys and email code sign in
- Free build tools
- How reports work
- Malware check on every upload
- AppForShare Android store
- Re-sign iOS builds
- Single sign on (SAML and OpenID Connect)
- Require two step sign in
- Send to Microsoft Intune
- Choose where build files are stored
- Mac and Windows builds
- Workspace address
- Automatic clean up of old builds
- Tester email from your own mail server
- Webex notifications