An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

Hello, I am seeking advice or assistance regarding a significant delay in the review process for my app, Preppy (App ID: 6443527187). The app has been on the App Store for over 4 years and has been featured as "App of the Day" on three separate occasions. We have always maintained a good standing, but we are currently facing an unprecedented bottleneck that is negatively impacting our users. The Timeline: Version 2.6: Approved successfully ~3 weeks ago. Version 2.6.1: Submitted shortly after to address a critical bug. It was rejected due to the screenshots (which were the same as in 2.6), but I changed them according to the feedback. It remained in review for another 7 days. Even after requesting an expedited review, there was no movement anymore. Action taken: I rejected the build and resubmitted with a new build and updated screenshots again, hoping it would help. It sat for another 5 days with no status change again. Phone Support: I spoke with support via phone and was advised to increment the build/version number and resubmit and was told the app is in the expedited queue, so it will be reviewed shortly, which did not happen. Version 2.7: Uploaded 4 days ago with a new version number, updated screenshots yet again, and an improved description. It has been stuck in "Waiting for Review" since then. I have sent multiple emails to the App Review team explaining that this update contains a critical bugfix. Because of this delay, we are now receiving a wave of negative 1-star reviews from users who are experiencing the bug that is already fixed in the pending build. I have had no response to my follow-up emails, and the "Contact Us" forms haven't resulted in any updates. Has anyone else experienced this recently with a long-standing app? Is there any other way to escalate this beyond the standard expedited review form (which has already been used)? Thank you for any help or guidance.

Hello, I have recently received a trademark infringement claim against my app. The claim did not specify exactly how I am infringing, or supply any other actionable information. However they did mention they filed at the USPTO. Nevertheless I pulled my app from the U.S app store to prevent any unintentional infringement, and contacted the complainants to resolve the situation. It's been a few weeks since then and I haven't heard anything from the complainants. Meanwhile Apple is reminding me to resolve this conflict. Does anybody here have any advice on how to proceed? I have tried getting in touch with AppStoreNotices@apple.com but they do not appear to reply. Thanks!

Hello everyone, my initial app release (Version 1.0) has been stuck in the 'Waiting for Review' status for 6 days now. It is a comprehensive app that includes localization for 14 different languages. I understand that initial submissions and extensive localizations can take longer to review, but 6 days seems unusually long. Is anyone else experiencing similar extended delays with App Review recently? Any insights would be appreciated. Thank you.

Please help review app stuck 'Waiting for review'. Let me know if you need anything from us id: 6756242440

I'm trying to distribute one-time use offer codes for a non-consumable IAP, but every redemption attempt fails at the App Store with the error: Unable to Purchase This promotional offer is not available. My setup: the app is in Ready for Distribution state, the IAP is Non-Consumable and Approved, and the offer is a Free one-time use offer available in all 175 territories. I generated a batch of 500 production codes which are active and were created more than 24 hours ago. I've already ruled out the usual suspects: the app is installed from the public App Store (not TestFlight), the test Apple IDs have never purchased this IAP before, the storefront is included in the offer's territories, and the IAP works correctly when purchased at regular price. The error reproduces across multiple users, devices, and Apple IDs, and each failing code is still unredeemed. Has anyone successfully shipped non-consumable offer codes since the October 2025 rollout? Thanks!

Hi, I can sign in to my Apple ID, but my Apple Developer account shows a “closed” status and I’m unable to access App Store Connect features. My app is currently showing “Ready for Distribution,” so the account appears active, but developer access is restricted. I’ve already contacted Apple Developer Support and am waiting for their response. Also, I temporarily can’t access my primary email due to a verification issue, so I’ve provided an alternate contact email and phone number in my support request. Has anyone experienced a similar situation or knows possible reasons for a “closed” developer status while the app remains approved? Thanks.

Is there any way to activate Storekit External Purchase Entitlements in Russian region currently? External Purchase documentation's form link for this specific region is not working. Is there a workaround to register for it?

The In-App Purchases and Subscriptions section is missing from my version page despite having a build attached and subscriptions in Waiting for Review status. This is the same bug reported in Developer Forums thread 820936. I need this escalated so my version 1.0.5 build 6 can be submitted with my subscriptions.

