Skip to content

Product Engineering

What App Store Rejection Taught Me

4 min read

Getting Tracademic through Apple's App Store review was, without question, the hardest part of shipping to iOS. Not because any single problem was complicated, but because App Store review checks a wide surface area — purchases, privacy, sign-in, metadata, the actual working state of the app — and a rejection on any one of them sends you back to the queue. This post is the list of guidelines I tripped over, what I did about each one, and the fact that it ended, eventually, in approval.

In-app purchase rules

The first lesson was the most fundamental: any digital subscription offered inside an iOS app has to go through Apple's in-app purchase system. A web-based payment flow — the kind that works perfectly well for Tracademic's browser version — isn't an option inside the iOS app itself. The fix was routing all iOS subscription purchases through RevenueCat, which sits on top of StoreKit and handles the App Store's in-app purchase flow properly, while the web app kept its existing Stripe integration. I've written more about how that platform split works in One Codebase, Three Platforms.

Privacy and sign-in requirements

Review also checks that what you tell Apple about data collection matches what the app actually does, and that any sign-in options meet Apple's requirements around account creation and account deletion. Getting this right meant going back through the app's actual data flows — not what I assumed they were — and making sure the privacy details submitted with the app matched reality exactly, along with making sure account deletion was actually reachable from inside the app rather than requiring an email to support.

Metadata that didn't match the app

App Store metadata — screenshots, description, the preview of what the app does — has to represent the app as it actually behaves at the point of submission. A screenshot from an earlier build, or copy that describes a feature slightly differently to how it now works, is enough to trigger a rejection on its own. The fix here was less technical and more procedural: re-capture screenshots against the exact build being submitted, every time, rather than reusing assets from the last approved version.

IAP products not submitted

This one cost me a full review cycle for a reason that had nothing to do with the app itself. In-app purchase products have to be submitted for review alongside the binary, in a "ready to submit" state — if a product referenced by the app isn't included in that submission, review can't verify it, and the app gets sent back. The fix was making sure every IAP product the build actually offers is attached to that same submission before hitting submit, not assumed to already be approved from an earlier round.

A broken demo account

Reviewers need to be able to actually use the app, including any parts that sit behind a login or a paywall. A demo account that doesn't work — wrong credentials, an account that's expired, a Pro feature that isn't actually unlocked for it — stops review before it can even assess the feature. The fix was maintaining a working demo account with Pro access confirmed immediately before each submission, rather than trusting that an account set up weeks earlier was still in a valid state.

Rejection reasonFix
Subscription paid outside Apple's IAPRoute iOS purchases through RevenueCat/StoreKit
Privacy details didn't match app behaviourRe-audit data flows, correct the submitted privacy details
Screenshots/metadata out of dateRe-capture against the exact build being submitted
IAP products missing from submissionAttach every referenced product before submitting
Demo account didn't workVerify credentials and Pro access before each submission

What got Tracademic through in the end wasn't a clever fix. Each rejection only told me about the issue found in that pass, so it came down to fixing it, resubmitting and waiting for the next round, again and again. It was the hardest part of the whole project, and what carried it over the line was determination and a lot of hours.

Getting to approval

None of these individually were hard engineering problems, and the guidelines above are the ones that actually caught me out along the way.

The takeaway

App Store review isn't really testing whether your app works — you already know that. It's testing whether your submission, in full, is internally consistent: what you say the app does, what it actually does, what you've told Apple about data and payments, and whether a reviewer with no prior context can pick it up and use it end to end. Treating the submission itself as something to audit, not just the app, is what got Tracademic through.

The build pipeline that gets a submission-ready iOS binary out in the first place is its own set of lessons — see CI/CD for a Solo Developer.