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

Dear App Store Connect Team! Since Passkeys have been introduced as login option on https://appstoreconnect.apple.com, I am unable to to make use of this new sign in option. I have attached sysdiagnoses, screen recordings, and .har exports in my feedback requests: FB22167539 FB17622414 FB22403813 When I select "Sign in with Passkey", the spinner just keeps spinning. Signing in with password works without issues. I can sign into my Apple ID on other Apple websites using my passkey without problems. Hope that helps! – Frederik

Hi everyone, I’m currently facing an issue in App Store Connect when submitting a build to TestFlight. When I try to complete the “What to Test” section and submit, I get the following error: “There was an error processing your request. Please try again later.” Case details: Case ID: 102871190604 Submitted: April 17, 2026 (GMT+7) Status: No response after 3–4 days This issue is blocking me from submitting the build. What I’ve tried: Retried multiple times Switched browsers (Chrome, Safari) Used Incognito mode Logged out and back in Simplified the “What to Test” text Checked build is processed and not expired I have already contacted Apple Developer Support but haven’t received any response yet. Questions: Is this a known App Store Connect issue? Should I wait for support, or upload a new build? If any Apple staff could help check this case, I would really appreciate it. Thank you.

Hi everyone, I’m getting this error in App Store Connect when submitting a build in TestFlight: “There was an error processing your request. Please try again later.” Case information: Case ID: 102871415765 Contacted Apple Developer Support: April 17, 2026 (GMT+7) It has been 3–4 days with no response so far Where it happens: App Store Connect During the “What to Test” step The build is already processed and available What I tried: Retried several times Switched browsers Used Incognito mode Logged out and back in Simplified the “What to Test” text Checked that the build is not expired This issue has been blocking submission for several days now. Has anyone experienced this recently? Is there any workaround, or should I upload a new build? Thank you.

Hi everyone, I’m experiencing a delay with my app review process and wanted to check if this is normal or if anyone has faced something similar. App Name: Finna: Budget Tracker Here’s the timeline: Apr 13: Submitted → Waiting for Review → In Review → Rejected Apr 15: Fixed the issues and resubmitted → Waiting for Review (since then, ~48+ hours now) Current status is still “Waiting for Review”, and it hasn’t moved to “In Review” yet after resubmission. A few points: -> This is not a brand-new submission (it was previously reviewed and rejected once). -> I addressed all rejection points carefully before resubmitting. -> No major feature changes, just fixes based on Apple’s feedback. Questions: Is it normal for resubmitted apps to take longer than the first review? Does rejection history affect queue priority? Should I wait more or consider contacting Apple Developer Support? Would appreciate insights from anyone who has gone through similar delays recently. Thanks!

Hi everyone, We are currently facing an issue in our App Store Connect account where all of our production apps are suddenly showing the status “Removed from Sale.” This happened unexpectedly, and: We did NOT make any manual changes to app availability No recent app rejections or guideline violations were received Agreements, Tax & Banking section shows no pending actions TestFlight builds are still working fine We also have not received any clear communication from Apple explaining the reason for this. This is affecting all our live apps and impacting business operations. Has anyone else faced a similar issue recently? Could this be related to account-level restrictions or any recent policy updates? Any guidance or suggestions would be greatly appreciated. Thanks in advance!

For the past couple of days having a problem with Xcode 26.4. When I try to upload an archive to App Store Connect, it gets stuck on "Uploading". I see the progress bar about 70% full, and a "Preparing to upload xxxx.ipa" label below. Letting it sit overnight, restarting Xcode, machine, etc. and the same result. Anybody else seeing?

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.

