My App is showing Ready for Dist and in Apps and Pricing showing Available in UK but still is not on the App Store. It said this for 2 days now

Hello, I am new for apple developer. I see the problem and I think apple show me very few error message and I do not know to start with it. I was created my app by python and build to .app then package it to pkg by the pkgbuild. I have problem to upload the pkg file to app store connect by transporter both CLI and GUI. when I try to upload it by GUI, I see this message. Cannot find the ITMSP file: (null). (11)` and when I upload my pkg by the CLI, I found more message but still cannot start with it as well. [2026-08-23 09:57:58 ICT] <main> DEBUG: Registered file for monitoring: /Users/xxxxxxxxx/.itmstransporter/temp/tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp with action CANCEL_ALL [2026-08-23 09:57:58 ICT] <main> DEBUG: Started file monitor for 1 file(s) [2026-08-23 09:57:58 ICT] <main> INFO: Starting upload for package b7ac46de-45fe-4fa6-b0f6-6fea35038d8f-tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp. [2026-08-23 09:57:58 ICT] <main> INFO: Computing total size of files to upload ... [2026-08-23 09:57:58 ICT] <main> DBG-X: adding file for % complete logging: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp , size: 7704460 [2026-08-23 09:57:58 ICT] <main> DEBUG: Setting total size of files for upload to: 7704460 [2026-08-23 09:57:58 ICT] <main> INFO: Done computing total size of files to upload. [2026-08-23 09:57:58 ICT] <main> INFO: Starting checksum calculations for 1 file(s) using up to 1 thread(s)... [2026-08-23 09:57:58 ICT] <main> INFO: Checksum calculations are complete, elapsed time: 0 d 0h 0m 0s. [2026-08-23 09:57:58 ICT] <main> INFO: Creating reservations for build upload: b7ac46de-45fe-4fa6-b0f6-6fea35038d8f [2026-08-23 09:57:58 ICT] <main> DEBUG: creating upload file... [2026-08-23 09:57:58 ICT] <main> DEBUG: SMART-CLIENT: getCurrent(); using pinned data center = contentdelivery01.itunes.apple.com [2026-08-23 09:57:58 ICT] <main> INFO: Package upload progress: 0.00% completed [2026-08-23 09:57:58 ICT] <main> INFO: Transfer Metrics Summary: [2026-08-23 09:57:58 ICT] <main> INFO: bytes transmitted: 0 [2026-08-23 09:57:58 ICT] <main> INFO: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp transfer metrics: [2026-08-23 09:57:58 ICT] <main> INFO: bytes transmitted: 0 [2026-08-23 09:57:58 ICT] <main> INFO: Starting checksum calculations for 1 file(s) using up to 1 thread(s)... [2026-08-23 09:57:58 ICT] <main> INFO: Checksum calculations are complete, elapsed time: 0 d 0h 0m 0s. [2026-08-23 09:57:58 ICT] <main> INFO: Creating reservations for build upload: b7ac46de-45fe-4fa6-b0f6-6fea35038d8f [2026-08-23 09:57:58 ICT] <main> DEBUG: creating upload file... [2026-08-23 09:57:58 ICT] <main> DEBUG: SMART-CLIENT: getCurrent(); using pinned data center = contentdelivery01.itunes.apple.com [2026-08-23 09:57:59 ICT] <main> DEBUG: Stopped file monitor [2026-08-23 09:57:59 ICT] <main> DEBUG: Transport HTTP failed after 0 bytes, trying next transport. Error: could not upload file: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp [2026-08-23 09:57:59 ICT] <main> DEBUG: Upload phase transition: CLOSED -> INITIAL [2026-08-23 09:57:59 ICT] <main> ERROR: All transport types failed for file: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp Package Summary: 1 package(s) were not uploaded because they had problems: /Users/xxxxxxxxx/xxxxxxxxx/../xxxxxxxxx_Image/xxxxxxxxx.pkg - Error Messages: All transport types failed for file: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp [2026-08-23 09:57:59 ICT] <main> DBG-X: Returning 1 Not too sure if anyone ever see my issue and how you solved it?

The appeals process for when your Apple Developer account is in Pending Termination status doesn't work. The re-instate developer account form is very clear it shouldn't be used if it's pending. But the form for "I would like to appeal an app rejection or app removal" which is the correct form for pending state. Gives the error "There are no apps associated with this team." we do have apps associated. There could be thousands of developer accounts that weren't able to file an appeal correctly because of this bug. "If you would like to appeal this termination decis ion to the App Review Board, you must do so within 30 calendar days. When submitting your appeal, be sure to select "I would like to appeal an app rejection or app removal" from the drop-down menu on the Contact the App Review Team page and provide a written statement that includes the following:" Apple is very clear which to use.

I’m trying to determine the supported submission path for the first non-consumable IAP in a watchOS-only app. Configuration The app uses a standard watch-only container: Container: com.seanfu.safe Watch app: com.seanfu.safe.watchkitapp ITSWatchOnlyContainer = true WKWatchOnly = true WKApplication = true It offers one non-consumable “Full Version” unlock and uses StoreKit 2: Product.products(for:) Product.purchase(options:) Transaction.currentEntitlements Transaction.updates The product ID in the Release binary exactly matches App Store Connect. Paid Apps agreements, banking, tax, pricing, and territory availability are active. The Release archive contains no local .storekit configuration or test bundle. TestFlight works, but App Review receives no product In TestFlight, using the real App Store sandbox and App Store Connect product configuration, Product.products(for:) returns the correct product, localized price, and title. The purchase sheet can be presented. During App Review, the same request repeatedly returns an empty array without throwing an error. The reviewer sees this application-defined diagnostic: IAP-L-01(empty x5) This is not an Apple or StoreKit error code. It means: Five separate Product.products(for:) calls completed without throwing. Every call returned an empty product array. The diagnostic appears only after the initial request and limited retries are exhausted. Thrown StoreKit errors use different diagnostics. The app does not locally filter a successfully returned product. Therefore, the screenshot means StoreKit returned no matching product in five consecutive requests. This has happened in multiple review attempts, while the same Release code path works in TestFlight. An App Review representative contacted us and explicitly stated that a watchOS-only app can be reviewed and tested with IAP. They suggested investigating our StoreKit integration, but our audit found no code path that could transform a non-empty response into this diagnostic. Submission behavior changed Earlier watchOS-only builds could be submitted with both: The app version The “Full Version” IAP Those submissions reached App Review, where the product was empty: Submission accepted → Review starts → Product array is empty For build 23, we explicitly added the In-App Purchase capability to the Watch target in Xcode. The project now records the IAP capability and explicitly links StoreKit.framework. This did not add an IAP entitlement to the signed app. The bundle IDs, watch-only packaging, product ID, StoreKit code, pricing, availability, agreements, banking, and tax status remained unchanged. After uploading build 23, App Store Connect no longer allows the app version and IAP to be submitted together. The draft contains: iOS App 1.0, build 23 The “Full Version” non-consumable IAP App Store Connect blocks the submission and says IAPs and subscriptions are not supported on Apple Watch and must be removed from the submission. The behavior is now: App version + IAP selected → Submission blocked before review This timing does not prove that adding the Xcode capability caused the change. App Store Connect may have changed its validation, or the new build may have caused its watch-only classification to be reevaluated. However, the transition is notable: earlier submissions were accepted but the product was unavailable during review; the current submission is blocked entirely. Contradictory documentation StoreKit documentation says the Swift IAP API is available on watchOS 8+: https://developer.apple.com/documentation/storekit/choosing-a-storekit-api-for-in-app-purchases The documentation for purchase(options:) specifically says to use it for apps running on watchOS: https://developer.apple.com/documentation/storekit/product/purchase(options:) However, App Store Connect documentation says IAPs are not supported on Apple Watch and must be removed before submitting an Apple Watch app version: https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/submit-an-in-app-purchase/ The same page says the first non-consumable IAP must be submitted with a new app version. This creates a circular requirement: The first non-consumable IAP must accompany an app version. An Apple Watch app version cannot include an IAP. A watchOS-only app therefore appears unable to submit its first IAP. Questions What is the supported path for submitting the first non-consumable IAP of a watchOS-only app? Can Apple review the first IAP separately, or apply a backend override, despite the requirement to include it with an app version? Is an iPhone companion app required, with watchOS IAP support intended only for Watch apps associated with a regular iOS app? Could the unsupported submission association explain why TestFlight sandbox returns the product while App Review receives an empty array? Why were earlier watchOS-only submissions accepted with the IAP attached, while build 23 is blocked despite unchanged bundle IDs and watch-only packaging? Does App Store Connect use the Xcode IAP capability or explicit StoreKit linkage when validating the submission? Clarification from a StoreKit or App Store Connect engineer would be greatly appreciated. The StoreKit documentation, App Store Connect validation, and guidance from App Review currently describe different behaviors.

I’m still waiting for app review and it’s the third iteration. It’s taking two months to get my app reviewed and I don’t understand what the issues are with these constant backlogs and long wait times, Apple. What’s going on? You are hurting us developers.

’m extremely disappointed with the way Guideline 4.1(a) – Copycats is being enforced. My app was rejected even though it uses its own custom logo and design, while another app on the Mac App Store is using branding that is much closer to Instagram’s official identity and can easily mislead users. App in question: https://apps.apple.com/ro/app/app-for-instagram-%C2%BA/id6781353081?mt=12 This feels like inconsistent enforcement and unfair competition. I hope someone from Apple reviews this case and takes appropriate action regarding this application.

I'm starting to wonder if something has gone horribly wrong in the App Review department. We've had reviewers request specific information in one message, which we supplied the same day, then we wait another 4 days and they ask the same question having clearly not looked at the information we sent. We've now been completely adrift for 21 days and it's been over a week since we last heard from them. We have hundreds of people waiting on us, can't promote on social media, receiving support requests every day from customers wondering why they can't access the app. This isn't the first time we've released an app through App Store Connect, and our app is very straighforward - no restrictions or unusual requests. The app is obviously compliant, they just aren't reading any of the information we're providing, so we're totally stuck. It didn't used to be like this. A year ago we were seeing reviews turn around within the stated 24-48 hours. Has something changed in the last 6 months? Perhaps an uptick in submissions due to AI coding? Anyone else seeing these issues?

Summary: The "In-App Purchases or Subscriptions" selection section does not appear on my app version page, so I cannot attach my first In-App Purchase to my build. This has caused four consecutive Guideline 2.1(b) rejections. Setup: App: Qmetra IQ (Apple ID 6791254506, Bundle ID com.vibecode.qmetraiq.londa9) First app release, never published App version 1.0, current build 1.0.1 (2) Non-consumable IAP: com.vibecode.qmetraiq.londa9.results (Apple ID 6792799431) IAP status: Ready to Submit App Review screenshot for the IAP: uploaded (1242×2688) Paid Apps Agreement signed, banking and tax complete, no open items under Business What I see: On the version page, the "In-App Purchases or Subscriptions" heading exists, but contains only an informational message ("...add an app version to your submission so the items are reviewed together..."). There is no button, link, checkbox, or "+" to select the IAP. The submission draft panel contains only the app version, with no way to add the IAP. Opening the draft from the IAP page shows only the IAP, with the warning "Cannot be submitted for review — add an app version for the selected platform", and the "Submit for Review" button greyed out. What I have tried: Removed the previous rejected submission from review, then rechecked the version page — section still absent Assigned a fresh build (1.0.1 build 2) and saved Re-saved the IAP metadata Resubmitted the app version alone — rejected again under 2.1(b) Replied in the review thread twice — no resolution Rejection reason each time: "one or more of the In-App Purchase products have not been submitted for review." Could an Apple staff member please forward this to App Store Connect Support or engineering so the In-App Purchase can be moved to In Review manually? Several older threads describing this exact bug were only resolved that way. Happy to share more details privately if needed. Thank you.

Hi, My Digital Services Act trader verification has been stuck "In Review" since July 9, 2026 — nearly 7 weeks now, against the stated typical review time of ~5 business days. Current state in App Store Connect: Business → Compliance: Digital Services Act | 27 Countries | Last Updated: Jul 9, 2026 | Status: In Review Pricing and Availability: 148 Available / 27 Cannot Sell — all EU territories show "Trader status is required for distribution on the App Store in the European Union" App is live on all non-EU storefronts (verified via apps.apple.com/us), not found on any EU storefront including Poland where I'm based All agreements, bank accounts and tax forms: Active No request for additional documents received at any point App: BirthMinder: Birthday Reminder, Apple ID: 6789108105 Support case filed: 20000148065826 (August 26) I've seen several threads describing the identical situation, including cases where the verification was already approved on Apple's backend but never reflected in App Store Connect. Could someone from Apple please check the status of this verification? Almost two months of blocked EU distribution for an indie developer is a serious problem. Thank you.

It seems that Beta 6 isn't allowed to upload to App Store connect yet? Will this be resolved soon? No issues with previous beta's

For the last 2 months I have been submitting the first iOS builds of my app “Zema Kirar”. However Appstore connect wrongly rejects it claiming it was built bu a BETA version of xcode and / or MacOS. My Dev Environment I am Running macOS Tahoe 26.6.2, and Xcode 26.6 (Build 17F113). Both are the ”current” latest public (GM) versions required by apple. Steps to reproduce: Xcode cloud build/ and transporter upload completes > I select the build > click save > click on Submit. Appstore connect shows error: Unable to add for Review. The items below are required to start the review process: New apps and app updates must be built with the latest public (GM) versions of Xcode, and the iOS, macOS, watchOS, and tvOS SDK. Apps built with the beta versions aren’t allowed.

My Apple Developer membership shows a renewal date of September 5, 2026, but there is no “Renew Membership” option anywhere in my account. I have already opened a support case more than 24 hours ago with no response, and today I spent around 50 minutes on hold with Apple Developer Support before the call disconnected. This has been extremely disappointing and irresponsible for a paid developer service. This is also directly affecting my app. I am unable to submit my build for External Testing review because of the membership issue. At the same time, I still have around 10 days remainingin the account expiry. On my Internal Testing section, TestFlight shows users that “the app cannot be downloaded.” This is so so disapointing that apple doesn't bother to even give an update on what is the actually issue. I have dropped 4-5 emails and request call back atleast 3times only to get ghosted on both platforms. Can someone from Apple Developer Support please investigate this and enable the renewal option? I need to continue testing and distributing my app, and I'm running out of time.

Hi everyone, I’m trying to switch my app’s Primary Language from Simplified Chinese to English (US) in App Store Connect. When I hit save, I receive this error message: You have one or more errors on this page. Primary Language couldn’t be saved because another field is invalid. The problem is no specific invalid field is pointed out by the UI. There is no highlight, no hint telling me exactly what is wrong. I’ve already contacted Apple Developer Support. They checked my backend account and said there are no obvious issues on their side, and suggested I post here for community assistance. I have filled out all required metadata fields for English (US), including app name, subtitle, description, keywords, support URL, privacy‑policy URL, and uploaded all required screenshots. All assets are ready. I have attached screenshots showing my configuration and the error popup. It is really confusing that App Store Connect throws a generic error without pointing to which exact field is causing the validation failure. Has anyone run into this exact error? What hidden requirements or possible gotchas should I check? Any advice would be greatly appreciated. Thank you.

I'm trying to submit my app's first-ever subscriptions for review, and I'm stuck in a loop between two different App Store Connect submission flows that seem to conflict with each other. Setup: App: HeyFlat (bundle au.com.heyflat) Subscription group "HeyFlat Casa" with 3 auto-renewable subscriptions (monthly/semiannual/annual), all status "Ready to Submit" App version 1.0 has been rejected multiple times (most recently for Guideline 2.1(b) — "In-App Purchase products have not been submitted for review") What I've tried: On the Subscriptions page, I click "Add for Review" on the subscription group → it opens a "Draft Submission" panel (breadcrumb "Submissions") listing the group as an item ready to submit. That panel shows: "Unable to submit for review — Add an app version for the selected platform." I uploaded a brand-new, never-before-submitted build (build 31, version 1.0) via CI and manually attached it to the App Store version page (Distribution → App Store Version 1.0 → Build). Went back to the Draft Submission — same error persists, plus a new one: "New subscription groups must be submitted with an auto-renewing subscription from that group." The item listed is just the subscription group itself, not the individual subscriptions. Separately, the legacy per-version thread (App Review → iOS Submission) now shows build 31 as "Ready for Review" — but that thread only lists 1 item (the app version itself), no subscriptions attached, even though they're marked "Added for Review." So I have: a subscription group with 3 ready subscriptions, and a fresh unreleased build attached to the app version — but no path in the UI actually lets me submit them together. This exact same "In-App Purchases not submitted" rejection has now happened twice, with the subscriptions in this same "ready" state both times. Has anyone run into this specific mismatch between the "Submissions" draft flow and the legacy per-version "App Review" thread? What's the correct way to get a first-time subscription group submitted alongside an app version right now?

Good day, I'm trying to resolve the EU "Digital Services Act" compliance for my employer's Apple Developer account, but I'm stuck on verifying the phone number. The email verification code came through without any issue. We are located in South Africa, with a "+27" area code and the number I need to use here is a landline that comes through to the receptionist at our head office. This number does not have the ability to receive text messages, so I selected the "Didn't get a verification code?" link and chose the receive a phone call instead, however the call never comes through. Calling the number from my cellphone goes straight through to the receptionist, there are no digital switchboard prompts for the caller to select from. I tried this numerous times this Friday just past, and again twice now today, still no luck. I've requested an official document from my manager to see if I can go that route to verify the details, but so far nobody seems to be able to find an appropriate document for me to use... :( Is there anything else that I can do here?

Hello i have paid developers account, setting up my app.. and when I open appstore Connect, I see white page with 1 header menu.. Why?

Hi, I have an iOS app already released on the App Store and I am preparing an update for version 1.1. The problem is that my Mac is currently running a macOS beta. Because of that, the stable public version of Xcode does not work correctly on this system due to version compatibility issues. I can build and archive the app only with Xcode beta. However, when I upload the archive made with Xcode beta to App Store Connect, the upload is rejected because builds for App Store distribution cannot be submitted from a beta version of Xcode. So I am stuck in this situation: stable Xcode cannot be used on my current macOS beta installation; Xcode beta can build and archive the app; App Store Connect does not accept archives built with Xcode beta; the app update is ready, but I cannot submit it. What is the recommended solution in this case? Can I use Xcode Cloud or another Apple-supported cloud build option to archive the app with a stable Xcode version, even if my local Mac is running macOS beta? If Xcode Cloud is the correct approach, how can I enable it when I do not see the Xcode Cloud option inside Xcode and App Store Connect only shows the general Xcode Cloud introduction page? I would like to avoid downgrading macOS if possible, but I need to submit a valid App Store build made with a supported non-beta Xcode version. Thanks.

Hello. I've created an Apple developer account but haven't received any feedback. My account is restricted even though I haven't done anything related to my questions. I submitted support requests with numbers 102925492955, 102925472666, and 102924677966 but still haven't received a response. I need urgent help.

Hello, My app "Glow Mode: AI Skin Scanner" (Apple ID: 6762376419) has been blocked from distribution in all 27 European Union countries for 49+ days due to Digital Services Act trader verification stuck in "In Review" state. Current state in App Store Connect: • Business → Compliance → Digital Services Act: "In Review" since 24 March 2026 • Pricing and Availability → Manage Availability: all 27 EU countries show "Trader Status Not Provided" → "Cannot Sell" • App-level: declared as "trader app" ✓ • Account: published in 148 other countries, all agreements / banking / tax forms verified and Active Apple's stated typical review time is 5 business days. I'm at day 49. Several other developers have reported identical issues in recent threads: • https://developer.apple.com/forums/thread/822744 — DSA Review stuck • https://developer.apple.com/forums/thread/822857 — App not available in EU • https://developer.apple.com/forums/thread/818244 — Review stuck 2+ months I've also filed a support case (ID: 20000114608599) but wanted public visibility in case this is a systemic issue affecting multiple developers. Questions for Apple staff and the community: Has anyone resolved a DSA verification stuck this long? If so, how? Is there a backend status that may already show "approved" while the UI continues to show "In Review"? What is the recommended escalation path beyond the standard support form? Thanks in advance for any insight.

Hi, hoping someone can help with this. I submitted my app on Friday and it was initially rejected asking me to update the privacy policy. I made the changes straight away and resubmitted it. It was then reviewed again and I received another message asking me to confirm whether the pricing was correct. It was, so I replied confirming this within about 20 minutes. Since then I haven’t had any update and it’s now been several days. As far as I can see, there’s nothing else I need to change or submit — they asked for clarification, I gave it almost immediately, and the review now seems to be stuck. The app is already live on Google Play and we’re holding off on marketing and properly launching it until the iOS version is approved, as we want to launch on both platforms together. At the moment, Apple approval is the only thing we’re waiting for. Has anyone had this happen before or know if there’s anything I can do to get it back in front of the reviewer? If anyone from App Review sees this and can help work out what’s happened with the review, I’d really appreciate it. Thanks