Our app has been in review for 7 days with no updates. We’ve followed up by email, phone, and even submitted an expedited request, but haven’t heard back. Can someone clarify why it’s stuck and what we can do to move it forward?

Hello Apple Developer Support, I am facing an issue when attempting to use the App Store Connect API with my API key. While basic access (e.g., /v1/apps) works correctly, any requests related to Certificates, Identifiers & Profiles (CIP) are failing with a 403 Forbidden error. Here are the details of the request and validation results: JWT Details: { "header": { "alg": "ES256", "kid": "2XLW343BLM", "typ": "JWT" }, "payload": { "iss": "9cf6159c-e038-4703-b542-7652242a6dbf", "iat": 1757515277, "exp": 1757516357, "aud": "appstoreconnect-v1" } } Test Results: ✅ /v1/apps?limit=1 → Status: 200 (working) ❌ /v1/bundleIds?limit=1 → Status: 403 Error: Unable to find a team with the given Content Provider ID 9cf6159c-e038-4703-b542-7652242a6dbf to which you belong. ❌ /v1/certificates?limit=1 → Status: 403 Error: This request is forbidden for security reasons. ❌ /v1/profiles?limit=1 → Status: 403 Error: Unable to find a team with the given Content Provider ID. I have already confirmed that: All API keys were generated correctly. All required roles and permissions have been assigned in App Store Connect. It seems that while public access endpoints are functioning, the CIP endpoints are blocked for my account/key. Could you please advise: Why the given Content Provider ID is not being recognized? Whether additional permissions, roles, or configuration are required to enable access to Certificates, Identifiers, and Profiles through the API? If it is possible to reset or refresh my membership/team configuration so that I can successfully access the App Store Connect API endpoints for CIP. Thank you for your support and guidance. Best regards

I've bought the developer account on Saturday. I received a receipt yesterday. My account is still pending. There was a message on Saturday that the verifications might take place up to 48 hours. Almost 100 hours passed.

Hi there, My app update submission was stuck in "Waiting for Review" state for over 80 hours. Yesterday I canceled and resubmitted it again after 3.5 days of inactivity, but this time it still hasn’t moved forward. I'd like to be sure that there is no issues on my side during sending build to review, cuz I noticed that submit app flow was slightly changed a week ago. Usually app update was verified in 10-20 hours, but now it's stuck. Thank you in advance.

项目中未使用UIScene，在iOS26的设备上运行时控制台报错UIScene lifecycle will soon be required. Failure to adopt will result in an assert in the future. 请问如果不使用UIScene，上架APP是否有影响

Hello Apple Developer Community, I’m facing an issue when submitting my iOS app to App Store Connect. ITMS-90429: Invalid Swift Support libswiftDarwin.dylib, libswiftMetal.dylib, libswiftCoreAudio.dylib, libswiftsimd.dylib, libswiftQuartzCore.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreGraphics.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftCoreMedia.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftCoreImage.dylib aren’t at the expected location: /Payload/Runner.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it. My setup: Using Flutter for iOS development Flutter version: 3.32.8 Xcode version: Version 16.3 What I have tried so far: Cleaned build folder: flutter clean Upgraded Flutter and CocoaPods to the latest version. Rebuilt the project using latest Xcode GM version. Verified that Always Embed Swift Standard Libraries is set to YES in Xcode. Reinstalled pods and ensured use_frameworks! is correctly set in Podfile. Despite this, I still get the same error. My questions: What is the correct way to ensure the Swift libraries are embedded in the correct location for Flutter apps? Is there any known issue when building with Flutter and integrating static .a libraries that could cause this problem? Has anyone successfully submitted a Flutter iOS app with external static libraries linked and avoided this error? Are there any manual steps required to fix the location of Swift dylibs during the build process? Thank you in advance for your help!

I've been trying to send an archive with Organizer to iTunes Connect. It's not my first time. I've been doing it for more than a decade. Anyway, when I try to send a package for my new macOS application, Organizer gives me two error messages that I have never seen before. App Record Creation Error App Record Creation failed due to an invalid attribute. The SKU you entered has already been used. App Record Creation Error App Record Creation failed due to request containing an attribute already in use. The app name you entered is already being used for another app in your account. If you would like to use the name for this app you will need to submit an update to your other app to change the name, or remove it from App Store Connect. An odd thing is that, as shown in the screenshot below, Organizer demands that I enter an application name and SKU manually. I've entered the exactly same ones from the App Store Connect page. I didn't see this step on Organizer last month. I'm using a new SKU for this submission. And I don't have an existing application at iTunes Connect with the same application name. I guess it's the same issue that has been reported here.. I have no pending contract issues. How do I send an archive without errors? My Xcode version is Version 16.4 (16F6). Thanks.

Hello, Our auto-renewable subscription products are currently showing as “In Review” in App Store Connect. However, they are not visible in the “In-App Purchases” section of the app version submission, so we cannot confirm or re-attach them to this app version. At the same time, we cannot delete or edit these products while they are in this state. This has left us in a situation where: The IAPs are stuck in “In Review” status, We cannot re-submit or re-attach them, And your review team cannot complete testing because the subscriptions are not yet approved. According to Apple’s own documentation, IAPs that are released with an app version only move from In Review to Approved when the app itself is approved. This means they must be reviewed together. Could you please: Confirm that our IAPs are correctly attached to this app version and will be reviewed together, or Reset their status back to “Ready to Submit” so that we can re-attach them properly to this app version? We want to make sure we are not stuck in a loop where the IAPs cannot be approved until the app is approved, but the app cannot be approved because the IAPs are stuck. Thank you for your help in resolving this situation. Best regards,

During these 60 days, we have attempted to communicate via email and phone, and have also submitted an expedited review request, but we have not received any proper feedback. Could you please let us know why this situation has occurred, and what information we should provide in order to move the review process forward?

