GeoTech

Engineering / Case study

Shipping to the App Store when the API says no: creating app records and the availability trap

GeoTech Engineering · · 7 min read

iOSApp Store ConnectRelease automationXcode

We publish a lot of iOS apps for a small team: our own products and apps for clients, each with Arabic and English listings, screenshots, age ratings and review notes. Almost all of that can be scripted against the App Store Connect API. Two things cannot be taken for granted. The API will not create the app in the first place, and an app that Apple approves can still be invisible in every country. This is the routine we settled on in November 2026, and the mistake that taught us the second part.

3approved apps that showed "Removed from App Store"
175territories each of our apps is now available in
1day from empty record to "submitted" for a new app

TL;DR

The problem

An App Store app starts as an app record in App Store Connect: name, bundle ID, SKU and primary language. Until it exists, there is nothing to upload a build to and nothing for the API to fill. With our team API key, a request to create one fails: the API answers that the apps resource does not allow CREATE. The key can read and update the apps it sees (19 of ours when we checked) but cannot make a new one.

The documented path is the website: New App, fill the form, done. That is fine once. It is a manual step in the middle of an otherwise scripted release, done by whoever happens to have the account open, and it is where wrong SKUs and wrong primary languages come from.

What we tried

The routine

1. Create the record from Xcode

We fill that sheet the same way every time: the brand name in Latin letters, SKU <slug>-ios, and the primary language of the product. On our build Mac this step is driven by AppleScript through System Events, so it does not depend on a person clicking.

Two practical notes. Typing into that sheet with simulated keystrokes did not work for us; setting the text field value directly and clicking by position did. And the sheet sometimes ends with DistributionAppRecordProviderError error 0. In our experience that error usually means the record was created and Apple's index had not caught up. Do not retry blindly; ask the API whether the bundle ID now has an app.

GET /v1/apps?filter[bundleId]=com.example.app
# 0 results  → really not created, run the sheet again
# 1 result   → created; continue with the script

2. Fill everything else by API

One script per app does the rest, with three modes: check (read-only), fill and submit. The key points of fill:

Everything is idempotent. Running fill twice gives the same listing, which matters because the build is usually not processed on the first run.

3. What stays in the browser

The App Privacy questionnaire has no API, so it is answered and published on the website. The reviewer account's password is typed by a person into App Review Information. And when an app is rejected, the API tells you the state but not Apple's message; the reason text is only in the Resolution Center.

The mistake: approved and invisible

On 14 November three of our apps, G.Academy, Spotra and Curava, came back approved and showed "Removed from App Store". Nobody could find or install them. Nothing had been removed. They had never been made available anywhere: the records had no territory availability, because our script set the price and assumed availability came with it.

Availability is its own resource. The fix is a single request that lists every territory and opts in to new ones:

POST /v2/appAvailabilities
data:     { type: appAvailabilities,
            attributes: { availableInNewTerritories: true },
            relationships: { app, territoryAvailabilities: [ ...one per territory ] } }
included: [ { type: territoryAvailabilities, attributes: { available: true },
              relationships: { territory } }, ... ]

The script now reads GET /v1/apps/{id}/appAvailabilityV2 first and only creates availability when there is none, so it never overwrites a deliberate choice. The next day we audited every app the key can see. All of our own apps report 175 of 175 territories, and eight older apps we manage were opened the same way. Checking availability is now a hard step before any "send for review".

Google Play has the same idea under a different name: countries and regions per track. It can be read through the API; for us, changing it meant the Play Console, then submitting the change in Publishing overview.

Result

Checklist

  1. Create the app record from Xcode Organizer; confirm by bundle ID through the API.
  2. Keep the name, SKU pattern and primary language the same for every app.
  3. Make the fill script idempotent: replace screenshot sets, update instead of create.
  4. Answer the age rating from the keys Apple returns today, not a saved copy of last year's form.
  5. Set availability explicitly and check it before every submission. Price is not availability.
  6. Expect to read rejection reasons in the website; plan for it.

Need this?

We take apps from build to both stores: records, listings in several languages, screenshots, privacy and age questionnaires, review notes and the release checklist, for our own products and for clients. Talk to us at geotech.dev.