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’m trying to enroll in the Apple Developer Program as an Individual / Sole Proprietor, but the enrollment keeps failing. The site shows: “We are unable to process your request. An unknown error occurred.” From the network response, I can see the enrollment request to: https://developer.apple.com/services-enrollment/submitIndividualEnrollment returns: HTTP Code: 406 Result Code: 202018 Result String: “Your request could not be processed” Response ID: c6246a54-354e-4336-a78e-9b4476342ac2 Could you please review my account and check what is causing this enrollment failure on Apple’s side? Thank you.

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.

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 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 devs and Apple support team, I’m waiting for updates on two Apple Developer Support cases: 102870790200 102870755282 Both are related to changing my Apple Developer / App Store Connect region and entity information from UAE to Kazakhstan. The requests were submitted last Thursday (5 days ago), and I still haven’t received any update. This is currently blocking my app release. Has anyone dealt with a similar issue, and is this waiting time normal for this type of request? Thank you very much.

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.

This issue has persisted for a week. Whenever I tap on "View Analytics" in Product Page Optimization, I always get the error: "The page you're looking for can't be found." Is anyone else encountering this issue? Thanks.

Hi everyone, I'm currently experiencing an issue when trying to submit my app/build via App Store Connect. Details: App name: Daily Habit Tracker 2026 Bundle ID: com.DailyHabitTrackerPro.2026 Case ID: 102871415765 Issue: Whenever I try to submit the build (TestFlight / App Review), I get the following error: "There was an error processing your request. Please try again later." This issue has persisted for several days. What I've tried: Retried submission multiple times Waited and tried again later Checked app metadata and settings Contacted Apple Developer Support on April 17, 2026 (no response yet) Question: Has anyone encountered this issue recently? Is this a known backend issue on Apple’s side, or is there anything else I should check? Thanks in advance.

I was invited to join development team. so after receiving mail to my account I clicked accept invitation button in email. but the page of appstoreconnect shows that link is expired or invalid. however admin Is inviting me 2 min ago. how can I solve this problem? what should I do?

Hello, I'm looking for guidance on a submission that appears to be awaiting re-review following my response to a "2.1 Information Needed" message. App: Markets: Global Trading 24/7 App ID: 6756673679 Version: 1.0.6 Timeline (all times ET): Apr 17, 10:45 AM: Submission entered "Waiting for Review" Apr 17, 9:25 PM: Moved to "In Review" Apr 17, 10:14 PM: Received "2.1 Information Needed" message regarding the OTP demo account flow Apr 17, 10:45 PM: Replied in Resolution Center clarifying the OTP behavior Apr 20, 9:10PM: Still awaiting response, and in "Waiting for Review" status The App Review FAQ notes that messages in Resolution Center are generally responded to within 24 hours. My reply has now been pending for approximately 3 full days, so I wanted to check in here in case it would be helpful to surface this. Our prior two updates to our published app were approved quickly, and the 2.1 message concerned the demo account OTP flow, which I responded to in detail in Resolution Center. If anyone from App Review is able to take a look, I would very much appreciate it. Happy to provide any additional information that would help. Thank you, Chuck Bradford Dexari Inc.

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!

I added my first subscription to my app using StoreKit's SubscriptionStoreView. Everything worked as expected in the debug environment and also in TestFlight. So I submitted my app and subscriptions to App Store Connect, got everything Approved and released. After updating my app through App Store and checking the Subscription View, it just says "Subscription Unavailable. The subscription is unavailable in the current storefront." I waited around 3 days and still getting the same message. Now the very strange behavior starts. I went to App Store Connect, I made and edit to the subscription description, saved, removed the edit, saved, and submitted to review. 15 minutes later the subscriptions appear in my app and everything works as expected. After getting the edit approved, the Subscription View in my app again only showed the message "Subscription Unavailable. The subscription is unavailable in the current storefront." No user is able to see the subscriptions anymore, even though it worked as expected before the edit was approved. So I did the same as before. Again, make an edit to the subscription description, save, remove the edit, save, submit to review. 15 minutes later the subscriptions are again available in my app and it works as expected. This is definitely not the expected behavior and submitting the subscription edits every day is wasting the App Review Team's time as well as mine. I contacted Apple Developer Support but I didn't get any reply back (at least yet). I am not the only one experiencing this. I found a friend online who has the exact same issue, and is able to temporarily solve it by making an edit to the subscription description as well. So far it has been a huge headache, and we are losing customers this way. Please if anyone has experience with this problem, or has any suggestions, they will be greatly appreciated. Thank you so much, Tomas

Hello, I’m currently trying to transfer an app via App Store Connect, but I’m blocked by the following message: “App Transfers Disabled for This Account. Due to irregular activity associated with your account, you cannot transfer or receive apps at this time.” The app is fully eligible for transfer: Status: Ready for Distribution Already live on the App Store No pending reviews or configuration issues I have already contacted Apple Developer Support regarding this issue, but it has been over 5 days without any response. This transfer is part of an ongoing business transaction currently in escrow, so the delay is becoming critical. Has anyone experienced this issue before? If so: How long did it take to resolve? Is there any way to expedite the review? I would really appreciate any guidance or if an Apple staff member could help escalate this. Thank you.

Hey everyone 👋 I have 14 years of experience in iOS development, starting in my mid-teens and later working as a senior and lead developer with Fortune 50 companies. Around 1.5 years ago I began my indie journey as a side hustle, and for the past 3 months I have been building apps full time with a growing portfolio and increasing revenue 📈 I currently handle everything myself including development, ASO, and design, with marketing planned for later 🚀 I just shipped a major release last week and taking a relaxed week now, so feel free to ask anything about iOS development, indie life, ASO, monetization, or related topics 💬

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!

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.