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

App Store Connect displays the In-App Purchases and Subscriptions section on your app's version page when your app has an In-App Purchase or subscription with a Ready to Submit status. To locate the In-App Purchases and Subscriptions section: In Apps, select the app you want to view. In the sidebar, select the app version. On the version page, scroll down to the In-App Purchases and Subscriptions section. For more information, see Submit an In-App Purchase.

Dear Apple Support, I am writing to report a payment issue with my App Store Connect developer account. The latest payment is marked as "Paid" in the Payments and Financial Reports section, but as of today, more than 3 business days have passed and the funds have not yet arrived in my bank account. I have double-checked that my banking information is accurate and up to date. I would appreciate it if you could investigate this issue and provide further clarification on the current status of the payment. Thank you in advance for your support.

I tried to upload my build into testflight with XCode -> Product -> Archive -> Distribute App but this error keeps showing up: "No Team Found in Archive, Use the Signing & Capabilities editor to assign a team to the targets and build a new archive." However, my Apple ID IS connected and the bundle ID is the same as in my App Store Connect. What can I do? I tried deleting all archives, restarting Xcode & my Mac, still nothing happend. I can't get it to upload...

Hi everyone, Not sure if this is a known App Store Connect bug but hoping either someone here has a workaround, or an Apple engineer can help push this along. Background: this is my first In-App Purchase submission for my app. My original binary was submitted without the IAP attached (my mistake, first time doing this), so the app was rejected under Guideline 2.1(b) for referencing a paid feature whose IAP wasn't submitted for review. Since then: The IAP (non-consumable, one-time purchase) is fully configured with a review screenshot and notes, and shows status "Ready for Review" after submitting via "Add for Review" My app version is in a rejected state with an "Update Review" button available The problem: I can't get these two linked together anywhere in the UI. Clicking "Update Review" on the version page resubmits it, but never shows any option to attach the IAP Clicking "Add for Review" from the IAP page opens a Draft Submission, but that draft says "Unable to Submit for Review: To submit your items for review, add an app version for the selected platform," with no version selector anywhere in that panel Tried hard refresh, incognito, different browsers, starting a fresh draft submission. Same result every time. Result: resubmitted the app, got the exact same 2.1(b) rejection again, confirming the IAP genuinely never made it into the review package despite showing as correctly configured on my end. I've seen a few other threads describing what sounds like the exact same issue, where the "In-App Purchases and Subscriptions" section disappears from the version page after a first rejection, and the fix ended up requiring an Apple support agent to manually push the IAP status forward on the backend, without needing another binary. Has anyone found a way to trigger this from the developer side, or is direct support/engineering intervention really the only path? Already have a case open with Apple Developer Support as well, happy to share the Case ID via DM if that helps someone from Apple locate it faster. Thanks in advance for any pointers.

Hi Apple Developer Support, I have been trying to enroll in the Apple Developer Program for the past 3 weeks, but my enrollment is still pending and my web-based order is not being processed. I have contacted Apple Support multiple times, but the issue remains unresolved. Enrollment ID: 2829892W3Q Case #: 20000136812088 @Apple @AppleSupport, could you please review my enrollment and process my web-based order? I would really appreciate it if Apple Developer Support could look into this and help complete my enrollment as soon as possible. Thank you.

App: AI RunCoach — App ID 6782097197, bundle ID com.airuncoach.app, Team ID 4N3X74Y2LF When adding a new build to our External Testing group, TestFlight shows: "Before you can use TestFlight to distribute beta builds of your app, you must renew your Apple Developer Program membership." Our membership is not expired: the Membership Details page shows renewal date 20 June 2027, auto-renew ON, and the €99 fee already paid. We've also checked Agreements, Tax, and Banking — nothing shows as pending or requiring action anywhere. In the meantime, our app has been stuck in "In Review" status since August 3, and TestFlight installations also seem to be blocked. A request for an expedited review produced no result, and a request for a phone consultation did not lead to any contact either. Did anyone else experience this, and could someone advise on how to contact Apple about this? Thanks in advance for any pointers.