Dear all, This is my first post in this forum - and, in fact, my first app, too! I'm glad to be here, and thanks in advance for your help. I'm looking to offer an app for a one-time payment. I'd also like people to be able to try the app for a week. It seems that the "Pricing and Availability" section in App Store Connect is not the right place to configure this kind of offer. It does allow me to set a one-time price, but I cannot find a trial-period there (or am I missing something?) Two different strategies seem possible here: Using in-app-purchases: make the actual app free, but ask users after a week to buy a non-consumable IAP. The problem with that: I need to verify that the app has been installed for seven days ... even if it has been uninstalled at some point. Using subscriptions: There is a "free trial" option for subscriptions. But after that free trial, subscriptions are being payed periodically. I'd rather have the user only pay once for lifetime-access. Some apps seem to use strategy 1 - I believe the "Lap swim" app does. But still it seems like a bit of a hack - is there a more elegant way to achieve this?

After clicking on our subscription group name, app store connect is hanging and does not load. After a few minutes it will give an error. I've tried on Safari and Chrome and have tried on multiple computers. fter

I have a submission that has been stuck in “Waiting for Review” significantly longer than expected, while other apps submitted from the same developer account during the same period were reviewed and approved quickly (under 2 days). Current pending submission App Store Connect ID: 6760300948 Waiting for Review - Mar 9, 2026 at 4:50 PM Related history (previous record for the same app functionality) App Store Connect ID: 6759011698 Status history: Waiting for Review - Feb 11, 2026 at 1:22 AM Developer Rejected - Feb 28, 2026 at 10:18 AM Ready for Review - Feb 28, 2026 at 11:31 AM Waiting for Review - Feb 28, 2026 at 11:31 AM Developer Rejected - Mar 9, 2026 at 3:13 PM I withdrew that earlier submission out of frustration after attempting to reduce review friction (first by changing metadata/review notes, then by withdrawing it altogether). The current pending submission (ID 6760300948) uses very conservative metadata and includes demo mode to allow straightforward testing. Can the App Review team check why submission ID 6760300948 is not progressing from “Waiting for Review”, and advise what the problem is or what information is needed to move it forward? Related similar thread: https://developer.apple.com/forums/thread/782319

I’m trying to submit the first release of my iOS app together with the app’s first consumable in-app purchases, and I’m stuck in what looks like an App Store Connect state issue. My app was already rejected by App Review because the in-app purchases did not appear inside the app when the reviewer opened the paywall. Current setup: First app release Current app version page: iOS App Version 1.0.2 Current attached build: 5 App has never been released before 4 consumable IAPs: com.glowup.credits.100 com.glowup.credits.500 com.glowup.credits.1000 com.glowup.credits.2500 What I see in App Store Connect: All 4 IAPs show Waiting for Review On the iOS App Version 1.0.2 page, the In-App Purchases and Subscriptions section does not appear at all Because of that, I cannot explicitly select or attach the IAPs from the version page What I’ve already done: Uploaded a new build and attached build 5 to version 1.0.2 Removed my local StoreKit configuration file so the app now uses live App Store / StoreKit only Confirmed RevenueCat is configured correctly and sees the offering/packages RevenueCat logs show the products exist remotely, but StoreKit cannot fetch any live products and returns an “offerings empty / none of the products could be fetched” type error RevenueCat also reports the products are still in WAITING_FOR_REVIEW My questions: If the IAPs already show Waiting for Review, are they automatically linked to the current app submission? Is it expected that the In-App Purchases and Subscriptions section can disappear from the app version page in this state? For a first-release app that was already rejected, is attaching a new build and clicking Update Review enough, or is there another step required to associate the IAPs with the resubmission? Has anyone seen App Review reject an app for missing IAPs while the IAPs were still pending review and not yet fetchable from StoreKit? Any guidance from someone who has dealt with this exact first-release + first-IAP submission flow would help a lot.

Hello everyone, I’m facing an issue with my app "FindUWay" (iOS), and I’m trying to understand if this is related to EU Digital Services Act (DSA) compliance. Current situation: App is approved and published on the App Store All agreements, tax forms (including W-8BEN), and banking info are completed and active App is set to be available in 175 countries, including Malta Issue: The app is NOT available in Malta and shows "App Not Available" on multiple iPhones and Apple IDs. Important detail: In App Store Connect, the only pending item is: Digital Services Act (DSA) compliance → Status: "In Review" since April 5th What I’ve observed: The app works and appears normally in some regions In Malta (EU), it does not open or install properly This seems to affect multiple devices (including iPhone 17 Pro Max) Questions: Is DSA compliance review blocking app availability in EU countries? Is it expected for the app to be unavailable while DSA is still "In Review"? Is there anything else I need to configure or submit? Has anyone experienced delays with DSA review recently? This is impacting my app launch, so any help or insight would be greatly appreciated. Thank you!

