Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

Apple TV app on Mac not showing Watch Now/Apple TV+ due to Uzbekistan storefront error

Title: TV app on Mac never shows Watch Now/Apple TV+/Store — confirmed server-side 400 on uts-api.itunes.apple.com, works fine on iPhone with same account


Issue: The TV app on my Mac only shows local Library sections (Recently Added, Movies, Rentals, TV Shows, 4K HDR, Home Videos, Downloaded, Home Sharing, Public Sharing, Family Sharing, Genres) in the sidebar. Watch Now, Apple TV+, Store, and Search never appear, no matter what I try.


I'm signed into the correct Apple ID (confirmed via Account menu in the TV app, account name shows correctly at the bottom of the sidebar) and my Apple One subscription, which includes Apple TV+, is active and confirmed under System Settings > Apple Account > Media & Purchases (renews monthly, apps listed include Apple TV, Apple Arcade, iCloud+). My Apple ID's App Store storefront/region is Uzbekistan.


Critically: the exact same Apple ID, on the exact same Uzbekistan storefront, is actively streaming Apple TV+ successfully on my iPhone right now. This is not an account, subscription, or region-eligibility problem — it is specific to the Mac / TV app on macOS.


Troubleshooting completed, none of it fixed the issue:

- Verified account matches across all devices

- Confirmed Screen Time / Content & Privacy Restrictions are OFF

- Cleared TV app's cache and data (Caches, HTTPStorages, Application Support), ran "defaults delete com.apple.TV"

- Ran "sudo tccutil reset All com.apple.TV" to reset sandbox/privacy permissions

- Performed a full in-place macOS reinstall via Recovery Mode

- Tested on a second, freshly created macOS user account on the same Mac — identical failure

- Inspected TV.app's code signature and entitlements (codesign -d --entitlements). App is validly signed by Apple, no library-validation issues, SIP enabled

- Located the app's actual local data store at ~/Library/Group Containers/group.com.apple.tv.sharedcontainer/ (app has no app-sandbox entitlement, so this is expected, not a bug)

- Captured unified system logs around app launch and traced the exact failure to a specific network call

- Signed out of the Apple ID under Media & Purchases and signed back in, to force a fresh account/storefront handshake. This did not change anything and did not fix the issue


Root cause identified via system logs: On every launch, the TV app's WatchListKit framework calls Apple's "Unified TV Services" configuration endpoint to determine what to show:


POST https://uts-api.itunes.apple.com/uts/v3/configurations


This call fails every single time with:

AMSStatusCode=400

message = "Uzbekistan is not a supported storefront"

title = BadRequest


The app treats this as a hard failure and silently falls back to local-library-only mode — no error dialog, no visible indication anything failed.


I ruled out local caching as the cause of this stale answer:

- Each failed request returns a unique, server-assigned AMSServerCorrelationKey and a distinct network elapsed time (0.13–0.28s across four separate attempts) — consistent with genuine live round-trips to Apple's server, not a replayed local cache hit

- Searched all relevant local cache databases for any cached response to /uts/v3/configurations — none exists

- Checked macOS's account database (Accounts4.sqlite) for a cached storefront ID/revision. Found storefrontID "143566-2,42" (143566 = Apple's numeric ID for Uzbekistan). Signing out and back in did not change this revision number and did not change the server's 400 response — ruling out a simple local auth-cache refresh as the fix


This appears to be one of two things:

1. A staged/platform-specific backend rollout gap — Apple enabled Apple TV+ for the Uzbekistan storefront on iOS, but the rollout hasn't reached whatever backend flag or client-eligibility check the macOS TV app's uts-api calls depend on

2. A client-parameter-based eligibility check unique to the macOS TV app (app version, OS build, or platform identifier sent only by macOS) that the server uses to gate storefront support, independent of the account's actual, already-enabled Uzbekistan storefront


Has anyone seen this exact issue, or knows a way to force a platform-eligibility refresh from the client side? I've exhausted every local remedy (cache clears, full OS reinstall, fresh user account, Apple ID sign-out/sign-in) without any change to the server's response, so this likely needs Apple's involvement.


Can someone from Apple confirm whether macOS TV app support for the Uzbekistan storefront has been fully rolled out, or is there a way to manually refresh this device's platform eligibility?


Mac model: MacBook Pro (13-inch, 2020, Two Thunderbolt 3 ports)

macOS version: 15.8 (Build 24H23)

2 replies

I face same issue with my mac mini, but from MiddleEast store, have you received any response from apple ?