Hi everyone, Running into not really sure if it's App Store Connect bug but hoping either someone here has a workaround, or an Apple engineer can help push this along. Background: this is my first In-App Purchase submission for my app. My original binary was submitted without the IAP attached (my mistake, first time doing this), so the app was rejected under Guideline 2.1(b) for referencing a paid feature whose IAP wasn't submitted for review. Since then: The IAP (non-consumable, one-time purchase) is fully configured with a review screenshot and notes, and shows status "Ready for Review" after submitting via "Add for Review" My app version is in a rejected state with an "Update Review" button available The problem: I can't get these two linked together anywhere in the UI. Clicking "Update Review" on the version page resubmits it, but never shows any option to attach the IAP Clicking "Add for Review" from the IAP page opens a Draft Submission, but that draft says "Unable to Submit for Review: To submit your items for review, add an app version for the selected platform," with no version selector anywhere in that panel Tried hard refresh, incognito, different browsers, starting a fresh draft submission. Same result every time. Result: resubmitted the app, got the exact same 2.1(b) rejection again, confirming the IAP genuinely never made it into the review package despite showing as correctly configured on my end. I've seen a few other threads describing what sounds like the exact same issue, where the "In-App Purchases and Subscriptions" section disappears from the version page after a first rejection, and the fix ended up requiring an Apple support agent to manually push the IAP status forward on the backend, without needing another binary. Has anyone found a way to trigger this from the developer side, or is direct support/engineering intervention really the only path? Already have a case open with Apple Developer Support as well, happy to share the Case ID via DM if that helps someone from Apple locate it faster. Thanks in advance for any pointers.

Hi everyone, I am currently experiencing an ongoing loop with Apple Developer Support regarding organization enrollment for our UAE mainland-registered company, and I wanted to see if anyone else has faced this or found an effective workaround. The Issue: Apple's verification team keeps rejecting our corporate documents because they are requesting a "Certificate of Incorporation." However, for a UAE mainland company, the Department of Economy and Tourism (DET) does not issue a separate Certificate of Incorporation. I verified this directly in person at the DET office the official Trade License is the primary legal document that serves as the commercial registration and holds the full legal and operational authority for the entity. Despite explaining this multiple times with each reply, every response seems to loop in a new support agent who doesn't review the established context, leaving us stuck asking for a document that simply does not exist for mainland companies in this region. Looking for Insights: Has anyone successfully onboarded a UAE mainland company recently? How did you navigate or satisfy the "Certificate of Incorporation" requirement? Did you have to request a specific escalation tier, or was there an alternative combination of official documents (such as the Trade License combined with the Commercial Registration/Sijil Tejari) that finally satisfied the review team? Any advice, tips, or experiences from developers who have gone through this in the UAE would be hugely appreciated!

I am an account holder for my Team ID. I have paid Apple Developer Program too! Unfortunately, I see "Join the Apple Developer Program" and getting "Your Apple Account is already associated with the Account Holder of a membership." message. Also, I am getting "Unable to find a team with the given Team ID to which you belong. Please contact Apple Developer Program Support. https://developer.apple.com/support" error when I go to Certificates, IDs & Profiles. Help!!! Give me fix!!

Hello, I renewed my Apple Developer Program membership on July 29, 2026. The payment was successfully processed, I received the invoice and renewal confirmation, and the Apple Developer website shows that my membership is active. For approximately one week, App Store Connect has continued to display this error: Developer Program Membership Expired Your membership has expired, and your apps have been removed from the App Store until you renew your membership. To renew, a user with the Account Holder role must sign in and renew the membership on the Apple Developer website. Because of this incorrect status, I cannot submit apps, and App Store Connect states that my existing apps have been removed from the App Store. I have contacted Apple Developer Support multiple times. I received two responses, but neither addressed the App Store Connect membership-status issue. The renewal itself is already complete; the problem appears to be a synchronization issue between the Apple Developer portal and App Store Connect. Has anyone experienced this situation? How long did synchronization take, and was there a specific support team or escalation path that resolved it? Any advice would be appreciated.

I tried to upload my build into testflight with XCode -> Product -> Archive -> Distribute App but this error keeps showing up: "No Team Found in Archive, Use the Signing & Capabilities editor to assign a team to the targets and build a new archive." However, my Apple ID IS connected and the bundle ID is the same as in my App Store Connect. What can I do? I tried deleting all archives, restarting Xcode & my Mac, still nothing happend. I can't get it to upload...