Our app PrepAiro: Crack UPSC IAS 2026 (Account: 6741750813) has been caught in a rejection/resubmission loop since April 12, now over 10 days. Timeline: April 12: First rejection received Cycles 1–6: Each rejection addressed per reviewer feedback, resubmitted promptly April 18: Status moved to "Waiting for Review" , no movement since We submitted an expedited review request through Apple Support due to the urgency. This release contains critical bug fixes actively impacting users, but there has been no response or update. We understand review timelines can vary, but 6 full cycles over 10 days with no resolution, and a 6-day stall after the last submission, is unusual. Each resubmission addressed the specific feedback provided, yet the cycle continues. Has anyone experienced similar extended holds recently? And is there any additional channel or escalation path beyond the expedited review request to get clarity on what's causing this? Any guidance from Apple or fellow developers would be appreciated.

its been more than 4 days (i.e. 106Hours) i made payment for my developer account and still didn't received my access. it asked me to wait for 48Hrs and after that i raised a case as well (case ID is 102879074844). no call, no email or any kind of communication. need help with this. anyone else also facing the same issue?

20 days passed since I released the app. According to Trends it has 30+ installs and 10 In-App purchases. When will I finally get analytics? Can't wait to see it, because I'm actively promoting my app and I wish to know the marketing performance. All that I see now in App Store Connect is this message: Other apps have no signs of this issue, I assume that the analytics is missing because the app is new. The question is "when"? :)

Hello, I'm try to Capabilities on the Identifier but I got this error. Any help please?

App Review stuck/stalled — Khalas (App ID 6757966927 Version 1.0.5 - ESCALATION) My app has been blocked in review far longer than usual, and previous channels have not resolved it. My app has an error and I need to roll back and release a fix and I can't because of this review problem. App Name: Khalas Apple ID (App Store Connect): 6757966927 Bundle ID: com.khalas.mobile.khalasapp2 Platform: iOS Team ID: AW8RAKXM5P Submission / review Version submitted for review: [1.0.5] Build number: 19 Current status in App Store Connect: In Review and previously stuck in “Waiting for Review” for over a week Total time in review pipeline: Over 7 days What I’ve already tried Requested Expedited App Reviewl Contacted Developer / App Review support Confirmed there are no unanswered messages in Resolution Center and no missing metadata on my side that I can see. Ask Please look up this submission by App ID 6757966927 and tell me whether: The review is actually active or blocked internally (queue, metadata sync, IAP attachment, etc.), There is a silent hold, duplicate submission, or binary processing issue, Anything specific you need from me (I’ve included identifiers above to avoid back-and-forth). I rely on this CRITICAL release and I’m doing everything I can on my side. I’m asking for a concrete status and, if possible, forward progress on this submission. Thank you

Hello, I'm posting again because my situation has not improved despite previous outreach. My app (ID: 6756186616, iOS 1.3.0) was submitted on March 15, 2026 — over 6 weeks ago. After about 4 weeks in "Waiting for Review," it moved to "In Review" on April 14, 2026. It has now been stuck in "In Review" for two full weeks with no further updates. I opened a Developer Support case (#20000111565861) earlier in the process and was told my submission was being investigated, but I have not received any follow-up communication since. Given Apple's stated review timelines, a 6+ week review with two weeks of silence during the active In Review phase is a serious blocker for an independent developer. I would really appreciate: Any clarity on whether something specific in my submission is causing this delay Whether there is an escalation path beyond Developer Support Whether anyone else has experienced similar timelines recently and how they were resolved Thank you for your time.

I am unable to submit any app for review. Every attempt to add a build to an App Store version results in a 409 error, both through the App Store Connect website and directly through the App Store Connect REST API. Affected accounts: Account 1: My personal Apple Developer account Account 2: A company-owned Apple Developer account where I have Admin access Both accounts are completely separate — different legal entities, different enrollments — but exhibit the exact same behavior simultaneously. API errors observed When calling PATCH /v1/appStoreVersions/{id}/relationships/build: 409 ENTITY_ERROR.RELATIONSHIP.INVALID "The specified pre-release build could not be added." When calling POST /v1/appStoreVersions to create a new version: 409 ENTITY_ERROR.RELATIONSHIP.INVALID "You cannot create a new version of the App in the current state." What I have verified All builds are processingState: VALID and not expired usesNonExemptEncryption: false is set on all builds No build is already attached to another version Build version string matches the App Store version (1.1.0) App bundle ID matches the build bundle ID Localization, review contact details, and keywords are all filled in Banking info in Agreements, Tax, and Banking was recently updated on both accounts Issue persists on both the website and via the REST API, ruling out a browser/cache issue Question Has anyone seen 409 errors affecting two completely separate developer accounts simultaneously? Could there be a platform-level issue with App Store Connect that is not reflected on the System Status page? I opened a support ticket 1 week ago but I only got a reply today and it's just asking for more details.