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 posting here because I no longer have access to the communication channels that were previously available to discuss my developer account with Apple. My appeal was denied, but Apple informed me that I could submit a reinstatement request after addressing the concerns that had been identified. Following that communication, I spent considerable time reviewing my applications, metadata, screenshots, codebase, user flows, and business practices. Although I do not believe my account was involved in dishonest or fraudulent activity, I nevertheless made extensive changes in an effort to address any potential concerns Apple may have had. The main difficulty is that the specific conduct that led to the termination decision was never clearly explained to me. Apple cited Section 3.2(f) and provided examples of prohibited behavior, but did not identify which specific action or activity was associated with my account. As a result, I was left attempting to correct every possible issue without understanding what the actual concern was. In addition, throughout my participation in the Apple Developer Program, I had never previously encountered a notice, suspension, or similar action of this nature. This made it even more difficult for me to understand what specific issue Apple believed had occurred and how best to address it. While I was still implementing changes and preparing what I believed would be a reinstatement submission, I received a termination notice. Since the termination, I have lost access to the Contact Us page and the communication channels that were previously available to me. I would therefore appreciate guidance from Apple or from developers who may have experienced a similar situation: How is a developer expected to submit a reinstatement request after termination if the Contact Us page is no longer accessible? Is there an alternative channel through which reinstatement requests can be submitted? Has anyone successfully submitted a reinstatement request after account termination and received a review? I am not asking Apple to reverse its decision through this forum. I am simply trying to understand how a developer is expected to submit a reinstatement request after termination when the previously available communication channels are no longer accessible. Thank you for your time.

Hi, Recently our App is facing a generic error with no error details. This error is happening once Build has been successfully uploaded to AppStore Connect through Xcode Organiser. Steps followed while uploading the build: Archive the Build through Xcode Once Archive is successful, Distributing the App through Xcode Organiser using AppStore Connect distribution method. Build Uploaded successfully to AppStore Connect After 5 min we are receiving a email with below message Hello, We noticed one or more issues with a recent delivery for the following app: AppName App Apple ID 2121111 Version 3.6.9 Build 75 Please correct the following issues and upload a new binary to App Store Connect. ITMS-90755: Invalid Binary - The following binaries in your app contains prohibited instructions: AppName.app/AppName. Remove the instructions from the binaries, rebuild and resubmit. Apple Developer Relations Solutions tried till now Updating Xcode to latest version of 16.4 Recreating new Distribution certificates and Provisioning Profiles Clearing DerivedData and cleaning Build Folder This issue seems to be occurring recently only since launch of Xcode 16.4 Other Device info Macbook Pro macOS: Sequoia 15.5 Xcode: 16.4

Hi everyone, I’m facing an issue with the App Store review / support process and would really appreciate some guidance from others who may have experienced something similar. I have contacted Apple Developer Support multiple times regarding my app, but unfortunately I have not received any meaningful response so far. At this point, I am unsure how to move forward or how to get proper feedback to resolve the issue. The lack of response is making it difficult to proceed with my app submission and address any potential problems on Apple’s side. Has anyone encountered a similar situation? How did you successfully escalate the issue? Is there a specific way to get a response from the review team or developer support? Any advice on how to move forward would be highly appreciated. Thank you in advance!