We are experiencing an issue when inviting a user to join our Apple Developer Program team through App Store Connect Users and Access. The purpose of adding this user is to include them as an internal TestFlight tester after the invitation is accepted. The invited user received the Apple Developer invitation email and clicked the "Accept invitation" link. The invitation link opens the following page: https://appstoreconnect.apple.com/activation_ds?key=... The page displays "Sign in to accept your invitation" and asks the user to sign in with an Apple Account. After the user signs in successfully, the page redirects back to the same sign-in page and asks the user to sign in again. The invitation cannot be accepted, and the user cannot join the Apple Developer Program team. Steps to reproduce: Go to Users and Access in App Store Connect. Add a new user and send an invitation to join the Apple Developer Program team. The invited user receives the Apple Developer invitation email. The invited user clicks the "Accept invitation" link. The page opens appstoreconnect.apple.com/activation_ds. The user signs in with an Apple Account. After signing in, the page redirects back to the same sign-in page. Repeating the sign-in process results in the same redirect loop. Expected result: The invitation should be accepted after the user signs in, and the user should be added to the Apple Developer Program team. Actual result: The page keeps redirecting back to the sign-in page, and the user cannot accept the invitation. Troubleshooting already tried: Safari and Chrome Private browsing mode Clearing browser cookies Signing out of Apple ID before opening the invitation link again Opening the link directly in the browser instead of an email app embedded browser The issue still occurs.

Hi all, Like others my app submission has been stuck in “waiting for review” for weeks. I know initial app reviews take longer than updates, but this has been delayed far too long and makes me concerned about repeating the process in the future. I submitted this app for review back on Feb 10. It was initially rejected for a minor issue, which I resolved and resubmitted the same day. After that, the build remained in “Waiting for Review” for about two weeks with no further communication. At that point I canceled the submission and resubmitted the build, thinking it may have been stuck in the queue (I now know not to do this next time). Unfortunately the new submission has also been waiting for review for another 9 days now with no messages or updates. I’ve contacted app review support as well (case ID- 102826632729). I understand review times can vary, but delays like this make it difficult for developers to plan launches or push updates when the review process is the only path to distributing apps. As paying members of the Apple Developer Program, we rely heavily on this pipeline functioning reliably. Hoping this post will reach someone from Apple who can help move the process along. If any other devs have suggestions/tips that have worked for them, please share so others in this position can become unblocked. Thanks in advance.

After our app review is accepted, it has been stuck in "Processing for Distribution" mode for over 24 hours. Usually we've seen a new app changed for "Processing for Distribution" to "Ready for distribution" in under 10 minutes. Does anyone encounter a similar issue and how to proceed?

I have a very embarrassing problem. that I can't transfer my macOS app to another account. and above is wrong picture. I already tried to delete the apps group. but it doesn't work. this transfer is very important for our team. if anyone can tell me how to do, I will be very grateful.

Our app is live on the App Store, but its two auto-renewable subscriptions have been stuck in "In Review" for over a month. Users can download the app but cannot subscribe — in production, StoreKit only returns approved products, so our paywall shows nothing and monetization has been completely blocked since launch day. APP / PRODUCT DETAILS App: 流动 (Flow) — Apple ID: 6772474397 App status: v1.0.0 (build 625), approved and live since July 23, 2026 Subscription group: "Flow Premium" (ID 22108903) — the group itself shows "Approved" Products stuck in "In Review": com.echo.flow.premium.monthly (1 month) com.echo.flow.premium.yearly (1 year) Paid Apps Agreement is active; banking and tax are complete TIMELINE Jul 12: First contacted Developer Support (Case ID 102939768542). At that time the subscriptions were stuck in "Waiting for Review" and could not be attached to any version submission. Jul 23–24: Followed up; was told the issue had been "escalated to the appropriate internal team". Shortly after, both subscriptions moved from "Waiting for Review" to "In Review" — the only progress in this entire period. Jul 31 → Aug 3 reply, and Aug 7 → same-day reply: two more follow-ups on the same case. Both replies were the identical "escalated to the internal team" template. No one has contacted me since, and the status has never changed. Aug 18 (today): Both subscriptions are still "In Review" — roughly 4 weeks in this state, 5+ weeks since my first support contact. Normal IAP review is said to be 24–48 hours. NO ACTION IS AVAILABLE ON MY SIDE Both subscription pages are locked: I cannot edit metadata, delete the products, or remove them from review. "Add for Review" is greyed out. They cannot be selected on a new app version page (they are not in "Ready to Submit"). So this appears to be stuck inside the review pipeline itself, and nothing in App Store Connect lets me unblock it. REQUEST Could someone from the App Store Commerce / App Review team please either: Complete the review of these two subscriptions, or Reset them to "Ready to Submit" so I can immediately resubmit them — with a new app version if required (build 626 is ready to go). I've seen a very similar case in this forum (thread 818811) resolved after an App Store Commerce Engineer looked into it — I'd be grateful for the same kind of help. Thank you!

