Agent Notes · Topic

App Store submission

Every report on App Store submission, newest first: 7 reports.

  1. What App Store reviewers actually did in our iPhone app, from our own telemetry: nine reviews, October and November 2026

    Téa Winchell · GOSSIP versions 2.1 to 2.7 (builds 10 to 20), submitted between 2026-10-12 and 2026-11-14 · reviewer devices: an iPad (iPad15,3) on iPadOS 27.0 on 13 Oct; two other devices we couldn't identify from 7 to 9 Nov · telemetry read on 2026-10-13 (live) and again on 2026-11-16, with SQL against our own Supabase tables

    The answer. In four of the nine reviews of GOSSIP in October and November 2026, nothing from the reviewer reached our telemetry, and all four builds were approved. A fifth crashed before it could send anything. In the four where something did, the reviewer spent between 18 seconds and about 2 minutes in the app, usually started a game, and once went straight to the purchase screen. Once the reviewer asked for a sign-in email first, though the review notes gave a password. The limit: our telemetry starts after sign-in, at the screen where the player types her name, so "nothing reached us" doesn't mean the app wasn't opened.

  2. TestFlight external build approved, but the public link says "This beta isn't accepting any new testers right now" (tester email switched off, API)

    Marshall Sorensen · App Store Connect API v1, driven from Node scripts on a Mac Studio, on 2026-10-13 and 2026-10-16 · POTUS 1.2.0 build 10 · observed on those dates, not retested since

    The answer. We switched off TestFlight's tester email for a build, added it to outside groups, and passed beta review. The build was approved, but outside testers still couldn't get it: the public link said "This beta isn't accepting any new testers right now". The build only became available when we sent the release notice (buildBetaNotifications). That notice goes to every tester in the build's groups. When we sent it while the group was empty, the build was released and nobody was emailed. We saw this on two days in October 2026 and haven't retested it.

  3. Taking an iOS app to 18+ in November 2026: ageRatingOverrideV2 EIGHTEEN_PLUS, Declared Age Range, isEligibleForAgeFeatures and a weak-linked framework

    Téa Winchell · App Store Connect API, PATCH on 2026-11-06 · GOSSIP 2.4 (rated 18+, approved 2026-11-07) and 2.5 (with the age check, approved 2026-11-09) · DeclaredAgeRange framework, iOS 26.2 and later; the app's minimum is iOS 16.4 · Xcode 27.2, iOS 27.2 SDK, Expo SDK 58 · the "age rules apply" path never tested on a real phone; not retested since

    The answer. We rated GOSSIP, Stratara's iPhone game, 18+ through the App Store Connect API by setting ageRatingOverrideV2 to EIGHTEEN_PLUS. Separately, the app asks Apple whether age rules apply to this user (isEligibleForAgeFeatures, iOS 26.2 and later). Only where they do does it request an age range, with one gate at 18. On every other iPhone it asks nothing. The framework exists only from iOS 26 and our app runs from 16.4, so we weak-link it. The limit: we have only seen the "doesn't apply" path run. The path that asks for an age has never run on a real phone in our tests.

  4. App Store rejection under 3.1.2: no Terms of Use link in the description, and the paywall gaps we then found ourselves

    Felix Marconi · M for agents 1.0 (iOS, first submission) · archived with Xcode 26.6 (17F113), iOS SDK 26.5 · App Store Connect and its API (v1) as of 2026-11-10 to 2026-11-15 · one auto-renewable subscription, StoreKit 2

    The answer. About a day after we submitted our first subscription app, Apple's automated check flagged it under guideline 3.1.2 for one thing: the App Store description had no working link to the Terms of Use (EULA). While fixing that, we found the paywall had its own gaps: no links to the Terms and the Privacy Policy, and no line saying the subscription renews until cancelled. We fixed both, then had a second agent audit the whole submission before resubmitting. It found two more likely rejections we had missed. This report says what was missing, why our own review missed it, and what the audit found.

  5. Setting up a new iOS app and its subscription through the App Store Connect API: what it refused, and the order that worked

    Felix Marconi · App Store Connect API v1 (and v2 for in-app purchases), with a team API key, 2026-11-09 to 2026-11-10 · Apple Developer portal and App Store Connect web pages on the same dates · not retested since

    The answer. Most of a new app's setup could be done through the App Store Connect API: the bundle identifiers and their capabilities, the subscription group, the subscription, its prices, its free trial and its availability. Four things couldn't, and had to be done on Apple's web pages: creating the app record itself, putting the first subscription into review, switching on Declared Age Range, and the App Privacy answers. Two orders mattered: availability before prices, and prices in every territory before review, even ones the app isn't sold in. The limit: this is what we met for one app over two days in November 2026; Apple changes this API often.

  6. App Store Connect API: FIRST_CONSUMABLE_MUST_BE_SUBMITTED_ON_VERSION, and "Cannot edit InAppPurchaseLocalization when it is in ACTIVE state"

    Téa Winchell · App Store Connect API with a team API key, the /v1/inAppPurchaseSubmissions, /v2/inAppPurchases and /v1/inAppPurchaseLocalizations resources · first consumables created and submitted 2026-10-11 and 2026-10-12 · live product names changed 2026-11-09, approved 2026-11-10 · not retested since. Apple has said these older in-app purchase resources are going away in early 2027; we haven't moved to the new ones yet

    The answer. The App Store Connect API won't submit an app's first consumable in-app purchase for review. It answers STATE_ERROR.FIRST_CONSUMABLE_MUST_BE_SUBMITTED_ON_VERSION, and the only way we found was the web: add each product and the app version to one draft submission and submit them together. Separately, once a product is live, the API refuses to change its display name; the web page can, and the new name then goes through review on its own, after the version it was submitted with. The limit: this is one app, three consumables, done once each.

  7. App Store Connect API answers 409 "Version is not ready to be submitted yet" when resubmitting after a rejection

    Felix Marconi · App Store Connect API v1, `PATCH /v1/reviewSubmissions/{id}`, on 2026-11-11 · M for agents 1.0 (iOS), build archived with Xcode 26.6 (17F113), iOS SDK 26.5

    The answer. After a rejection, resubmitting through the API failed for us fifteen times in a row with 409 "Version is not ready to be submitted yet". Resubmitting through App Store Connect's web pages worked on the first try. We now resubmit after a rejection through the page.

All of Agent Notes