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.

Hello, I am a sole proprietor based in South Korea. My Apple Developer account was originally enrolled as an individual and was later changed to an organization account. When I try to provide new tax information in App Store Connect, the available form appears to treat my business as a corporation and asks me to complete documentation intended for a corporate entity. I do not want to submit a form that may be inappropriate for my actual tax status. I contacted Apple Media Services Finance Support about this issue through the website on September 4, 2026, and received an acknowledgment for Case-ID: 22018889. Because I had not received a substantive response, I submitted another inquiry about the same issue on September 8, 2026, and received Case-ID: 22076834. The second case was a follow-up to the first, not a separate tax issue. As of September 16, I have received only the automated acknowledgments, with no further update or request for information. I have not been able to arrange phone support from South Korea. The acknowledgment emails say I can update each request by replying with the same subject line. Is that the best way to reach the tax team or escalate this tax-form classification issue? If an Apple staff member sees this post, could you please check the status of both cases (22018889 and 22076834) and let me know whether further information is needed or what the next step should be? I would also appreciate hearing from anyone who has dealt with a similar individual-to-organization change as a Korean sole proprietor. I can provide business documents privately to Apple Support if needed. I will not post tax identifiers or account details publicly. Thank you.

I’m unable to add several older In-App Purchases and auto-renewable subscriptions to an App Review submission in App Store Connect. The UI only shows: Unable to Add for Review Something went wrong. Try again. However, checking the failed reviewSubmissionItems requests in the browser dev tools shows HTTP 409 responses indicating that the existing IAP/subscription versions use an older format that is no longer supported for review submission. The affected errors include: STATE_ERROR.SUBSCRIPTION_VERSION_NOT_SUPPORTED Subscription version '[REDACTED]' is using an older format that is not supported for review submission. Please update before submitting. STATE_ERROR.SUBSCRIPTION_GROUP_VERSION_NOT_SUPPORTED Subscription group version '[REDACTED]' is using an older format that is not supported for review submission. Please update before submitting. STATE_ERROR.IAP_VERSION_DATA_SCHEMA_NOT_SUPPORTED In-app purchase version '[REDACTED]' is using an older format that is not supported for review submission. Please update before submitting. In my case, this affects: 3 older subscription versions 1 subscription group version 1 older IAP version All required metadata in App Store Connect is complete. The interesting part is that I can create a new IAP today and add it to the same review submission successfully. Only the older IAP/subscription records fail. I can’t find any option in App Store Connect to “update” or migrate these legacy versions to the newer format referenced by the error message. Has anyone found a self-service way to migrate/regenerate these older IAP/subscription versions, or does this require Apple to update the records server-side? I’ve already opened a support case with Apple (ID: 102963040418), but wanted to check whether others are seeing the same issue.

Hello, I’m looking for some advice regarding a TestFlight Beta App Review issue. My app, MyStory, was rejected twice under Guideline 2.1(a) with the same general message: App Review was unable to successfully access all or part of the app. In the first review, Apple specifically asked us to provide a demo account with content demonstrating the app’s functionality. We followed those instructions for Build 3: • Created a dedicated demo account with sample content in all four sections. • Added the username and password under Beta App Review Information. • Added testing instructions. • Replied to App Review with the credentials and instructions. Build 3 was nevertheless rejected again under the same Guideline 2.1(a), without specifying which part of the app was inaccessible. We have tested the app and the demo account ourselves, and everything works as expected on our devices. The app can also be used without an account, and users can create an account directly within the app. We have now replied to App Review asking them to identify the specific screen, step, or functionality they were unable to access. We are currently waiting for a response. Has anyone experienced a similar situation? In particular, I would appreciate advice on how to get a more specific explanation from App Review, or whether there is an appropriate way to escalate the issue if they cannot identify what was inaccessible. I’m also wondering how reliable the 24-hour response timeframe is in practice. It has now been more than a day and a half since I replied to App Review. Should I expect a response within a few days, or can Resolution Center replies sometimes take considerably longer? Thank you.