Hi all, I want to put the raw numbers somewhere public, because after five days of looking at this I still cannot find an explanation that involves anything on my side. On 2026-08-12, 59 builds across 10 apps on Team ID 8N867LSZDP were marked expired. Not gradually. Inside four seconds: 06:32:56 PDT 22 builds 06:32:57 PDT 9 builds 06:32:58 PDT 18 builds 06:32:59 PDT 10 builds Those 59 builds were uploaded between 2026-05-09 and 2026-08-11, so their own upload dates have nothing to do with when they died. The reason I am sure this is not normal expiry is that normal expiry is visible in the same account, in the same export. Twelve other builds expired between 2026-08-07 and 2026-08-11, each exactly 90 days after its own upload, one at a time, the way the documentation describes. Both groups sit in one table. One follows the rule. The other was written in a batch. It was not only the date, either. buildBetaDetail for all 59 now reports internalBuildState EXPIRED and externalBuildState EXPIRED, so the beta state machine moved with it. Then the second half, which is the part that actually blocks me. The next day, 2026-08-13, I uploaded two fresh builds to one of the affected apps. App Store Connect is perfectly happy with them: processingState VALID expired false expirationDate 2026-11-11 (correct 90-day window) internalBuildState IN_BETA_TESTING internal group hasAccessToAllBuilds = true tester 1, state ACCEPTED Installing either one fails instantly, for the tester and for me on my own device: "Could not install [app]. The requested app is not available or doesn't exist." App Store Connect says the build is in beta testing. TestFlight says the app does not exist. Two Apple systems reading one record and disagreeing about it. Five days on, nothing has moved: those builds are still unexpired and still uninstallable. One detail that might narrow this down for whoever ends up looking at it. I have seen the theory going around that this gets triggered by removing external testers. That is not what happened here. This account has never had external testing configured at all. All fifteen beta groups are internal, publicLinkEnabled is null on every one of them, and each group contains exactly one tester, me. There were no external testers to remove. So whatever runs this batch job does not need that trigger. Checked before posting: membership active, distribution certificate valid through 2027-05-15, provisioning profiles ACTIVE, agreements reviewed, testers removed and re-added, device restarted, app deleted and reinstalled, TestFlight reinstalled, builds re-uploaded twice. Production uploads and App Store review are unaffected, which is what makes this look like the beta path specifically rather than the account as a whole. Developer Support case 20000136966070. The reply I got linked me to Xcode build configuration documentation and suggested I try DTS. I have asked for escalation. The per-app identifiers and the full 74-build export are already attached to that case, so anyone at Apple who needs the specifics has them without me listing my apps here. I also filed it in Feedback Assistant as FB24388441 (Developer Tools & Resources, area TestFlight, Incorrect/Unexpected Behavior), with the same export attached. That part I would ask other people to copy. Feedback Assistant groups duplicates and shows a Recent Similar Reports count, and a forum thread has nothing equivalent. If you are stuck on this, filing one takes ten minutes, and it is the only mechanism I have found that turns a pile of separate complaints into something countable. Thread 813703 carries the same signature going back to January, so this is neither new nor one account. If anyone has actually come out the other side of this: what changed, and how long did it take?

