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

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.

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?

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.

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'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!

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.

Hello, I'm hoping someone from Apple or the community can help me get some clarity on my situation. Two months ago, my app was rejected by App Review, and I immediately filed a formal appeal. Since then, I have received absolutely no response — not an acknowledgment, not a status update, nothing. In the meantime, I have also reached out to Apple Developer Support via email on multiple occasions. Again, no response of any kind. I understand that review and appeal timelines can vary, but two months of complete silence — across both the appeal process and direct support emails — makes it very difficult to know whether my case is even being reviewed or if something has fallen through the cracks. If anyone from the App Review team or Apple Developer Relations sees this, I would appreciate any guidance you can offer. And if any developers have been in a similar situation, I'd like to know what worked. Thank you.

Hi, App ID 6756673679 has been approved in prior cycles relatively quickly. The current review cycle began on April 17, and entered "In Review" as quickly as prior submissions. After working through Resolution Center on some items, we spoke with Apple Developer Support on Wednesday (case 102875923017), who applied an expedited flag and advised us to resubmit. It's now been ~27 hours since it was expedited, and ~6 days since the submission cycle began. Would someone from App Review be able to take a look and confirm whether there is any specific blocker or provide any update on expected timing? Thank you.

Our app (id 1611398578) has been stuck "In Review" in App Store Connect for 15 days, after being approved quickly by App Review. We contacted Apple Support multiple times through email and phone, but we did not receive any response. Today we tried re-submitting a new version hoping it will trigger a system reset and fix the issue. The submission for iOS was approved very fast by App Review, but it is again stuck "In Review". PLEASE APPLE HELP US GET THIS ISSUE RESOLVED!

Hello, I have a few questions regarding App Store featuring nominations. -When do applicants receive a response to their nominations? -How is this response provided? Is it via the App Store Connect app page, email, or the nominations section? -For an already published app, can an application for App Launch Nomination submitted 1-2 days after publication be accepted? It says applications must be submitted 3-4 weeks before publication. Thank you for help.

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

My app (Markets: Global Trading 24/7, version 1.0.6, App ID 6756673679) was rejected on April 20 for Guideline 1.2. Apple's rejection message offered the option to demonstrate compliance via a screen recording, which we provided in Resolution Center the same day. The submission has remained in Rejected status while we await a response. Do we need to click "Update Review" to surface this to App Review, or are we supposed to wait in "Rejected" status until we get a Resolution Center reply? Thank you.

Hi all — this is genuinely urgent for us and I'd really appreciate any help. We've been fully blocked from shipping updates for almost two weeks, and Feedback Assistant has been completely silent. Posting here as a last resort to get the issue in front of someone who can route it. Our app (1.0.0 live on App Store, CN region) has a version record stuck in a broken backend state since April 9. Every recovery path fails at the Apple backend layer. Version record ID: 00ae0692-f94d-4632-a369-a9b230788330 Case: #102865399563 Symptoms via ASC web UI: Version shows "Prepare for Submission" Save fails with red error icon, no message shown DevTools Network shows: 409 ENTITY_ERROR.RELATIONSHIP.INVALID on /data/relationships/build "+" button to create next version is hidden while this record is in "Prepare for Submission" state Symptoms via ASC API (all paths tried, all 409): DELETE /v1/appStoreVersions/{id} → 409 STATE_ERROR "Only the first version of any platform can be deleted" PATCH /v1/appStoreVersions/{id}/relationships/build with 4 different valid builds (71 / 73 / 74 / 78) → 409 ENTITY_ERROR.RELATIONSHIP.INVALID on each PATCH with null (clear relationship) → 204 success PATCH to re-set relationship after clear → 409 again GET confirms versionString is still "1.0.3" in backend even though UI shows "1.0.4" after a rename attempt What we need: Either (a) Apple engineering resets this version record, or (b) official guidance that we can abandon it and create 1.0.5 (the "+" button is currently hidden, so this path is blocked from our side too). All builds (71, 73, 74, 78) are VALID in TestFlight. The blocker is purely the broken backend state on this version record — not our builds, not our code. Thank you so much to anyone who takes the time to read this or help route it. If any Apple engineer here can escalate Case #102865399563 to the right team, it would mean a lot — we've done everything we can from our side and are just stuck waiting. Any advice from fellow developers who've seen similar 409 issues would also be hugely appreciated. Thanks again 🙏

Hi everyone, I’m facing a persistent issue where App Store Connect invitations are marked as "Invalid" or "Expired" the moment the recipient clicks the link, even if it was sent just minutes prior. I have already tried the following troubleshooting steps without success: Removed and re-added the user multiple times. Sent invitations to different email addresses (different domains). Changed the assigned Roles (tried Developer and Support). Tried opening the invitation link in Incognito/Private mode and different browsers. Despite these attempts, the link remains invalid. Is there an ongoing server issue or a specific workaround for this? Thanks in advance for any help!

Hello Community I have a current app that is live in production that was last deployed under Account X. I had to change my account name to Account Y so I created a new Account and asked Apple to transfer my app. They have done and I can see my App on the new Account as well as transferring my app id (bundleID) and provisioning profiles. I am trying to push a new version of the app that was transffered but I keep on Running into this error. My Account X has expired but the new Account (Account Y) is valid and has no agreement exceptions on it. Couple of questions The Transfer Status is Active (not complete) is this correct? Is it possible there is still ties to the bundle id to the old Account X that I can no longer see I have a paid agreement present and sitting in New Status under the business page. I do not have any paid app functions on my app.