Hi everyone, I am writing this post with the hope that someone from Apple's App Review team, Developer Relations, or the wider developer community can shed some light on what I am experiencing. I have exhausted every official support channel available to me, and I am at a complete loss. ━━━━━━━━━━━━━━━━━━━━━━━ THE SITUATION ━━━━━━━━━━━━━━━━━━━━━━━ I have a v1.0 iOS app that has been stuck in 'Waiting for Review' for 57 days. It has never progressed beyond this status. No rejection. No feedback. No communication. Just silence. I am not here to complain. I am here because I genuinely do not understand what is happening, and I need guidance. ━━━━━━━━━━━━━━━━━━━━━━━ TIMELINE ━━━━━━━━━━━━━━━━━━━━━━━ • Day 1 — App submitted for review. Status: 'Waiting for Review.' • Day 22 — No movement. No feedback. Out of frustration, I made the mistake of doing a Developer Reject and resubmitting. I now understand this was the wrong decision, as it likely reset my position in the queue. • Day 27 — Contacted Apple Developer Support. A Senior Advisor confirmed the app was still in review and said they would reach out to the internal review team. • Day 42 — Still no change. Sent a formal follow-up and escalation request. • Day 44 — A second Senior Advisor responded, confirming they had also forwarded the case to the review team. • Day 57 (today) — The app is still in 'Waiting for Review.' Nothing has changed. Two separate Senior Advisors have each told me they contacted the internal review team. After both of those interactions, nothing changed. ━━━━━━━━━━━━━━━━━━━━━━━ WHAT MAKES THIS UNUSUAL ━━━━━━━━━━━━━━━━━━━━━━━ I want to be clear about something: the app has NEVER entered 'In Review.' It has been in 'Waiting for Review' the entire time. This is not a case of a slow review — it appears the app has never been picked up for review at all. I have checked Apple's System Status page multiple times throughout these 57 days. All services have consistently shown as fully operational. I have not resubmitted again after Day 22. I have been patiently waiting, following the advice given to me. ━━━━━━━━━━━━━━━━━━━━━━━ MY HONEST QUESTIONS ━━━━━━━━━━━━━━━━━━━━━━━ Is it technically possible for a v1.0 app to be permanently stuck in 'Waiting for Review' without any notification or rejection? Could this be a system or queue issue on Apple's end? Is 'Waiting for Review' for 57 days — with no status change and no communication — within the range of what other developers have experienced? I want to understand if this is abnormal. When a Senior Advisor says they have 'forwarded the case to the review team,' what does that actually mean in practice? Is there a way to verify this happened or to escalate further? Is there a formal escalation path beyond Developer Support — for example, Developer Relations or the App Review Board — for situations where standard support channels have not produced any result after nearly two months? Could the app category (social / matching) be the reason for an extended manual review? If Apple requires additional information, documentation, or content moderation policies from developers in certain categories, why is there no notification or communication mechanism to request this? ━━━━━━━━━━━━━━━━━━━━━━━ WHAT I AM NOT ASKING FOR ━━━━━━━━━━━━━━━━━━━━━━━ I am not asking for my app to bypass the review process. I am not asking to skip the queue. I am not asking for guaranteed approval. I understand Apple's review process exists to protect users, and I fully respect that. I am simply asking for ONE of two things: — Either: review the app and give me a decision — approval or rejection, both are acceptable. — Or: tell me if there is a problem, a hold, or something you need from me, so I can act on it. Fifty-seven days of silence, with no path forward, is the one outcome I cannot work with. ━━━━━━━━━━━━━━━━━━━━━━━ A NOTE TO APPLE DEVELOPER RELATIONS ━━━━━━━━━━━━━━━━━━━━━━━ If anyone from Apple is reading this — I am not writing out of anger. I am writing because I am a solo developer who has poured everything into this product, and I am genuinely stuck. I have done everything I was asked to do. I have been patient. I have followed the process. All I am asking for is a resolution — in any direction. If there is anything I can provide — demo account credentials, additional documentation, a content moderation policy, privacy details, anything at all — I will provide it within hours of being asked. Thank you sincerely to anyone who takes the time to read this and share their experience or advice. — Akif Solo Developer

Our app update for Underground Arena (a padel sports community platform) has been pending review for over (65 days), since the first submission on February 11, 2026. At no point has the submission transitioned to "In Review" or received any feedback. The previously approved version (v1.1.2) was reviewed and approved within one day. This update includes security improvements, privacy policy alignment, and metadata updates. No changes to monetization or permissions. We have submitted two expedited review requests and opened support case 102840575585 — none have resulted in movement. We have a padel tournament on April 22, 2026 that requires the updated app for participant registration. Our Android version is already live on Google Play, and iOS users are currently unable to access the latest features. Could someone from the review team please confirm whether this submission is in extended review, or advise on any information needed to proceed? Thank you.

Hi, we have an app which used DeviceID to track users. We had implemented ATT and setup our privacy declaration in ASC accordingly. Now in our new version we decided to not track users anymore. We removed NSUserTrackingUsageDescription, removed ATT permission code and submitted the new version. Now, reviewer has complained that our privacy declaration in ASC still says we are tracking users and refused app acceptance. They told us to update the privacy declaration in ASC. We tried to do so, but ASC does not allow us to remove device ID tracking. It is showing a warning that our app still uses NSUserTrackingUsageDescription and in fact that is true for the production version. We are now in a chicken egg problem. We can't change our privacy declaration in ASC because the production version still uses the feature AND we do not get the new version accepted as long as our privacy declaration is not changed. How can we fix that ? Pls advise !

Hello, I am experiencing an issue when trying to upload my app to App Store Connect via Xcode. I am the Account Holder and Admin of my Apple Developer account, and I can successfully log in to App Store Connect. My account appears correctly under “Users and Access” with full permissions. However, when attempting to distribute my app from Xcode (Product → Archive → Distribute App → App Store Connect), I consistently receive the following error: “App Store Connect access for ‘[my name]’ is required. Add an account in Accounts settings.” “No App Store Connect access for the team” I have already tried the following steps: Verified that my account has Account Holder / Admin role in App Store Connect Logged out and back into Xcode multiple times Removed and re-added my Apple ID in Xcode Restarted Xcode and my Mac Confirmed that my Apple Developer membership is active Checked that all Agreements, Tax, and Banking sections are completed Verified that Apple Distribution and Development certificates are created and valid Ensured the correct Team is selected in Signing & Capabilities Despite all this, the issue persists. It seems like Xcode is not correctly recognizing my App Store Connect access for the team. Could you please help investigate this issue or advise on how to resolve it? Thank you very much in advance.

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