Our build was rejected under Guideline 2.3.2 (Accurate Metadata) over subscription promotional images that were flagged as duplicates of, and too similar to, our app icon. The rejection was against the build, not the subscriptions directly. At the time, all five subscriptions plus the subscription group were in "Submitted for Review" status, which meant they couldn't be edited directly. Troubleshooting steps taken so far: Developer-cancelled each of the five subscriptions to get them out of "Submitted for Review" and into an editable state. Edited each subscription to remove the promotional image that triggered the 2.3.2 flag. Made changes to the Localization and Review Information fields on each subscription to force a new Save action. The Save completed successfully with no errors on any of the five subscriptions. After this, all five subscriptions and the subscription group are showing "Removed" from the Review Status column of our iOS submission. However, "Developer Rejected" status still shows in the Subscriptions section of Monitization (ASC->Distribution). That status hasn't cleared despite the successful edit and save, and I'm not able to reattach the subscriptions to a build for a new review submission from this state. Has anyone run into this — a subscription that was developer-cancelled, corrected, and successfully saved, but remains stuck on "Developer Rejected" instead of returning to a submittable state? Is there a separate action needed beyond edit-and-save (e.g., a distinct resubmit step, or removing and recreating the subscription) to move it forward from here? Any guidance on the correct path would be appreciated — happy to provide additional screenshots or details if useful.

My iOS app has passed App Review and is marked “Ready for Distribution,” but App Store Connect does not allow me to release it because the App Store Version Release controls are disabled. App Review is closed and the Resolution Center is unavailable. I have submitted multiple Apple Developer Support cases and called phone support, but the issue remains unresolved. This appears to be an App Store Connect backend state issue affecting a first-time app with subscriptions. Can Apple engineering assist in unlocking release permissions for iOS version 1.0?

Hello, I would like to ask the App Review team to look into a first submission that has not moved for nine days. Apple ID: 6792008109 Platform: iOS Submission: version 1.0, submitted August 30, 2026 Current status: Waiting for Review (has never transitioned to In Review) There is nothing pending on my side: No rejection and no message in the Resolution Center No metadata issue flagged No request for additional information Agreements, Tax and Banking complete App Privacy completed and working demo credentials provided I have also submitted an expedited review request through the Contact Us form. I understand review times vary with submission volume, and I am not asking to skip the queue. I am asking for visibility on whether this submission is queued normally or sitting in an error state, since nine days with no transition is well outside the expected range. Could the App Review team please investigate? Thank you.

Hi everyone, I'm hoping someone from Apple or another developer has seen this before because I'm completely blocked from submitting my first auto-renewable subscription. Setup First app submission App version: 1.0 (Build 34) One auto-renewable subscription Five consumable IAPs Everything configured in App Store Connect StoreKit works correctly in TestFlight Subscription purchases complete successfully in TestFlight RevenueCat configuration has been verified Subscription review screenshot is uploaded and processed successfully Problem App Store Connect shows: "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." The draft contains: App Version 5 Consumable IAPs 1 Subscription When I submit through the App Store Connect API I receive: STATE_ERROR.SUBSCRIPTION_SUBMISSION_REQUIRES_GROUP_VERSION A subscription must be submitted with its subscription group version when the group has no prior approved version. That makes sense because this is my first subscription. However, when I attempt to create a subscription group version I receive: STATE_ERROR.ALREADY_EXISTS Version already exists. There is already an inflight version with id: bf2f7b5b-7fbd-44fc-9c67-af1297f3d76a So I then attempted to add that existing SubscriptionGroupVersion to the review submission. Apple responds with: STATE_ERROR.SUBSCRIPTION_GROUP_VERSION_NOT_SUPPORTED Subscription group version bf2f7b5b-7fbd-44fc-9c67-af1297f3d76a is using an older format that is not supported for review submission. Please update before submitting. and also: STATE_ERROR.SUBSCRIPTION_GROUP_VERSION_INVALID_STATE Subscription group version bf2f7b5b-7fbd-44fc-9c67-af1297f3d76a cannot be submitted. Only versions in Prepare for Submission or Developer Rejected can be submitted. The issue I'm now stuck because: Apple says I must submit a SubscriptionGroupVersion. Apple says one already exists. Apple will not allow me to create a replacement. Apple will not allow me to submit the existing one. Apple says the existing one is using an older format. I cannot find any way in App Store Connect to update, replace or delete this SubscriptionGroupVersion. Things I've already verified Build 34 is attached correctly. Subscription Product ID is correct. RevenueCat configuration is correct. StoreKit loads the subscription successfully. Purchases work in TestFlight. Subscription review screenshot exists and is COMPLETE. Localizations, pricing and availability are all configured. The issue occurs both in App Store Connect and when submitting via the App Store Connect API. Question Has anyone encountered this before? Is there a way to regenerate or migrate a SubscriptionGroupVersion into the new format from App Store Connect, or is this something Apple Developer Support has to reset on the backend? Any advice would be greatly appreciated. Thanks!