Filed: FB23052931 (Feedback Assistant, 2026-06-10) + Apple Dev Support Case 102913469272. Question for the community: Has anyone else hit this and resolved it? TestFlight beta feedback (screenshot submissions) for one of our apps stopped being recorded in App Store Connect at 2026-05-31 17:15:54 UTC. Testers submit screenshot + comment via TestFlight "Send Beta Feedback" — the dialog completes successfully and dismisses with no error — but submissions never appear in the ASC web UI under TestFlight / Feedback / Screenshots or in the App Store Connect API endpoint GET /v1/apps/{id}/betaFeedbackScreenshotSubmissions. meta.paging.total has been frozen at 882 for 10+ days. Verified live by submitting two screenshots from a current TF build today and confirming the API total did not increment seconds later. The betaFeedbackCrashSubmissions endpoint is also stale on this app (last entry 2026-05-03), which makes me think it's the whole beta feedback ingestion pipeline for this app record, not screenshot-specific. Minimal repro: 1) Install a current TestFlight build (any from a current train, processed VALID, internalBuildState IN_BETA_TESTING, delivered to a tester group). 2) Take a screenshot inside the app. 3) From the share sheet, tap "Share Beta Feedback". 4) Add a comment, tap Submit. Dialog completes successfully. 5) Query the App Store Connect API: GET /v1/apps/{id}/betaFeedbackScreenshotSubmissions?limit=200. meta.paging.total is unchanged. data[0].attributes.createdDate is unchanged. Developer-side causes I've already ruled out: Build processing: all 10 most-recent builds are VALID with internalBuildState IN_BETA_TESTING and were delivered to both internal and external tester groups. Per-group Tester Feedback toggle: verified ON for both groups in the ASC UI. App entitlements / Info.plist: no changes in the 30 days prior to the cutoff. Tester membership: verified active. The tester used in the repro is Account Holder on the team. ASC API key: the same key successfully retrieves the 882 historical submissions. Read auth is intact; only writes from the device side fail to land. App Privacy: configured and submitted. What I've already filed: Feedback Assistant: FB23052931 (filed 2026-06-10, Area: App Store Connect, Incorrect/Unexpected Behavior) Apple Developer Support (Distribution / TestFlight email channel): Case 102913469272 (filed 2026-06-10, cross-references FB23052931) What I'd love to hear from the community: Have you seen this exact pattern (sharp cutoff date, total frozen, no error on submission)? Did it eventually resolve on Apple's side, and if so what was the rough turnaround? Is there anything you tried on the developer side that actually re-enabled ingestion (re-promoting a build to groups, regenerating an ASC API key, anything)? Anyone on a thread where an Apple Frameworks Engineer responded to this class of bug? I'm aware of older threads going back to 2019 (thread 122295) with similar symptoms but no Apple engineer response. Hoping to surface a more recent path forward. Thanks.

Hello, I am writing this out of profound frustration and desperation. My team has worked incredibly hard to build an app that now supports a community of 500,000 users, trusting Apple as a reliable partner. Instead, we are being completely starved of our own capital due to a severe and ongoing failure in Apple’s payout routing, and support is entirely ignoring us. The Timeline of Errors: February 8: Monetization began, and we met the minimum payout threshold within two days. April 9: The app was legally transferred to my developer account from my ex-co-founder. I updated all banking and tax details on my account that exact same day. Payout Failure 1 (April 9): Upon transfer, Apple incorrectly issued our earned revenue to my ex-co-founder’s bank account instead of mine. Thankfully, my former co-founder is cooperative and manually transferred the funds to me. However, this could have created a major financial and legal issue if the previous account holder had not cooperated. Payout Failure 2 (June 4): Despite my banking details being verified and active for two months, Apple again bypassed my account and routed another payout to my ex-co-founder. Worse, the amount sent was only a fraction of the total revenue actually owed. It is now June 10. The 45-day payment cycle logic is completely broken, and funds are actively being sent to an account that no longer owns the application. The Impact: Behind this app are real people. I have employee salaries to pay and personal bills to cover, and my business operations are being suffocated because Apple is withholding our earned revenue. To add insult to injury, I am also being completely ignored regarding my enrollment in the App Store Small Business Program, with zero communication or updates. When I call support, representatives tell me they cannot access finance issues and tell me to open another ticket. When I open tickets, I am met with absolute silence. Ignored Support Tickets: Case ID: 20382739 Case ID: 20447730 Could a community manager or moderator please escalate these case IDs to a senior supervisor in Finance? This is extremely frustrating because Apple takes a 30% commission, but I still cannot get clear information or timely access to earned revenue. Thank you.

