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.

I recently submitted a new app for App Review, and it has been in “Waiting for Review” for longer than expected. I understand that review times can vary depending on Apple’s current workload, but I wanted to ask if other developers are currently experiencing similar delays. The submission is still showing “Waiting for Review”, and there are no messages or issues shown in App Store Connect. Is there currently a longer-than-usual App Review wait time? And is there anything I should do while waiting, or is it best to simply wait for the review to begin? Would appreciate any insight from developers who have recently gone through the same situation. Thank you!

Hi my app is still "Waiting for Review" since almost a week now. Is it normal? Thank you!

Hello, I am experiencing a serious TestFlight issue that began immediately after I removed some testers from an External Testing group. Right after removing those external testers, all existing TestFlight builds for my app were suddenly marked as Expired, even though they were still within the normal 90-day TestFlight validity period. I did not manually expire any build. Removing an external tester should only revoke that tester’s access and should not affect the status of any TestFlight build. After the mass expiration, I uploaded a replacement build. The new build uploaded and processed successfully in App Store Connect, but I could not add or submit it for External TestFlight Beta App Review. App Store Connect incorrectly displays the following message: Before you can use TestFlight to distribute beta builds of your app, you must renew your Apple Developer Program membership. However, my account currently shows: Account type: Individual — Account Holder Apple Developer Program membership: Active Apple Developer Program License Agreement: Accepted Free Apps Agreement: Active No pending Apple Developer Program agreements Replacement build uploaded and processed successfully I inspected the failed App Store Connect network request and found the actual backend error: POST /iris/v1/betaAppReviewSubmissions HTTP 422 Unprocessable Content { "errors": [ { "status": "422", "code": "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app.", "detail": "Beta Contract is missing." } ] } The exact sequence was: External testers were removed from the External Testing group. All existing TestFlight builds suddenly became Expired. A replacement build uploaded and processed successfully. The build could not be submitted for External Beta App Review. The backend returned ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING. I have found reports from other developers describing the same sequence after removing external testers, including all TestFlight builds unexpectedly expiring and TestFlight distribution no longer working. This appears to be an account or team-level TestFlight backend issue in which the Beta Contract or distribution state becomes detached after modifying external testers. I have already contacted Apple Developer Support and provided the private account, app, request, and error identifiers through my support case. Could an Apple engineer please confirm whether this is a known backend issue and whether the TestFlight Beta Contract needs to be re-provisioned or re-attached? Has anyone else experienced this exact issue after removing external testers? If Apple resolved it, what action was required on the backend? Thank you.

