deniz.in

Markets

Weather

Loading weather

· via dev.to (home feed)

Developer turns three App Store rejections into a pre-submit checklist for iOS releases

A solo iOS developer on dev.to details the real causes behind App Review rejections, from a 4.3(a) listing fingerprint to a tool that looked broken but wasn't, plus the checks now gating every submission.

Developer turns three App Store rejections into a pre-submit checklist for iOS releases

A solo iOS developer who maintains three apps has documented, in a post on dev.to, the concrete causes behind a run of App Review rejections — and the pre-submit checklist that now gates every submission.

The developer ships a prayer-times app written in Flutter, plus a PDF password tool and an expense tracker in SwiftUI. According to the post, a single week brought rejections over an App Tracking Transparency prompt the reviewer never saw, a China publishing-license request, and an ITMS-91064 privacy-manifest error. The run continued with a 4.3(a) rejection under the spam guideline, a build voluntarily pulled from the review queue, and a tool that appeared broken during testing even though its code was correct. With each rejection costing a 24-to-48-hour cycle, every lesson became a line in a file called PRE-SUBMIT-GATE.md: nothing is submitted until each line carries evidence — a commit, a screenshot or an API read-back.

The 4.3(a) rejection came from the listings, not the code

Most discussion of guideline 4.3 concerns reskinned template apps, but the developer's three codebases share almost nothing, and the prayer app was flagged anyway. Looking at the three App Store listings the way a reviewer would, the developer found a shared fingerprint: the same screenshot layout across all three apps, a common description skeleton with repeated stock phrases about one-time pricing and on-device data, near-identical sentences in the review notes, and all three submissions made within eight minutes from a brand-new developer account. None of these is a problem alone; together, they suggest an account producing interchangeable apps, and once one app is flagged the rest of the account draws scrutiny.

A keyword search made the positioning worse: a competitor's description already claimed nearly word for word what the developer had listed as differentiators, meaning the copy described the entire category rather than a specific app.

The response was to withdraw PDF Unlock 1.2 while it still sat in "Waiting for Review". As the post explains, cancelling a submission is not a rejection — the version returns to an editable state and the in-app purchase goes back to "Ready to Submit". The listing was rewritten around a feature that is genuinely uncommon, auto-unlocking recurring password-protected bank statements and payslips, and review notes now open with a differentiation section, a 60-second test path and an attached sample encrypted PDF. No boilerplate is shared between apps, and the new gate also bars submitting two apps on the same day — a rule the developer admits breaking that same weekend.

A tool that looked broken but wasn't

While testing on a real phone, the developer added a password to a PDF, opened the file in the Files app and got no password prompt; a print-and-copy option also seemed ignored. Verification with Core Graphics showed the output was genuinely AES-128 encrypted with permissions correctly set. The actual defect was behavioural: every tool writes a new copy with a suffix into the app's own Files tab and silently leaves the original in iCloud Drive untouched, and the result screen never explained that. Under guideline 2.1, a tool that seems to do nothing reads as broken.

The fix combines communication with verified replacement. The result screen now states that a new copy is saved in the Files tab and that the original is unchanged, with Save to Files and Share buttons. An optional Replace Original action, behind a confirmation, appears only for files picked through the system document picker that the app can actually write to; the write is coordinated with NSFileCoordinator, then the file is read back and compared byte for byte so success is never claimed without verification. A nearby second silent failure was also fixed: the in-app viewer had shown blank pages for encrypted files instead of requesting the password.

Failing safe on the launch crash

A TestFlight build had crashed at launch with GADInvalidInitializationException because the Google Mobile Ads SDK validates GADApplicationIdentifier in Info.plist at startup even when the SDK is never used, and three archives in a row carried an empty ID. The refined approach still fails the build on a malformed ID, but lets a Release build from a fresh clone or CI run ad-free: an xcconfig substitutes Google's sample app ID purely to satisfy the launch check, while the empty unit ID keeps the SDK, the UMP consent flow and ATT entirely switched off.

Why it matters

App Review failures are frequently presentation and feedback problems rather than engineering defects: a listing fingerprint, an unexplained output location, a crash caused by an unused SDK. The practice documented on dev.to — converting each rejection into one concrete, evidence-backed check that must pass before submission — is a cheap and portable discipline for any solo iOS developer whose release cadence depends on a 24-to-48-hour review cycle.

  • #ios
  • #app-store
  • #app-review
  • #mobile-development
  • #swift