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

Another Limbo with IAP. I'm genuinely baffled by this. My app " Tapix - AI Writing Keyboard " was reviewed, approved, and is currently live and downloadable on the App Store. Great except the auto-renewable subscription that I submitted at the same time is STILL sitting in "Waiting for Review." Let me spell out what this means for real users: A user finds my app on the App Store They download it They open it and hit the subscription screen Nothing works. They can't subscribe. The core functionality is locked behind a paywall that Apple hasn't approved yet. They think the app is broken They leave a 1-star review and delete it. This is an absolutely terrible first impression and there's nothing I can do about it from my side. Everything is configured correctly metadata, pricing, review screenshots, subscription group, product IDs all of it. The app was approved. The subscription just... wasn't. How is it possible that Apple approves and distributes an app but leaves the IAP that the app literally depends on in limbo? Shouldn't these be reviewed together? Why would you release an app to users in a state where its core monetization is non-functional? Every hour this sits in "Waiting for Review" is real damage and a launch that's essentially sabotaged through no fault of my own. I'm asking for any guidance on how to escalate this. This needs urgent attention. Thank you. App Name - Tapix AI Keyboard

Hello, My app "Zen Mahjong!" has been stuck in the App Review process for an unusually long time and I’m trying to understand if something might be wrong with the submission. Timeline: First submission entered “In Review” and stayed there for 6 days without a decision. I rejected that build, uploaded a new build and resubmitted on February 17. Since then the app has been in “Waiting for Review” for more than 3 weeks. Additional context: App size ~40 MB Only IAP is a “Remove Ads” purchase I already contacted Developer Support and opened an expedited review request. Support also mentioned that this delay seems unusual. Has anyone experienced something similar or could this indicate that the submission is stuck in the review pipeline? Any guidance would be greatly appreciated. Thank you.

Hey everyone 👋 I’m starting my journey in iOS app development coming from a Java background and I already have an app idea but want to approach things the right way so I’d love your guidance What AI tools do you recommend for coding debugging and learning Swift or SwiftUI 🤖 how do you approach app design 🎨 and where do you find UI inspiration graphics or useful resources for building apps 🚀 any tips or lessons learned would really help 🙏

I am submitting an app to the App Store and want to understand the best way to handle keywords that include special characters. If a keyword has accents like coração and users may search for coracao without accents, should I include both versions or rely on Apple to match them automatically?

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

I work on an SDK, and one of the ways we distribute it is as a pre-compiled static XCFramework. As far as I know, it’s the nature of a static framework to not contain symbols since the framework will be embedded in the final app binary, and the symbols should then be generated. However, when testing the "Validate" function of the Xcode 16 deployment process, our users are receiving a warning that says the framework does not contain symbols. Is my assumption about static frameworks and symbols incorrect? Could this be a bug in Xcode 16? Should we modify something in our framework to inform Xcode that symbols are not needed?

Is anyone else having trouble generating App Store promo codes? The promo codes page in App Store Connect is mostly failing to finish loading, and even when it does finish, promo code generation gets stuck on Generating.

Hello Apple Developer Community and App Review Team, I am reaching out here because I am completely stuck and have not received a response from the standard support channels. On March 4th, I requested and was successfully granted an Expedited Review for a critical bug fix for two of my apps ("Who Wants to Be AI Professor?" and "The Fed Chair"). However, it has been 12 days and both apps are still stuck in the "Waiting for Review" status. Suspecting a system glitch or "ghosting" issue, I contacted App Store Connect support on March 10th and received Case ID: 102840953234. The automated email stated I would receive a reply within 2 business days, but that time has long passed with no response. I kindly ask if an App Review Team member or Apple Staff could look into this Case ID and check if my submissions are stuck in a technical loop. I have refrained from canceling and resubmitting to avoid further delays, but I am currently completely blocked. Any help to push these manually to the review desk would be immensely appreciated. Thank you!

I want to provide free test accounts so that mobile games reviewers can play my iOS game for free. They should be able to make in-app purchases(consumables) without any charges. I don´t know how to create the free test accounts. Is it necessary that my iOS game is already published in the Apple App Store before I can provide test accounts for mobile games reviewers? Or is it necessary to let the reviewers play my game while it is still in TestFlight? If yes, should I ask them to give me there email address so that I can add it to my Sandbox accounts? My game was not yet released in the App Apple Store. It´s only available on TestFlight.

