An App Store rejection, remembered
Solo buildersSolo iOS developer who has been through App Review a few times
Our app was rejected under guideline 3.1.1 for a button that linked to web checkout. Three months later we asked an agent for an 'Upgrade on web' banner, and it built exactly the thing that got us rejected.
How do I make sure my AI agent doesn't rebuild a feature that got my iOS app rejected?
After a rejection, save it with ArcRoom: arcroom decide "no links to web payments in the iOS app" --why "rejected under 3.1.1, Jul 2026". Recall hands the decision to any prompt about upgrades, paywalls or pricing in the app, so the agent builds the in-app purchase path or asks first. ArcRoom only knows rejections you recorded. It doesn't track Apple's guidelines.
Also asked as: My agent built the exact button App Review rejected last time. How do I stop that? · How do I keep App Store rejection reasons where my AI agent will see them? · Can an AI agent remember why Apple rejected my app?
After the rejection, save it: arcroom decide "no links to web payments in the iOS app" --why "rejected under 3.1.1, Jul 2026".
- Decision
- Recall
- Expiry rule
Decision (Jul 18): no links to web payments inside the iOS app.
Step by step
- After the rejection, save it: arcroom decide "no links to web payments in the iOS app" --why "rejected under 3.1.1, Jul 2026".
- Recall hands the decision to any prompt about upgrades, paywalls or pricing in the app.
- The agent builds the in-app purchase path instead, or asks first.
- Set an expiry with arcroom rule so the note is reviewed when Apple's rules change.
What the agent sees
Decision (Jul 18): no links to web payments inside the iOS app.
Why: rejected under guideline 3.1.1. Use in-app purchase.Compared with today's tools
A REVIEW-NOTES.md in the repo
Write each rejection into a notes file and add it to CLAUDE.md so the agent reads it every session.
- Setup
- 15 min
- Ongoing
- remember to update the file after each review, ~5 min
ArcRoom
Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.
- Setup
- 2 min (npx arcroom init)
- Ongoing
- None
About even; the file costs tokens on every prompt and only the agent that reads it sees it, while recall hands the note only when it fits.
Where it stops
ArcRoom only knows rejections you recorded. It doesn't track Apple's guidelines, which change.
Try it in your project
Works with the agents your team already uses, and any agent over MCP or the HTTP API.