I submitted 2 subscriptions along with my new iOS build, reviewer rejected my build because I didn't mention the EULA terms of use link in my app's metadata (description). Now I have added the Terms of use link in description and I have the option to resubmit the app for review, but when I scrolll down on the version page I am not able to see the in-app purchase section anymore as they are in rejected state. When I opened the subscriptions, they showed the "developer action needed' status, I changed the localization description and saved it, now for localization it shows 'Preparing for submission', but the subscription's status still shows 'Developer action needed'. Now, how am I supposed to reattach these subscriptions back to the same build, as the rejection reason was not the issue in my build, so, I want to resubmit the same build with same subscriptions. Help me out.

Lately every app that I submit (games) with in app purchases, always coins , the app gets rejected with: Guideline 3.1.1 - Business - Payments - In-App Purchase Your app uses intermediary currency to purchase items that function as non-consumable products but still does not include a restore mechanism. Users restore transactions to maintain access to content that they've already purchased It baffles me that reviewers think buy different number of coins is non-consumable. I have tried to explain that coins will be used to buy weapons and skins and they will also be earned at the end of every level yet for some reasons they are still rejecting the app. It is absurd. This is the second app that I have to go through with this. The first one they eventually figured it out but this one no.

Hello, My app was rejected, with the reason being given: -- Parts of the app's user interface were still crowded, laid out, or displayed in a way that made it difficult to use the app when reviewed on iPad Air (5th generation) running iPadOS 26.0. Specifically, when viewed on iPad, your app uses only a portion of the screen. It is the same layout as the iPhone 16 on the iPad air, and I know of multiple apps that follow this scheme. I have even sent images. I believe that I am absolutely in the right here. Please do let me know.

Since 1st of September archives uploaded via Xcode 26 beta 7 or builds distributed via CD (fastlane deliver) don't appear in App Store Connect. No errors reported during/after upload process, no e-mails with errors received. Xcode reports successful upload (with a few warnings regarding dSYM) I'm not getting any e-mails with ITMS errors Builds don't appear at in App Store Connect in TestFlight section (not even in "Processing" or "Failed" states). For me it seems like App Store Connect outage but all statuses in https://www.apple.com/support/systemstatus/ are green.

My app update submission has been in the Waiting for Review status for over 72 hours. A few days ago I already canceled and resubmitted after 3 days of inactivity, but this time it still hasn’t moved forward. I’d like to check if there might be any issues on my side that I should address, or if this is just part of the current review timelines. The update includes a critical bug fix, and unfortunately I’m losing users while waiting. Is there anything I can do to help move the review process along, or should I simply continue to wait? The problem is getting more absurd, since it is not a new app submission but an update for already existing one. Thank you in advance.

Hello, Our app gets rejected for the reason that the reviewer cannot purchase the subscription with the message, "Guideline 2.1 - Performance - App Completeness We found that your in-app purchase products exhibited one or more bugs which create a poor user experience. Specifically, we were unable to purchase Auto-Renewable Subscriptions. The app launched back to the rendering when we tap on the "Get started"" When we test this with our sandbox accounts in test flight version, we can see the subscribe pop up showing and purchase successfully. But turns out they cannot. Unfortunately we cannot see the reason why and even after requesting further explanation regarding how to move along, we are not getting any explanations. Our subscription products are submitted in the first time with the app and they are in "In review" state for more than a week. We requested phone calls and wrote messages to reviewers many times but unfortunately there's no help yet.

Our app, submitted on Sept 12, has been stuck in "Waiting for Review" for over 3 days without updates. Please advise or help escalate.

Hi, In the AppstoreConnect website it's possible to retrieve the payments and estimated proceeds. Is it possible to recover it automaticaly with an API ? I saw "Payments and Proceeds" documentation (https://developer.apple.com/help/app-store-connect/getting-paid/view-payments-and-proceeds), and the "Download Sales and Trends Reports" API documentation (https://developer.apple.com/documentation/appstoreconnectapi/get-v1-salesreports). But none can retrieve the amount that Apple proceeds to the bank account. I need this because I sell in different countries with different currencies. And I manage different Apple accounts. Best Regards,

Hey guys, I'm currently building my first app, which is not released yet. Inside the app there is one button that should bring the user to the app's App Store page, if the user wants to rate the app. I have found a way to navigate the user to the App Store page, with the help of the SKStoreProductViewController - https://developer.apple.com/documentation/storekit/skstoreproductviewcontroller. Although I need the App Store ID of my app aka the SKStoreProductParameterITunesItemIdentifier. - https://developer.apple.com/documentation/storekit/skstoreproductparameteritunesitemidentifier My question is now: How can I get my App Store ID if my app is not released yet? When looking into App Store Connect - My App - General Information I see a point called "Apple ID" with an 10 digit code. The description when clicking on the question mark is: "An automatically generated ID assigned to your app". This code looks like the App Store ID, but is it really it? Really appreciate any help!

The app icon of my iPad app appears as a placeholder/template instead of the correct app icon when viewed through the App Store. It is correctly displayed on the website version of the App Store, in App Store Connect, and when running the app. I noticed that another app with the same issue is "Things 3 for iPad." This might be related to the fact that both apps are iPad-only. I implemented a new app icon using the new Icon Composer. Since users can switch between different icons, some are created with Icon Composer and others are still included traditionally within the asset folder. This is my app (Bubbles' Journal): https://apps.apple.com/app/id1547297023

I built the Appvector tool – aso.report, a completely free ASO analysis platform designed to help indie developers easily improve their App Store listings without complex metrics or costly subscriptions. Just paste your app’s URL to get instant insights, multi-country analysis, and actionable recommendations - making ASO simple, accessible, and effective for everyone.