Direct Answer: Managing App Store Territories with AI
When publishing an iOS app, you decide which countries and regional App Store storefronts can discover and download your software. While many indie apps launch worldwide by default, regional content licensing, financial compliance rules, data privacy laws, or staged market rollouts often require restricting availability to specific territories.
With FlightDeck, you can manage your app's geographic distribution using natural-language conversations with your AI coding assistant (Cursor, Claude Code, Antigravity, or Windsurf).
Your assistant inspects your app's current regional availability, explains the consequences of modifying distribution, and stages proposed changes in the FlightDeck Desktop Approval Center. You review which countries are being enabled or removed, click Approve, and FlightDeck applies the changes across Apple's global storefronts.
What You Need
Before modifying territory availability:
- FlightDeck for Mac: Running and signed into your App Store Connect account.
- Connected AI Assistant: Connected to FlightDeck MCP.
- Approved or Draft App Record: An existing app in App Store Connect. (Note: on a brand-new app, territory settings take effect once your initial version is approved by Apple).
Core Concepts: Understanding App Store Availability
1. App Availability vs. App Store Pricing
It is essential to distinguish availability from pricing:
- Territory Availability determines which country storefronts can discover, download, and update your application.
- Pricing Schedules determine how much the app costs in local currencies across eligible price tiers.
An app can be free or paid in any country where it is available. If you remove an app from a country, customers using that regional App Store cannot find or download it, regardless of its price.
2. What Happens to Existing Users When a Territory Is Removed?
A common misconception is that removing an app from a country immediately deletes the app from customers' devices.
Important Platform Behavior on Territory Removal:
- THE APP REMAINS ON THEIR DEVICES: Apple does not erase or uninstall the application from existing devices. The app remains on the user's phone and can execute locally unless disabled by your own backend APIs.
- No Future Updates: Existing users in removed territories cannot download subsequent app updates.
- Redownload Restrictions: If a user uninstalls the app, they generally cannot redownload it from the App Store unless your account maintains specific grandfathered purchase entitlements.
- New Downloads Blocked: New customers in that country storefront cannot search for, view, or download the app.
3. Territory Identifiers and Regional Compliance
In Apple's App Store Connect API, territories are represented as individual 3-letter ISO 3166-1 alpha-3 codes (such as USA, CAN, GBR, DEU, FRA, JPN) across 175 individual markets.
Two critical platform realities apply:
- No Single "European Union" Territory Code: The European Union is not a single territory code in Apple's API. European distribution is managed through individual sovereign member-state territory codes (e.g.,
DEUfor Germany,FRAfor France,ITAfor Italy). - Geographic Availability vs. Regulatory Compliance: Enabling a territory code grants geographic distribution rights, but does not satisfy statutory regulatory obligations. For example, distributing in the 27 EU member states requires declaring your "Trader Status" under the European Union Digital Services Act (DSA) in App Store Connect. Without completed DSA verification, Apple may restrict your app from EU storefronts regardless of API availability settings. FlightDeck manages geographic availability via API, but regulatory compliance declarations must be completed directly in the App Store Connect portal.
- Export Administration Regulations (EAR): Apps using proprietary encryption must meet US export requirements before worldwide distribution.
- Content Licensing: Audio, video, and news apps frequently hold rights restricted to specific domestic markets.
Step 1: Inspect Current Territory Availability (Prompt)
Ask your AI assistant to check where your app is currently distributed:
Check the territory availability for [Your App Name] using FlightDeck.
Tell me:
1. Is the app currently available worldwide or restricted to specific countries?
2. How many countries are enabled?
3. Is "available in all future territories" enabled?
4. Are any major markets (such as the US, UK, Germany, France, or Japan) currently excluded?
What Your Assistant Does Behind the Scenes:
- It queries
apps_listto locate the target app and its App Store identifier. - It calls
app_availability_getto retrieve Apple's remoteappAvailabilityV2record. - It maps Apple's internal territory codes into readable country names and presents a clear summary in chat.
Step 2: Proposing Territory Changes (Prompt)
Whether expanding globally or restricting distribution to pilot markets, instruct your assistant to prepare a proposal:
Scenario A: Restricting to Specific Pilot Markets
We want to restrict [Your App Name] to English-speaking pilot markets: the United States, Canada, the United Kingdom, Australia, and New Zealand.
Please:
1. Explain the impact on existing users outside these markets.
2. Propose the exact territory change without executing it yet.
3. Show me the list of territories that will be enabled and those that will be removed.
Scenario B: Expanding to Worldwide Distribution
We are ready to launch [Your App Name] globally.
Please propose setting our territory availability to all supported App Store countries worldwide, including all future territories that Apple adds.
Show me the proposal before applying anything.
What Your Assistant Does:
- Evaluates your requested target list against Apple's supported territories.
- When configuring worldwide distribution, FlightDeck configures the
allTerritoriesparameter to true (enabling all storefronts) and setsavailableInNewTerritoriesto true for future regions. - Highlights user impact: warns that existing users in excluded territories will lose future update access.
- Confirms the proposed change in chat before initiating FlightDeck staging.
Step 3: Authorizing in FlightDeck Desktop Approval Center
Because changing territory availability directly affects user accessibility and commercial distribution, FlightDeck treats app_availability_set as a mutating operation requiring human authorization.
When your assistant prepares the update, FlightDeck stages a formal proposal in the Desktop Approval Center:
┌─────────────────────────────────────────────────────────────────────────┐
│ FlightDeck Approval Center [Profile] │
├─────────────────────────────────────────────────────────────────────────┤
│ 📋 Proposal: Update App Territory Availability │
│ │
│ App: FocusFlow (ID: 6478901234) │
│ Action: Set Territory Distribution │
│ Mode: Restrict to Selected Countries (5 enabled, 170 removed) │
│ Enabled Territories: USA, CAN, GBR, AUS, NZL │
│ Future Territories: Disabled │
│ Rationale: Restrict to English-speaking pilot markets │
│ │
│ [ Reject Proposal ] [ Approve & Apply ] │
└─────────────────────────────────────────────────────────────────────────┘
- Switch to the FlightDeck Desktop app on your Mac.
- Inspect the proposed territory changes and verify the enabled and excluded regions.
- Click Approve & Apply to authorize the update.
Step 4: Verify Updated Availability (Prompt)
After approving the proposal in FlightDeck Desktop, instruct your assistant to confirm the change:
I have approved the territory availability update in FlightDeck. Please apply the changes if needed and read back our current territory status to confirm that Apple's API has recorded the update.
What Your Assistant Does Behind the Scenes:
- It completes the staged execution through FlightDeck's secure coordinator.
- It queries
app_availability_getto perform a read-back verification against Apple's API. - It confirms that the remote territory settings match your authorized configuration.
Edge Cache Propagation and Timing
After Apple's API accepts your availability update:
- API Record Updates Immediately: Querying
app_availability_getreflects the new territory settings immediately. - Storefront Edge Propagation: Apple operates edge CDN caches for App Store storefronts worldwide. When an availability change is committed, Apple's API record is updated immediately, but public storefront visibility and regional App Store search indexes update asynchronously across Apple's global content delivery network. Apple does not publish a formal edge cache propagation SLA.
- First-Time Apps: If your app is not yet released, territory configurations remain pending until Apple approves your initial version draft.
Troubleshooting Territory Issues
| Issue | Cause | Solution |
|---|---|---|
| App not appearing in newly added country | Storefront edge cache propagation delay. | Storefront edge caches and search indexes update asynchronously across Apple's global CDN; allow time for regional caches to refresh. |
| EU country addition fails | Missing EU Digital Services Act (DSA) trader declaration. | Sign into App Store Connect $\rightarrow$ Business $\rightarrow$ Compliance and complete the DSA questionnaire. |
| Existing users cannot download updates | Country was removed from availability list. | Re-enable the territory or deploy backend communication informing users of the migration. |
| Cannot set availability on new app record | Version has not yet passed App Review. | Territory settings take effect automatically upon version approval and release. |
Related Guides
- Configuring App Store Price Schedules and Free Tiers via MCP
- Execution vs Staging Rules: What AI Operations Require Human Approval
- Human-in-the-Loop Governance: FlightDeck Approval Center
- Pre-Flight App Store Submission Readiness Check
- From Vibe Coding to the App Store: Complete iOS Deployment Guide