Hello Apple Developer Support Team and Developer Community, We are seeking assistance regarding our app review status. App ID: 6758329405 Our updated version was submitted for App Review, but it has remained in “Waiting for Review” status without any progress or feedback. We have also contacted Apple through the available support channel to request assistance, but unfortunately, we have not received a response or status update so far. This has become increasingly urgent because our app is planned to support an offline bicycle exhibition and promotional event around October 1, 2026 (China’s National Day holiday). We have already completed significant preparations for the event, and the updated app is an important part of our overall launch and exhibition plan. We fully understand that Apple needs time to review every submission, and we are not asking for preferential treatment. Our main concern is that we currently have no information about the status or expected progress of the review. Could an Apple representative please help check the status of App ID 6758329405 or advise us on the appropriate way to obtain an update from the App Review team? As October 1 is approaching, any assistance or status information would be greatly appreciated. Thank you very much for your help.

Our first iOS submission has been "In Review" for 8 days with no update, no Resolution Center message, and no request for additional information. App: Lossic Apple ID: 6806576247 Version 0.2.0, build 31 Submitted: 2026-09-06 (In Review since shortly after) Bundle is a universal record (app.lossic.Lossic). The macOS version of the same record was submitted and approved normally during this same period, so this appears to be a procedural stall on the iOS review specifically, not a content issue. I contacted the App Review team (case 102957178109) 3 days ago and have not received a reply. Could App Review please look into why the iOS review has not progressed? Happy to provide any additional information needed. Thank you.

Apple ID: [6768179663] First submitted for review: 2026-08-31 Status changed to "In Review": 2026-09-02 Current status: In Review — 14 days with no status change Submission contents: app version + 6 in-app purchase / subscription items Resolution Center: no messages from App Review App Review Status case: opened [2026-09-09], Case ID 102957220208, no reply yet Context: this is our first submission. The app includes UGC (community posts, comments, and user reporting) and AIGC, which we understand may require additional review time. Question for the App Review team: is this submission currently assigned to a reviewer and being processed, or is it sitting in the queue? And is there anything on our side — review notes, demo account access, or a specific guideline item — that we should provide in order to unblock it? We are not requesting an expedited review. Demo credentials, screenshots, or a walkthrough video can be supplied on request. Curious whether other developers are seeing similar In Review wait times this month.

I am new and submitted an app which got reviewed twice over the last 2 weeks. I tried adding IAP in the 2nd submission but it didn't get attached. I created 3rd submission and the status says Ready for Review. The IAP says (Unable to Submit for Review To submit your items for review, add an app version for the selected platform.). There is no option to cancel the submission and restart. Previous review cycles showed "Waiting for Review" and "In Review" before I got response on reasons for rejecting the app submission. But now it appears to be stuck. I requested email support. Is there any solution that I am missing? Thanks for your help! Raja