Hi, My app wich shipping ID is e18f049f-bff9-4993-97b4-742c6ba63d0e is waiting for review since last month. if there is any place that I can submit a ticket or ask more properly please let me know. best, David Silva

Hello, I submitted my app for review for the first time about two weeks ago and it is still stuck in "Waiting for Review" with no update. I haven't received any feedback yet and I'm not sure if this kind of delay is normal or if something might be wrong. Has anyone experienced something similar? What did you do in this situation? Thanks.

Hello everyone, I submitted my app USDT Miner – Rig Manager to App Store Connect on February 2, and it has been in “Waiting for Review” status since then. I understand that review times can vary, but it has now been several days without any status change or feedback. This is my first submission for this app, and there are no resolution center messages or rejection notices so far. I wanted to ask: Is this delay normal at the moment? Are there any known review backlogs or factors that could cause an extended “Waiting for Review” status? Is there anything recommended to do from the developer side, or should I simply continue waiting? Any insights from Apple staff or fellow developers who’ve experienced similar delays would be appreciated. Thank you.

Hello, I'm a first time developer and both of my submissions for NexFi - Portfolio Tracker have been suck in Waiting for Review for an extended time. TestFlight: My first build was submitted on Feb 15th (25+ days) and still Waiting for Review Production/Distribution: Submitted March 2nd (10 days) and still Waiting for Review. It is a finance category app (portfolio tracker) that requires no login, no account creation, and no server side user data so I figured it should be a relatively quick process as there is a minimal privacy footprint. App Name: NexFi - Portfolio Tracker Platform: iOS App ID: 6759226354

Hello everyone, I am seeking some guidance on how to break out of what appears to be an automated App Review rejection loop. My app has been rejected three times in a row for the exact same reason, and my replies in the Resolution Center seem to be getting ignored. The Issue: My app is named Linkwise (associated with my web platform, linkwise.app). I am being rejected under Guideline 4.1(c) - Design - Copycats. The rejection message specifically states: "The app's icon and name contain an icon, brand, or product name that belongs to the following developer: Linkwise." The bizarre part is that I am the developer of Linkwise. I am being accused of impersonating my own brand and product. Submission Details: App Name: Linkwise Submission ID: fa557f1b-3724-4e01-aa85-bf05ced4801f Version: 1.0.1 Review Device: iPhone 17 Pro Max What I've Tried: I have replied to the rejection message in App Store Connect three times explaining that I am the owner of the Linkwise brand and domain. Despite this, I keep receiving the exact same copy-pasted template response. It feels like a human is not actually reading the appeals. My Questions: How can I escalate this past the initial review tier to someone who can read the context? Has anyone else experienced being rejected for copying themselves? What specific "documentary evidence" does App Review usually want in this scenario to prove I own my own name? Would my domain registration receipt for linkwise.app be sufficient, or do they require formal trademark documentation? Any advice on how to get this in front of a real person would be greatly appreciated. Thank you!

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

Hello, I am currently implementing External Purchase Link and External Purchase Custom Link and am encountering an issue where both ExternalPurchaseLink.canOpen and ExternalPurchaseCustomLink.isEligible always return false under all test conditions. I would like to confirm whether my setup is missing any required steps or whether this behavior is expected. Below are the details of my current environment and configuration: 🔧 1. Development Environment Xcode: 16.3, 16.4, 26.0 beta 4 Devices: iPhone running iOS 26.2 beta iPhone running iOS 16.7.12 macOS 15.5 (real device testing) Simulator iOS 18.0 Build Type: Local development build using a Developer Provisioning Profile Sandbox account signed in during testing 🔑 2. Entitlements (Developer site & Xcode) In Certificates → Identifiers → App ID, both capabilities are enabled: StoreKit External Purchase StoreKit External Purchase Link The .entitlements file in Xcode includes: com.apple.developer.storekit.external-purchase = YES com.apple.developer.storekit.external-purchase-link = YES The Provisioning Profile also contains both entitlements (confirmed via codesign -d --entitlements :-). 📄 3. Info.plist Configuration Both keys are configured with correct region codes according to documentation: SKExternalPurchase SKExternalPurchaseCustomLinkRegions 🌍 4. Test Storefront Device storefront verified as United States (US) or Portugal (PT) (US = target region for External Purchase Link, PT = EU region) But despite all the above configuration, both API calls consistently return false: ExternalPurchaseLink.canOpen // false ExternalPurchaseCustomLink.isEligible // false So I cannot proceed to testing the remaining flow (token retrieval, link opening, etc.) ------ Questions ------ ❓ Q1) Local Development Build Limitation Is it expected behavior that Developer-signed local builds always return canOpen = false / isEligible = false for External Purchase Link & Custom Link? Is there a technical or policy restriction that prevents eligibility in local dev builds? ❓ Q2) App Store Connect Configuration Requirement Are there mandatory App Store Connect settings (such as external purchase URLs, support URL, disclosures, or country configuration) that must be enabled before eligibility becomes true? Currently, no External Purchase Link or Custom Link menu is visible in my App Store Connect app settings. Is this menu only available after certain approvals or under specific conditions? ❓ Q3) TestFlight Requirement Do External Purchase Link and Custom Link only return eligibility = true on: TestFlight builds, or Distribution-signed builds? Or should eligibility also work on developer builds? Formal confirmation would be helpful. ❓ Q4) Developer Account Type Limitation We are using an Individual Developer Account (not Organization). Can Individual accounts fully request, test, and ship apps using: External Purchase Link External Purchase Custom Link Or are there limitations on account type? 🙏 Request We have completed all documented setup steps (Entitlements → Provisioning → Info.plist), but eligibility remains false, blocking feature validation. Please clarify which of the following is the cause: Local development builds do not support eligibility Missing App Store Connect configuration (not visible to us) Account type restriction Region rollout or entitlement approval requirement Any additional setup not documented publicly Thank you for your assistance.