Product: Auto-renewable annual subscription Environment: Production iOS version: 26.6 StoreKit version: StoreKit 2 I have an active subscription that shows correctly in the App Store app, but neither Transaction.currentEntitlements nor Product.SubscriptionInfo.Status (via subscription.status) return any record of it — both come back empty. What I've checked: Transaction.currentEntitlements — iterated fully, zero transactions found for this product ID Product.SubscriptionInfo.Status — checked independently as a second signal, also returns no active status for this product AppStore.sync() — called before checking entitlements, completes successfully, does not resolve the issue Settings → [Apple ID] → Subscriptions on-device — does not show this subscription "Restore Purchases" in-app — consistently reports nothing found Impact: Since my app gates access behind an active entitlement check, this means the user is stuck on the paywall screen indefinitely, despite having a valid, active, paid subscription. There's no client-side workaround, since every available StoreKit 2 API reports no entitlement exists. Code pattern (simplified): swift for await result in Transaction.currentEntitlements { if case .verified(let transaction) = result, transaction.productID == productID { // never reached for this product } } if let subscription = product.subscription { let statuses = try await subscription.status // statuses is empty / doesn't reflect the active subscription } This looks consistent with the pattern reported in thread 823454, where currentEntitlements and Transaction.all return empty for valid, non-refunded purchases in production for a small number of users. In my case, this is affecting a currently active subscription — not a refunded or expired one — and is reproducible on this account across multiple app builds. Has anyone found a reliable workaround, or is this being tracked by Apple as an active known issue beyond the fix already applied for the non-Gregorian calendar case (which doesn't apply here)?

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.

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

Hi, our organization's Apple Developer Program enrollment was recently completed, but App Store Connect access has never been provisioned, and I'd appreciate help escalating this. Timeline: Organization enrollment verified and completed; "Welcome to the Apple Developer Program" email received more than 50 hours ago Membership shows as active on developer.apple.com under the correct team Apple Developer Agreement accepted; Apple Developer Program License Agreement accepted on August 11, 2026 - no pending agreements are shown on the account page I am the Account Holder, signing in with the same Apple Account that was used to enroll the organization Despite this, signing in at appstoreconnect.apple.com consistently returns: "Your Apple Account isn't enabled for App Store Connect." What I've already tried: signing out of both developer.apple.com and App Store Connect and signing back in via a private/incognito window, different browsers, and navigating to App Store Connect from the developer account page. The error is unchanged. I contacted Apple Developer Support by email (no phone option is available in my region) and am waiting on a reply - case number: 20000135517368 This looks like the known issue where App Store Connect provisioning doesn't trigger for a new organization enrollment. Could someone from Apple take a look or advise how to get the provisioning kicked off manually? Happy to provide the Team ID privately if needed.

Hello! I have a new organization-level Apple Developer account and I'm stuck on the Tax Forms step in App Store Connect (https://appstoreconnect.apple.com/business). The system is showing me U.S. Form W-9 as the only option, but in my case filling out a W-9 would be incorrect — and I'd appreciate guidance from anyone who has resolved this. My setup: I am a non-US individual (not a US citizen, not a US resident, never lived in the US). I am the sole owner of a single-member LLC registered in the US (set up via Firstbase specifically to distribute a mobile app). For US federal tax purposes, this LLC is a disregarded entity — it's not treated as a separate taxpayer from its owner. Why W-9 is not the correct form in my case: The IRS instructions for Form W-9 explicitly state: "If the owner of the disregarded entity is a foreign person, the owner must complete an appropriate Form W-8 instead of a Form W-9. This is the case even if the foreign person has a U.S. TIN." Form W-9 also requires me to certify, under penalty of perjury, that I am a US person — which I am not. The LLC itself doesn't certify anything on a W-9 because it's disregarded; the IRS looks through to the beneficial owner, who in my case is a foreign individual. The correct form for me should be W-8BEN (Certificate of Foreign Status of Beneficial Owner — Individuals). What I've already tried: I opened two support cases 4 days ago and have not received a substantive response yet: Apple Developer Support — Case ID: 20000112974233 Ack Tax / Tax category settings — Team ID: 7YYWN3MYCY, Case ID: 19944616 My questions: Has anyone in the same situation (non-US individual, sole owner of a US single-member LLC) successfully switched the tax form from W-9 to W-8BEN inside App Store Connect? If so, how? Is there a specific path in the Business / Tax Forms section to declare the beneficial owner as a foreign individual that I might be missing? Is there an escalation channel beyond the standard support cases for tax-form issues that are blocking onboarding? Thanks in advance for any pointers.

My developer account is a US single-member LLC owned by a non-US individual. The LLC is a disregarded entity with a valid EIN. App Store Connect only shows me the W-9 workflow. But the IRS instructions for W-9 say: ▎ "If the owner of a disregarded entity is a foreign person, the owner must complete an appropriate Form W-8 instead of a Form W-9" So I legally cannot submit a W-9. I need the W-8BEN workflow enabled. Apple Finance told me all US legal entities must complete a W-9, then suggested I get an EIN (I have one) or change my address. When I sent the IRS guidance, they said their system can't make the change and forwarded it to the tax team. That was May 14 (Case-ID 19771345). Over 15 business days later: no reply, no timeline, and my paid agreement is still inactive. My business is on hold. Has anyone with a foreign-owned single-member US LLC gotten the W-8BEN workflow enabled? Is there any escalation path beyond iTSPayments and the Finance contact form? Both have gone quiet.

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.

Hi, I'm trying to upload my app to TestFlight which contains the new iOS 27 CrashReporterExtension, however I'm getting this error: Invalid Info.plist value. The value of the EXExtensionPointIdentifier key, com.apple.crash-reporter.extension, in the Info.plist of “App.app/Extensions/CrashReporter.appex” is invalid. Please refer to the App Extension Programming Guide at https://developer.apple.com/library/content/documentation/General/Conceptual/ExtensibilityPG/Action.html#/apple_ref/doc/uid/TP40014214-CH13-SW1. I'm guessing App Store Connect has not been updated to accept the crash reporter extension yet? Any idea when uploading an app with this extension will be possible?

I am having an issue with both In-App Purchases and auto-renewable subscriptions using the current App Store Connect submission workflow. My app was previously submitted for review along with its IAPs and first auto-renewable subscriptions. The app itself was approved, but the IAPs and subscriptions were not approved with it. Afterward, the IAPs/subscriptions showed “Developer Rejected.” I did not intentionally reject these products individually. Because App Store Connect states that the first auto-renewable subscription must be submitted with a new app version, I created a new version (1.1.8), uploaded a new binary, and added version 1.1.8 for review. I now have the following situation: • My In-App Purchases show “Ready for Review.” • My subscription group shows “Ready for Review.” • Both auto-renewable subscriptions show “Ready for Review.” • The Add for Review controls for these products are disabled, so I cannot add them to another submission. • App Store Connect shows only one Draft Submission. • When I open that Draft Submission, the only item listed is iOS App 1.1.8. • None of the IAPs, the subscription group, or the individual subscriptions appear in the Draft Submission. Therefore, App Store Connect appears to consider the IAPs and subscriptions Ready for Review, but they are not actually visible in any Draft Submission and I have no way to add them to the 1.1.8 submission. I have tried removing iOS App 1.1.8 from the Draft Submission and adding it again. This does not change the status of the IAPs or subscriptions and does not make them available to add to the submission. I have contacted Apple Developer Support twice, but so far they have not been able to provide a solution. Has anyone encountered this with the new App Store Connect IAP/subscription submission workflow? Is there a way to reset the review/submission state of IAPs and subscriptions that show “Ready for Review” but are not actually present in any Draft Submission? I would strongly prefer to keep the existing product identifiers rather than recreate all of the IAPs and subscriptions.

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.

Hi App Review team, This is my first app submission. SiteLog AI (Apple ID 6768819001), version 1.0, build 56, has been in "Waiting for Review" since August 1, 2026 — about 10 days. The App Review page in App Store Connect shows no messages, no rejection, and no outstanding items, so nothing appears to be needed from me. My developer membership and agreements are active, and the app is not distributed in the EU (DSA declared non-trader). Could someone confirm the submission is queued as expected, and whether anything is needed from me to proceed? Happy to provide any additional detail. Thank you.

Hi, can some one please guide how to contact apple support for the verification process the only way is to contact via email but every time i sent them an email from there website i get an automated reply and no ones contact me it's been days i need to migrate my account from individual to organization already submitted all my details business information D.U.N.S number etc but no luck. Please guide how can we process our request? Thank you

StoreKit 2 returns zero subscription products in Sandbox/TestFlight — FB24199369 I’m experiencing an issue where StoreKit 2 returns zero subscription products in both Sandbox and TestFlight for my iOS app. App: Bundle ID: com.sleeplessnight.naengbiseo Subscription group: Naengbiseo Premium Product IDs: naengbiseo_premium_monthly naengbiseo_premium_yearly Although the production app uses RevenueCat, I reproduced the same issue in a separate minimal native SwiftUI app using StoreKit 2 directly, with no RevenueCat, Expo, React Native, or other third-party SDK involved. Native StoreKit 2 call: let products = try await Product.products(for: [ "naengbiseo_premium_monthly", "naengbiseo_premium_yearly" ]) Current native test result: STOREKIT_COUNTRY_CODE: KOR STOREKIT_STOREFRONT_ID: 143466 DIRECT_STOREKIT_COUNT: 0 Returned products: None Test environment: Physical iPhone StoreKit Configuration: None Sandbox Apple Account signed in Storefront: KOR In-App Purchase capability enabled Correct Bundle ID and Product IDs I have rechecked the following configuration: The subscriptions are available in the test storefront Subscription pricing is configured Subscription localization is configured Paid Apps Agreement, banking, and tax information are active App ID has In-App Purchase enabled The App Store/TestFlight build has the expected Bundle ID, provisioning, and signing configuration I also created a StoreKit Configuration file using “Sync this file with an app in App Store Connect”. The sync completed, but the resulting configuration contained: products: [] subscriptionGroups: [] The same subscriptions also fail to load in TestFlight. The subscription products currently show Rejected in App Store Connect because the associated app version was rejected. App Store Connect states that the subscriptions were returned because the associated app was rejected and will remain Rejected until resubmitted for review. However, App Review also stated: “In-App Purchase products do not need prior approval to function in review.” I have reviewed TN3186 and have not found a remaining developer-side configuration issue that explains why Product.products(for:) returns zero products. Since the issue reproduces in a minimal native StoreKit 2 app, this does not appear to be caused by RevenueCat or another third-party SDK. Feedback Assistant: FB24199369 Could an App Store Commerce / StoreKit engineer advise whether there is any remaining developer-side configuration that could cause this, or whether the subscription catalog / app association may need to be reprocessed on Apple’s side? Thank you.

I’m experiencing what appears to be a team/account-level TestFlight backend issue, and it is currently blocking my development workflow. Team ID: TJ6F83PA4W What happened All existing TestFlight builds across my apps suddenly became Expired / unavailable. This happened across the developer team rather than to one particular app or build. I then uploaded a completely new build to determine whether the previous builds had simply been reset or invalidated. Test app: RESON | See the frequency. Apple ID: 6799940431 Version: 1.0.0 Build: 2 The new build: Uploaded successfully Processed successfully Appears normally in TestFlight Shows a fresh 90-day testing period Has an active Install button But installation immediately fails with: Could not install RESON | See the frequency. The requested app is not available or doesn’t exist. So this does not appear to be normal build expiration. A completely new and successfully processed build is also affected. Troubleshooting / support I have already opened an Apple Developer Support case: Case ID: 20000133520102 I’ve contacted Developer Support multiple times by email and also requested/spoken through phone support, but the issue remains unresolved and is now blocking my TestFlight workflow. I have intentionally not started changing certificates, provisioning profiles, Bundle IDs, or repeatedly uploading replacement builds because the symptoms affect the entire team and appear to occur at the TestFlight distribution stage. I’ve also seen reports from other developers describing similar symptoms, including references to BETA_CONTRACT_MISSING / missing Beta Contract backend state. I cannot confirm that this is the cause on my account, but the symptoms appear similar. Question for Apple / other developers Has anyone experienced this exact combination? All TestFlight builds unexpectedly expire → new builds process successfully → builds appear available for 90 days → installation fails with “The requested app is not available or doesn’t exist.” If someone from App Store Connect / TestFlight engineering sees this, could you please advise whether the Beta Contract / TestFlight distribution provisioning state for the Developer Team needs to be checked or re-provisioned server-side? Any confirmed workaround or escalation path would be greatly appreciated.

Hi, I'm hoping someone from App Review can help, as email support has not resolved this. We publish digital magazine apps where each new issue is sold as a separate in-app purchase. Two of our IAPs have now been stuck in "Waiting for Review" / "In Review" for 3-4 weeks, well beyond the normal 24-48 hour turnaround we've seen on previous submissions. Because of this, we are currently unable to sell our product to paying customers. Readers cannot purchase the current issues at all. This is actively affecting live revenue, not just a delayed update. We've already sent two emails to Developer Support with no meaningful response beyond being asked to keep waiting, and a Contact Us request through App Store Connect has not moved things forward either. Could someone from App Review please look into why these specific IAP submissions have been stuck for so long, and help move them forward? I'm happy to provide the App ID / bundle ID and IAP product IDs privately to a verified Apple team member. Thank you for any help you can offer.

My app store review submission has sat in Waiting for Review for 8 days and has never moved to In Review. Checked and confirmed: Free Apps Agreement active Nothing in Resolution Center No contact from App Review at any point Reviewer demo account verified working end to end against production No builds removed or resubmitted since the original submission Developer Support case 20000132574764 was filed 8 August. No response so far. Is anyone else seeing new-app submissions failing to enter the queue in August? Any guidance on escalating this would be appreciated.