Hello! I am developing an app that includes an app clip. Recently, I launched my app on the App Store, but I discovered that some of the app clip codes are not functioning correctly. My AASA file is configured correctly (general deep links work with it, as well as some app clip URLs) and is also configured for app clips. { "appclips": { "apps": [ "TEAM_ID.maxood.AveBingo.AppClip" ], "details": [ { "appID": "TEAM_ID.maxood.AveBingo.AppClip", "paths": [ "/*", "/bingo/*", ] } ] }, "applinks": { "apps": [ "TEAM_ID.maxood.AveBingo" ], "details": [ { "appID": "TEAM_ID.maxood.AveBingo", "paths": [ "/", "/bingo/*" ] } ] } } I've also created the advanced app clip experience in App Store Connect and configured it to open links with my domain as the prefix: So if I create an app clip code with my root URL 'https://avebingo.com', my app clip is immediately launched. However, if I create an app clip code and want to launch my app clip for a particular bingo using the URL 'https://avebingo.com/bingo/<some_id>', it is not launched, and a popup says, 'This app clip is not currently available in your country or region.' Interestingly, app clip diagnostics in my iPhone settings indicate that everything is okay for my root URL. But for URLs like 'https://avebingo.com/bingo/some_id', it says the following, which indicates that my app is not launched in the App Store (but it is). Can you please share what do i do wrong and how to fix it? Thanks in advance.

On the iOS App Version page in App Store Connect, clicking Save shows an exclamation-mark error icon on the button, but no error message or field-level validation appears anywhere on the page. The Add for Review button stays greyed out, so I can't submit. This happens on every new version. What I've verified: •⁠ ⁠Build is attached and shows "Validated" in TestFlight, no warnings or compliance issues •⁠ ⁠All required metadata populated: Description, What's New, Keywords, Support URL, Marketing URL, Copyright, Version, Sign-In Information (working credentials), Contact Info •⁠ ⁠Export compliance answered •⁠ ⁠Release set to "Manually release this version" •⁠ ⁠Screenshots present for iPhone 6.5" (same assets that worked on a prior version) •⁠ ⁠Media Manager shows no warnings on any size •⁠ ⁠Account has the Account Holder role •⁠ ⁠Reproduced in Chrome (latest) and in Incognito Observation: on clicking Save, the screenshots section briefly refreshes/reloads, then the error icon appears on Save. No other error is surfaced anywhere. Current workaround: my engineer uploads the build directly from Xcode to App Store Connect, which lets the version through - but the web Save/submit path is broken on every release. Question: what validation is failing here without being surfaced in the UI, and how do I get the web Save/submit flow working so I don't have to fall back to a manual Xcode upload each release?

Hello App Review Team, I wanted to follow up because my app, BitzaHugs, is still showing as Waiting for Review, and I was informed that my case was expedited and in active review. I addressed all previously cited rejection issues and resubmitted the app, but I am still waiting for the review to move forward. App Name: BitzaHugs Support Case #: 102903001544 Current Status: Waiting for Review Expedited Review: Requested again / currently active I completely understand that review times can vary, but because my app has already gone through multiple rejection cycles, the issues have been resolved, and my intended launch date has passed, I would greatly appreciate any update or escalation if possible. Please let me know if there is anything else needed from my side to help move the review forward. Thank you again for your time and assistance, Amanda Benavidez

Hi everyone, We are facing an unusually long review delay for our iOS app submission. Our app has been in “Waiting for Review” status for almost 2 weeks now, with no update or movement. We had planned our official launch for 21 May 2026, but the launch date has already passed because the app is still not reviewed/approved. We have already contacted Apple Developer Support and requested assistance, but the status has not changed so far. For context: • App name: SuperWomen • Platform: iOS • Current status: Waiting for Review • Waiting time: Almost 2 weeks • Planned launch date affected: 21 May 2026 • Apple ID: 6759612459 • Case ID: 102898811179 Is anyone else still experiencing unusually long “Waiting for Review” times recently? Also, if Apple Staff can check whether our submission is stuck in the review queue or if any action is required from our side, it would be very helpful. Thank you.