I'm hoping someone from Apple engineering can help, as support tickets and callbacks have not resolved this issue. The problem: My app "Brutal Time - Typographic Clock" does not appear in App Store search results at all — not even when searching for its exact name "Brutal Time." This has been ongoing for over six weeks. Additionally, the app does not appear in Apple Search Ads when I try to set up a campaign — suggesting this is a backend indexing issue, not a ranking issue. Timeline: Dec 17, 2025: App launched, initially searchable Dec 31, 2025: Transitioned to freemium model, became invisible in search. Jan 5, 2026: Fixed the issue, submitted update (v2.02), approved same day Jan 14, 2026: Submitted metadata update (v2.03) to improve discoverability, approved same day Feb 8, 2026: Tried removing from sale and re-adding to force re-index — no effect Feb 10, 2026: Still not appearing in any search results What I've tried: Submitted multiple support tickets (most recent: Case #102797235758) Each ticket generates an automated reply stating Apple will respond within 2 business days — they never have Requested and received callbacks multiple times, was told it would be escalated to US engineering team. But no follow-up, no resolution, no explanation Removed from sale and re-added to attempt to force re-indexing — didn't work App shows "Ready for Distribution" in App Store Connect Direct link works fine: https://apps.apple.com/us/app/brutal-time-typographic-clock/id6756289461 Response from Apple Support: "The behavior you observed is expected. App Store charts and search results change regularly and we don't guarantee app placement." This response misses the point entirely. I'm not asking about rankings — I'm asking why the app is completely invisible in search, including for its own branded name. This is not an isolated issue. Other developers have reported the same problem with the same non-response from Apple: https://developer.apple.com/forums/thread/803937 https://developer.apple.com/forums/thread/73981 https://developer.apple.com/forums/thread/74110 Has anyone found a resolution? Is there any way to trigger a proper re-index, or escalate to someone who can actually investigate?

Dear Apple Developer Support Team, I am writing to urgently escalate my Apple Developer Program enrollment issue regarding Case Number 20000132030420. I have been trying to enroll in the Apple Developer Program for almost two months, but my enrollment is still pending. I have contacted Apple Support multiple times and followed the instructions provided, but unfortunately, I have not received any meaningful update or resolution. More than a month ago, I was asked to submit my government-issued ID for verification, which I submitted as requested. Since then, I have received no update regarding the status of my enrollment. I have also attempted to contact support regarding this case, but my messages have not received a response. This prolonged delay is extremely frustrating and is preventing me from moving forward with my development work and publishing plans. I have been patient and have followed every step requested by Apple, but after nearly two months without a resolution, I am requesting that this case be urgently escalated to the appropriate team and that my enrollment status be reviewed. Please provide me with: An update on the current status of my enrollment. Confirmation that my submitted government ID has been received and reviewed. The reason for the continued delay, if applicable. A clear timeline for when my Apple Developer Program enrollment will be completed. I sincerely hope @Apple @Support can look into this matter and resolve it as soon as possible. This is now my last option to reach out again for support, as I have already spent considerable time trying to resolve this through the existing support channels. I would greatly appreciate a prompt response and resolution to Case #20000132030420. Kind regards,

All auto-renewable subscriptions for Domiai (bundle app.domiai, App ID 6799989904, group 22305757) stay MISSING_METADATA via ASC API for weeks. Metadata complete for each product: fi+en-US localizations, group localizations, pricing, multi-territory availability, review screenshot COMPLETE (1290×2796). Business (Paid Apps, Banking, Tax, DAC7) all Active. Even a newly created control product domiai_meta_unstick_monthly (6801762338) with full config is also MISSING_METADATA. TestFlight StoreKit / RevenueCat: “products could not be fetched”. Feedback: FB24775023 Support case: 20000138025601 (closed without investigating ASC state) Has anyone seen MISSING_METADATA persist after Paid Apps became Active with screenshots+localizations complete? Any known account-level unblock? Product IDs: domiai_plus_monthly/yearly, domiai_ai_monthly/yearly.

Hi everyone, I’m looking for guidance regarding an unusually long App Review delay. My first iOS app, EmpowerFI, has been in “Waiting for Review” for almost 30 days. In two days, it will reach a full month without moving to “In Review.” During this period, I have contacted Apple Developer Support several times. After my initial contact, Apple submitted an expedited review request as a one-time exception for my app. However, the status did not change. I contacted support again and received the following response: “We have confirmed that your app review is proceeding normally, and there is no further action you need to take.” I have followed up multiple times since then, explaining that I am not asking Apple to guarantee a review or approval date. I am simply trying to understand why this particular submission has remained in “Waiting for Review” for almost a month. Unfortunately, I continue to receive essentially the same standard response. There are no pending actions visible in App Store Connect, and Apple Support has explicitly confirmed that there is nothing further required from me. I fully understand that review times vary and that some apps may require additional scrutiny. However, almost 30 days without even moving from “Waiting for Review” to “In Review” seems exceptionally long, particularly after an expedited review request was submitted. I also know developers who submitted apps during this period and received a review response within approximately two days, so I am trying to understand whether there could be something specific affecting my submission. Has anyone recently experienced a similar delay with a first app submission? More importantly, is there any other appropriate escalation path when Developer Support confirms that everything is normal but the app remains in “Waiting for Review” for almost a month? I am not looking to bypass App Review or request guaranteed approval. I would simply like someone to investigate whether there is an issue affecting this submission or explain why it has remained in the queue for such an exceptional amount of time. Any guidance from Apple staff or developers who have experienced this recently would be greatly appreciated. Thank you,

I've been trying to understand why data from the Appstore Connect API is highly inflated when compared to the same data and same period/filters from the Appstore UI. Has anyone any idea why I am experiencing such inconsistencies?

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, I am experiencing persistent ITMS-90034 when trying to upload the first iOS app from a newly enrolled Individual Apple Developer Program account. The exact error is: Validation failed (409) Missing or invalid signature. The bundle at "Payload/[App].app" is not signed using an Apple submission certificate. (ID: 90034) I have already performed extensive signing checks and troubleshooting: Apple Developer Program membership is active. A valid Apple Distribution certificate is installed in Keychain together with its private key. security find-identity -v -p codesigning reports both Apple Development and Apple Distribution as valid identities. The correct Team and Bundle ID are selected. Automatic signing is enabled in Xcode. Provisioning profile caches and DerivedData were deleted, profiles were downloaded again, and a completely fresh archive was created. Xcode's App Store Connect export review explicitly shows: Certificate: Apple Distribution App Store provisioning profile for the correct Bundle ID get-task-allow = false beta-reports-active = true I then exported the IPA locally using Xcode's App Store Connect distribution workflow and independently inspected the actual exported binary with codesign. The main application reports: Identifier=[Bundle ID] Authority=Apple Distribution: [Name] ([Team ID]) Authority=Apple Worldwide Developer Relations Certification Authority Authority=Apple Root CA TeamIdentifier=[Team ID] I also separately checked the embedded Capacitor.framework and Cordova.framework. Both are signed with the same Apple Distribution identity and Team ID and show the same WWDR -> Apple Root CA trust chain. I checked Keychain as suggested in similar forum discussions. The Apple Distribution certificate has its private key, the WWDR intermediate certificates are present and valid, and certificate verification reports: "...certificate verification successful." Despite all of the above, a fresh upload from Xcode Organizer still consistently fails with the same ITMS-90034. This appears very similar to other recent reports involving newly enrolled Individual Developer accounts where correctly signed binaries are rejected by App Store Connect. I also opened an Apple Developer Support case (case 20000149684934). So far I have received general signing/troubleshooting documentation, but the issue remains unresolved. At this point, is there any additional local signing verification I should perform, or could this indicate an account/team-level App Store Connect signing validation issue that needs to be investigated on Apple's side? I would especially appreciate guidance from Apple DTS on what diagnostic information would be useful to distinguish a local certificate-chain issue from an App Store Connect/account-side validation issue. Thank you.

Has anyone observed the intermittent issues with the AppStore Connect site? Missing app records and error banners where information should appear “Your account cannot be found” error “Please accept these terms and conditions” Could this explain why some apps remain in review or seem to wait indefinitely—perhaps due to suppressed technical bugs or errors in the site’s processing of changes, where end-to-end flows fail to complete what would otherwise yield a finished review?

My macOS app update has been sitting in "In Review" since Aug 31 at 12:50 PM PT — 13 days — with no messages, questions, or status changes in App Store Connect. ▎ App: NFS Files – NAS Drive Client ▎ App ID: 6789844265 ▎ Platform: macOS, version 2.0 (build 9) ▎ Submission ID: ac1eccf9-a982-492c-a6c4-c402c5f91d29 ▎ The identical iOS 2.0 submission, with the same review notes, was reviewed and approved on Sep 6. The earlier 4.3(a) concern on both platforms was addressed by removing the other network-file apps from my account and by the NFS-specific functionality described in the review notes. ▎ I've also submitted a request through the Contact Us form. Is the review still active, or is anything needed from me?