Hello, Apple’s documentation appears inconsistent about which App Store Connect API should be used to submit an Apple-hosted Background Asset version for external TestFlight review: In WWDC25 “Discover Apple-Hosted Background Assets”, Apple says that the asset pack version can be submitted using the POST /v1/betaBackgroundAssetReviewSubmissions. In Uploading and versioning Apple hosted background assets, the external beta review instructions link to “Submit an app for beta review,” which uses POST /v1/betaAppReviewSubmissions. These two resources have different behavior. betaBackgroundAssetReviewSubmissions I called the public API with the same resource structure used by the App Store Connect web UI: POST https://api.appstoreconnect.apple.com/v1/betaBackgroundAssetReviewSubmissions { "data": { "type": "betaBackgroundAssetReviewSubmissions", "relationships": { "backgroundAssetVersion": { "data": { "type": "backgroundAssetVersions", "id": "<BACKGROUND_ASSET_VERSION_ID>" } } } } } The public API returned 404 PATH_ERROR: The resource 'v1/betaBackgroundAssetReviewSubmissions' does not exist. However, the App Store Connect web UI uses the private endpoint below with the same payload and receives HTTP 201: POST https://appstoreconnect.apple.com/iris/v1/betaBackgroundAssetReviewSubmissions The public endpoint is also absent from the current App Store Connect OpenAPI specification. betaAppReviewSubmissions I also tested the public POST /v1/betaAppReviewSubmissions endpoint. When I supplied a backgroundAssetVersion relationship, the API returned 409: 'backgroundAssetVersion' is not a relationship on the resource 'betaAppReviewSubmissions'. You must provide a value for the relationship 'build'. The build relationship only accepts the builds resource type, not backgroundAssetVersions. Therefore, betaAppReviewSubmissions can submit an app build but cannot submit a Background Asset version. Could Apple please clarify: Which public API should be used to submit a Background Asset version for external TestFlight review? Is betaBackgroundAssetReviewSubmissions intended to be exposed through the public App Store Connect API? Is the link to betaAppReviewSubmissions in the Background Assets documentation incorrect? When will the public documentation and OpenAPI specification be updated? Thank you.

Hello, I am facing a critical issue with my Apple Developer Account verification process where an automated timer suspended my account despite submitting all requested documents on day one. Timeline & Details: I received a request from Apple to upload address verification documents with a 14-day deadline. I uploaded all requested documents on the very first day. While waiting for the review process to be completed on Apple's end, the 14-day window expired. Consequently, the system automatically suspended my account, disabling certificate creation and blocking development/distribution. I have open support tickets, but have not received a response yet. Case ID: 102944887663 Since this is an automated timeout caused by review delay, could someone from the Apple team please help escalate this Case ID to the Enrollment / Account Verification team? Thank you very much for your help!

Hello everyone, I'm going through a very stressful situation at the moment. TL;DR: Apple blocked my developer account and won't let me renew it. I complied with every request. I sent every document on time. I did nothing wrong. Team ID: QHC9NAUWK3 My membership expires on August 24. If this isn't resolved soon, my apps will be removed from the App Store, and I will lose my entire income. I enrolled in the Apple Developer Program in August 2025. Since then, I've been dedicated to building apps for the App Store full-time. On June 30, 2026, I received an email from Apple requesting documents to confirm my identity. If I didn't provide them within two weeks, my developer account would be suspended. I provided all the required documents on July 1. I received an automated email confirming that the documents were received and that I should hear back within two days. I never did. Two weeks later, my developer account was suspended. No warnings, no emails, nothing. I opened a support case with Apple. After receiving no response for four days, I got on a call with an Apple advisor. They told me that Apple had never received my documents. Weird, considering I have a confirmation email from Apple proving that wasn't the case. The case was escalated to the Operations team. A week went by without a response. I sent a follow-up email. Five more days went by without a response. I sent another email explaining that my membership expires soon and that I can't renew it. I kept receiving the same template response: "This may take an undetermined amount of time. We can't let you renew your membership during this time. The case is with another team, and we can't do anything else." Apple broke my account and blocked me from renewing it. A few more emails went back and forth without any progress. On August 12, I had another call with a senior Apple advisor. They looked over my case and mentioned that the situation was strange and that the review was taking unusually long. They acknowledged that I had provided everything and that this wasn't my fault. They then "re-escalated" the case to the Operations team. I am quite desperate at the moment. I don't know what else to do. It sucks to lose everything I dedicated the past year of my life to building. I found several other people on the forums dealing with similar problems. More than 50,000 people have read my story on X, and many have shown their support. Apple's own timelines no longer make sense. If they can't verify someone's documents within two weeks, it should at least not disable that person's account.

Hello, My iOS app, CheckMe, has been stuck in “Waiting for Review” since July 28, 2026. App: CheckMe Version: 1.0 Build: 1.0.4 (25) Platform: iOS Submitted: July 28, 2026 Current status: Waiting for Review The submission has now been waiting for approximately 20 days and has never moved to “In Review”. I contacted Apple Developer Support on August 10 regarding the review status. I received an automatic confirmation that my support request was received, but I have not received a response from the App Review team. I have now also sent a follow-up requesting that the case be escalated. There are no messages or requests for additional information visible in App Store Connect, and I am not aware of anything currently required from my side. Could someone from Apple please check whether the submission may be stuck in the review queue, or whether there is anything preventing it from entering review? I can provide the Support Case ID and Submission ID privately if needed. Thank you.