I would like to confirm my understanding of how app availability and app removal affect existing and new users on the App Store. Scenario 1: App is removed from sale in App Store Connect (Availability is changed so the app is no longer available for new downloads.) My understanding is: New users Cannot find or install the app from the App Store. Existing users who already have the app installed Can continue using the app normally. Existing users who delete the app Can still re-download it from their Purchase History / Previously Purchased apps. Is this correct? Scenario 2: App is deleted using the "Delete App" option in App Store Connect (My understanding is that the app itself is removed rather than simply being removed from sale.) My understanding is: New users Cannot find or install the app from the App Store. Existing users who already have the app installed Can continue using the installed app. Existing users who delete the app Can no longer re-download the app. Is this correct? Additionally, could someone clarify the differences between the following actions and their impact on existing users? Remove from Sale Remove from App Store Delete App in App Store Connect App removed by Apple In particular, I would like to understand whether users who previously downloaded or purchased the app can still re-download it after each of these actions. Thank you for your help.

Hello, I'm facing an unusual App Store Search issue and would appreciate guidance from Apple staff or developers who have experienced something similar. App Details App Name: Logistos – Logistics Platform Apple ID: 6759841195 Category: Business Availability: Available in all supported storefronts, including India Publicly available for: More than 2 months Latest version: Released and live for more than 5 days Issue The app is accessible through its direct App Store URL and is indexed by Google Search. However, it does not appear in App Store Search results. I have tested the following search terms on multiple devices and storefronts: Logistos Logistos – Logistics Platform Logistos Logistics Platform 6759841195 (Apple ID) In all cases, the app does not appear in the search results. Additional Information The app name contains "Logistos". The subtitle is "Logistics & Shipment Tracking". The keywords include "logistos". Metadata changes have already been released and enough time has passed for propagation. App Store Analytics shows the app is receiving impressions, product page views, and downloads. Direct App Store links work normally. I have already opened a support case with Apple Developer Support. Case ID: 102908696756 Has anyone encountered a similar App Store Search indexing issue? Could this indicate that the app requires manual reindexing by Apple? Any guidance would be greatly appreciated. Thank you.

I am trying to understand the 2 million download limit for access to PCC. It says that Analytics provides information about first time downloads, but the linked documentation explicitly says that Total Downloads in Analytics (which does not seem to exist anymore) includes first time downloads and redownloads. Can you clarify where this data currently exists? While I do not have any apps approaching 2 million right now, my app with the most downloads is entirely free and has been on the App Store since 2012. The app was intended as a Lite version for users to try out and decide whether they wanted the paid version. In modern apps, In-App Purchases accomplish something similar; as I move forward with new apps, I would like to avoid a situation where people increase my first time download count but don't end up using the app. It seems like any freemium model would be detrimental to staying eligible for PCC. Do you have any recommendations?

I have my first app on the App Store and I’m unsure whether I’m seeing a normal App Store indexing delay or a storefront issue. The macOS version of my app is searchable and can be found normally in the Mac App Store. The iPhone/iPad version was approved, the direct App Store URL works, the app page shows a price, and the app can be reached from my website. However, neither the app name nor the developer name can be found through App Store search on iPhone or iPad. In addition, App Store Connect currently does not allow me to edit screenshots or other metadata, and the Mac storefront appears to be displaying incorrect screenshots. Is there a recommended Apple support path for App Store search indexing and storefront metadata issues, or does this indicate a known App Store Connect problem?

