- Home
- Skills
- Mobile Development
- App Store Review Guard for Expo
Works with the AI Agents you already use
App Store Review Guard for Expo
Most store rejections for Expo apps are not about code quality.
Free
App Store Review Guard for Expo
Example session with this skill installed
I'm about to submit this app to the App Store and Google Play. Will it get rejected?
- Read your context and instructions
- Compiled the app store review
Review readiness: clean / dev.fatmaaktas.shiptest (iOS + Android)
Verdict: Blocked. As it stands, this will be rejected on both stores. Most of the fixes are small, though.
Rules checked against: 2026-10-29, which is recent enough to trust.
I ran the static preflight script (it exited with errors) and read through src/.
Blockers (the upload or review will fail)
The production build is a dev client. eas.json → build.production.developmentClient: true means the build opens the Expo dev launcher, not your app. → Delete that line from the production profile.
2.
The backend URL is localhost (src/api.ts:1, API_URL = "http://localhost:3000"). On a reviewer's device, fetchNotes() will fail, and an app that can't load its core content is an instant 2.1 rejection. → Point it at your live production backend, and make sure it's running during review.
3.
The OpenAI key ships inside the app (src/api.ts:2, EXPO_PUBLIC_OPENAI_KEY). Every EXPO_PUBLIC_* value is compiled into the bundle, so anyone can pull the key out. Apple may not catch this, but it's a real security problem. → Move summarizeNotes to your backend, have the app call your server, and
rotate the key now.
4.
The camera permission string is empty (app.json → ios.infoPlist.NSCameraUsageDescription: ""). Apple rejects this under 5.1.1(ii). → Something like "Scan handwritten or printed notes so they're saved as text in your notebook." A cleaner option is to remove the infoPlist entry and add ["expo-camera", { "cameraPermission": "..." }] to plugins.
5.
There's no way to delete an account (Apple 5.1.1(v), Google User Data policy). Google Sign-In creates accounts, and nothing in the app deletes them. → Add Settings → Delete account, which calls a backend endpoint that deletes the user and their notes. Google Play also needs a
public web URL for deletion, entered in the Data safety form.
6.
AI data is shared without consent (Apple 5.1.2(i)). Notes are sent to OpenAI with no disclosure. → Before the first summary, show a consent screen that says notes are sent to OpenAI, and only send after the user accepts. Name OpenAI in your privacy policy.
Likely rejections (depends on the reviewer)
Sign in with Apple (4.8): Google is the only login. If it creates the user's main account, Apple expects an equivalent private option. → Add expo-apple-authentication (via npx expo install, which needs a new native build).
No privacy policy link in the app (5.1.1(i)): → Add one on a Settings/About screen as well as in the store listing.
Before you press submit
- Set
ios.config.usesNonExemptEncryption: falseif you only use HTTPS, so you skip the encryption question on every upload -
supportsTablet: truemeans reviewers may test on an iPad. Check the camera screen there and add iPad screenshots - Set up a demo Google account for reviewers (no 2FA), with sample notes already loaded
- Fill in the App Privacy labels and Play Data safety form: email/name (Google), user content (notes, sent to OpenAI), and photos (camera)
- Android: confirm targetSdk is at least 36 (SDK 58's default already meets this)
- For a new personal Play developer account: run the closed test (12 testers for 14 days) before production access
Questions that change the verdict
- Is Google Sign-In the only way to make an account? If there's also email/password, the 4.8 item mostly goes away.
- Are scanned photos sent to OpenAI too, or only text? That changes the consent wording and the data disclosures.
Draft review notes (once the above is fixed)
DEMO ACCOUNT
Google: [[demo@gmail.com]] / [[password]] (2FA disabled, sample notes preloaded)
HOW TO REACH THE CORE FEATURE
1. Sign in 2. Open a note → "Summarize" 3. Tap Scan to capture a note with the camera
PERMISSIONS
- Camera: requested when you tap Scan; used only to capture notes. If declined, typing notes still works.
ACCOUNT DELETION
Settings → Account → Delete account (deletes all data within [[N]] days).
THIRD-PARTY AI
Note text is sent to OpenAI only after the user accepts the consent screen shown before the first summary.
The quickest wins are #1, #2 and #4, which are all config changes. #3, #5 and #6 need backend work first. Want me to start on the config fixes?
Connects securely to your tools. The creator never sees your data.
About this skill
Most store rejections for Expo apps are not about code quality. They come from a short list of predictable gaps: a vague permission string, a missing account-deletion path, Google Sign-In without an equivalent private login option, a subscription screen that hides the price, a reviewer who could not log in. This skill finds those gaps before you submit, and turns a rejection email into a concrete fix when one has already happened.
What it does
- Static preflight (
scripts/preflight.mjs, zero-dependency Node 18+): reads app.json / app.config, package.json, eas.json and your source. Flags empty or generic permission strings, ATT without setup, account libraries without a deletion flow, secret keys shipped in the bundle, third-party AI calls without consent, rating prompts that ask for 5 stars, icon alpha channels, outdated Xcode images, Android target API below 36 and sensitive Android permissions. - Manual checklist for what a script can't see: IAP vs external payments, user-generated content moderation, hidden or region-locked features (2.5.19), reviewer access.
- Rejection triage: paste the email from App Review or Google Play and get the guideline, the Expo-specific fix and a reply draft.
- Review notes: a template for App Store Connect / Play Console notes, including a demo account and how the reviewer reaches each feature.
Output
A readiness report with a verdict (Ready / Fix before submitting / Blocked), blockers, likely rejections, a pre-submit checklist and the questions that would change the verdict.
Freshness
Rules checked on 29 Oct 2026 against Apple's App Review Guidelines (16 Oct 2026), Google Play Console Help and Expo SDK 58. The script exits non-zero on blockers, so it also works in CI.
Open source (MIT): https://github.com/disconnectuss/expo-ship-kit.skills. Part of expo-ship-kit, with sibling skills for release preflight, EAS Build & Submit and OTA updates.
Static checks only: it can't see runtime behaviour, whether your backend is reachable during review, or what's filled in App Store Connect / Play Console (privacy labels, Data safety, screenshots). Rules were checked on 29 Oct 2026; store rules change several times a year, so check the date in SKILL.md. The script needs Node.js 18+ and runs from the Expo project root.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 1 day ago
- Free with an Agensi account
Requires
Permissions
Terminal: runs `node scripts/preflight.mjs`, which only reads the local Expo project and calls `npx --no-install expo config --json` (no download, no network). Read Files: app.json/app.config, package.json, eas.json and source files. The key-like regexes in the script are leak detectors, not secrets.