In App Store Connect I've uploaded a new build about 11 hours ago and but I'm unable to distribute the App to my tester groups - including internal. The internal group is grayed out. I am able to Select an External group but they actually do not receive any email notification nor do they see any update within their TestFlight App. I've attempted to upload the build a few times, including old builds which had been distributed in the past to no avail. I'm not able to distribute to any tester group, please advise.

I have an app for iOS already on the AppStore and I'm trying to add a macOS version of it. The AppID prefix for this app is different than my Team ID. This mismatch was always fine for submitting my iOS app. However for some reason, the macOS version gets rejected when I upload it. It tells me the AppID prefix must match my Team ID. I do not control my TeamID and I do not control my AppID prefix, they are both given to me by Apple. Yet the error message tells me they must match. How do I get past this? Here is the error message: Validation failed Invalid code signing entitlements. Your application bundle's signature contains code signing entitlements that aren't supported on macOS. Specifically, the "APPID_PREFIX.MY_BUNDLE_ID" value for the com.apple.application-identifier key in "MY_PACKAGE" isn't supported. This value should be a string that starts with your Team ID, followed by a dot ('"), followed by the bundle ID. (ID: 930b77ae-099f-4798-a14a-2803f2a9be9e) Thanks in advance for any pointer.

Hello, I submitted my app for review several days ago, but the status is still “Waiting for Review.” It appears that nobody from the Apple review team has started reviewing the app yet. This situation is extremely frustrating and unacceptable for developers who depend on timely reviews to maintain and release their applications. Waiting days, weeks, or even a month just to receive a potential rejection due to a fixable issue wastes a significant amount of time for development teams. The main problem is not only the delay itself, but the lack of progress. The status remains stuck at "Waiting for Review", which suggests that the review process has not even begun. I have also noticed that many other developers are currently experiencing the same issue, which suggests that this may be a broader problem affecting the App Store review system. Could someone from Apple please clarify: Why apps are staying in “Waiting for Review” for so long Whether there is currently a backlog or system issue affecting reviews What developers can do to avoid these long delays At this point, I would really appreciate an immediate solution or at least an explanation for what is happening with the review process. SUBMISSION ID: c56590cd-cbdb-429d-9555-163efabda47b Thank you.

Hello, I am trying to understand what is happening with my submissions because the situation has become very unusual. I currently have three applications in the App Store review queue: • Healthoria – submitted Feb 5, 7:01 PM • OrbitGoals – submitted Feb 17, 4:11 PM • Memochron – submitted Mar 10 All three of them are still in “Waiting for Review.” The first submission has now been waiting for over a month. During this time I have sent support emails and submitted an expedited review request, but I have not received any response or update. What makes this situation more confusing is that most developers report review times of 2–3 days. Seeing my apps remain in the queue for weeks without any communication makes it difficult to understand whether there is a technical issue, an account-related delay, or something else affecting the process. I completely understand that review times can vary, but having three separate apps all stuck in the same stage for this long seems highly unusual. If anyone from Apple or other developers have experienced a similar situation, I would greatly appreciate any clarification or guidance. Thank you. Best regards, Berkay