Hi Apple Team, We're looking for guidance from developers who have successfully resolved a rejection under App Review Guideline 3.2.1(viii). Our app is mPokket: Instant Loan App, a consumer lending application that has been live on Google Play for nearly 10 years. The app is published by Maybright Ventures Private Limited, which owns and operates the mPokket lending business and brand. While consumers know the service as "mPokket," the legal entity behind the business and the developer account is Maybright Ventures Private Limited. Our iOS app has now been rejected twice with the following message: "The app provides loan services but the domains listed on the app's Product Pages are not clearly under your control or ownership." Apple also mentions that the Product Page domains and the email domains of the Apple Accounts associated with the developer account should clearly identify the company providing the loan services. Has anyone faced a similar situation where: The consumer brand name is different from the parent/legal entity name? The developer account is under the parent company while the app is marketed under a consumer brand? App Review requested additional clarification regarding ownership of the lending business and website domains? If so, what documentation or changes helped obtain approval? Did you need to: Change the Account Holder/Admin Apple IDs to use the parent company's domain? Add additional ownership documentation? Provide a corporate structure explanation or trademark/brand ownership details? Any guidance or experience would be greatly appreciated. Thank you.

I’m working on an iOS app and need help with ASO to find the best keywords for title, subtitle, description, and keyword field. Can anyone suggest free tools that show keyword volume, difficulty, and competitor keywords?

Hi, I can sign in to my Apple ID, but my Apple Developer account shows a “closed” status and I’m unable to access App Store Connect features. My app is currently showing “Ready for Distribution,” so the account appears active, but developer access is restricted. I’ve already contacted Apple Developer Support and am waiting for their response. Also, I temporarily can’t access my primary email due to a verification issue, so I’ve provided an alternate contact email and phone number in my support request. Has anyone experienced a similar situation or knows possible reasons for a “closed” developer status while the app remains approved? Thanks.

Hello everyone, I submitted the first update for my app on April 14. On April 18, I canceled that submission and immediately resubmitted it the same day, as many people suggested that resubmitting might help speed up the review process. Today is June 4, and after 47 days, the update is still stuck in “Waiting for Review.” I’ve seen that many other developers are experiencing the same issue, but 47 days is a very long time for me, and I have no idea how much longer I should expect to wait. I hope we can all find a solution to this situation soon. Any advice, insights, or shared experiences would be greatly appreciated. Thank you all.

Is there any way to activate Storekit External Purchase Entitlements in Russian region currently? External Purchase documentation's form link for this specific region is not working. Is there a workaround to register for it?

Hello, I’m posting again because our previous forum post received the following Apple Staff reply: “Thank you for your post. We're investigating and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us.” However, the issue has not been resolved yet. We have not received any separate contact in App Store Connect, the Resolution Center, or email. We currently have two active apps in the same developer account that are stuck in Waiting for Review. Because multiple apps in the same account are affected at the same time, this seems like it may be an account-level App Review queue or routing issue rather than an individual app binary issue. For one of the affected apps: App ID: 6760743106 Review submission ID: 6950ecff-f833-404d-b04b-ac34ec552b85 Submitted: June 1, 2026 Review submission state: WAITING_FOR_REVIEW Review submission item state: READY_FOR_REVIEW App Store version state: WAITING_FOR_REVIEW Build processing state: VALID Build audience type: APP_STORE_ELIGIBLE Build expired: false TestFlight installation works normally, and there is no Resolution Center message. We are also unable to submit an expedited review request because the expedited review form itself fails. After selecting the correct app and platform, the form sends a POST request and receives HTTP 200 OK, but the response page displays: “Sorry, we didn’t receive your request. An error has occurred and your submission wasn’t completed. Please go back and try again. If you continue to have issues, contact us.” The POST payload includes the correct app ID and platform: expedite_app_id_req: 6760743106 expedite_app_platform: ios Could Apple Staff please check whether our developer account or these submissions are affected by an internal App Review queue/routing issue? We are currently blocked because the review has not started for multiple apps, we have not received any follow-up contact, and the expedited review request form cannot be submitted.

Hello, about a month ago, the Apple Store account of my former company was closed. I was already registered as a developer, so there's no problem with that. Was my personal account also closed when this company account was shut down? I contacted Apple support about this, and they said they would investigate. I still haven't received a response. Was my account closed? Or is there another issue? Nobody is explaining why this happened.