Hi, I’m experiencing a server-side error in App Store Connect when trying to submit a TestFlight build for review. Details: App: Ngoc Rong 2 Platform: iOS Build status: Complete Distribution: External Testing App Store Connect Web (Safari / Chrome both tested) Steps: Go to TestFlight → Select build Click “Submit for Review” Fill in “What to Test” Click Submit Result: Popup shows: "There was an error processing your request. Please try again later." Notes: Build processing completed successfully Internal testing works External group already created Issue happens consistently Tried different browsers and cleared cache Same issue across multiple builds Is this a known App Store Connect issue? Is there any workaround? Additional information: I have already contacted Apple Developer Support. Case ID: 102871190604 If needed, I can provide further details or logs. Thank you.

Hello, I have a perplexing issue with apple reviewers not having the same experience as myself regarding the paywall. This is an Expo app and uses RevenueCat and SuperWall integrations. This app is going through its first review - it is not published yet. So the app and its subscriptions are being reviewed for the first time. I should also mention that this is my first time as an app developer, so please pardon my ignorance. When I install the app from TestFlight and launch it, I see the paywall with the product prices shown and I can complete a test purchase. Same for my friends who I've asked to test for me. But the apple reviewer does not see the product prices when the paywall is shown to them. Without being able to replicate the problem I am flying blind. I don't want to re-submit the app for review only to find the same problem exists. I also need to understand what is different between my testing environment and the apple testers. If anyone can point me in the right direction here I would really appreciate the help!

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!

Hello, I made my app icon with Icon Composer and added the .icon file directly to my Xcode project. I noticed that the icon preview in Icon Composer looks one way, while the icon shown on the App Store looks different. Details: I am using the .icon file directly in the project I am not using an exported PNG for the app icon I did not add a separate background image The background was set with fill in Icon Composer The preview in Icon Composer looks as expected The App Store version has a different appearance I would like to ask whether this difference may come from: App Store processing caching or a recommended Icon Composer setup for background fill If anyone has seen something similar, I would appreciate any guidance. I can also share screenshots of the Icon Composer preview and the App Store result.

Hi everyone, I am facing an issue while configuring an App Clip in App Store Connect, and I am unable to proceed due to a UI crash. Issue When I navigate to the App Clip section under my app version and click on the Subtitle field, the page immediately shows: “We can't process your request.” I am unable to enter any metadata for the App Clip experience. Console Error Previously, I observed the following error in the browser console: TypeError: Cannot read properties of undefined (reading 'appClipDefaultExperience.id')

Hi, My app is waiting for review since Saturday at 5:42 PM, so is TestFlight. It has been rejected a couple of times, and errors were fixed with each update. Is this normal?

Submitted my app and it was approved by Apple. I then downloaded it from the app store and went through onboarding however when I tried to complete a purchase it failed. Went back to app store connect and saw that there is an issue with my subscriptions. Says localization is rejected but does not provide any reason why. Any ideas?? Everything worked fine with sandbox account.

We recently ran into an issue where our submission was rejected due to references to an API that we are not using but that was present in the code. Guideline 2.5.1 - Performance - Software Requirements Issue Description The app uses the Clinical Health Records API but the app does not appear to include any primary features that require the Clinical Health Records API. Next Steps To resolve this issue, please remove the Clinical Health Records API from the app, as well as any references to this app’s interactivity with Clinical Health Records from the app or its metadata. And as it turns out, we actually did have references to that API that we had missed and did have to remove them. Usually, I would recommend to just resubmit the new build and see if it gets accepted, then hold it until the powers that be approve it for publication. For this client, though, their QA team forces us into more of a waterfall-ish approach, where we are not allowed to submit production builds ahead of time (i.e. until after all manual testing has concluded, test evidence has been filed and the required documents have been updated and approved). And if after resubmission we find something else that needs to be fixed, we get to restart the process all over again. That's ... slower. We do have a workaround in place where we submit a development build for review and check whether that would get accepted, then retract that version and submit the production build once we are allowed to. But that means more work for Apple (the App has to be reviewed twice) and more risk for us (if the submission team accidentally publishes a development build, the consequences would be severe). Is there a tool that allows us to check for guideline violations without having to submit a build to the App Store Connect? I'm not looking for a "yes, this will get approved" kind of guarantee, just a "well, the review team may find something else to question / reject, but as far as automated checks go, this looks ready for submission".