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

Hi everyone, I’m experiencing an unexpected delay in the review process for my app (RadioBar), and I’d appreciate your guidance. Here’s the timeline: March 24: Received feedback from the review team stating that identified issues could be resolved in the next update. Same day (March 24): Fixed the issues immediately and resubmitted the app. March 24–28: App remained in "In Review" status with no updates. March 28: Resubmitted the app again, assuming possible system issues. Status returned to "In Review." March 31: Requested an expedited review via the Resolution Center due to urgent bug fixes impacting users. As of April 2, the app remains stuck in "In Review" with no progress. This delay is disrupting my development schedule and affecting users awaiting critical fixes. Steps taken: Ensured compliance with all guidelines. Responded promptly to initial feedback. Submitted expedited review request. Could you kindly investigate the delay and prioritize the review? Any clarification or assistance would be greatly appreciated. Thank you for your support!

I've seen other similar posts with no clear answers and solutions. My Unity app has been rejected several times with this message: The UIRequiredDeviceCapabilities key in the Info.plist is still set up in such a way that the app will not install on the device used in review. Review device details: Device type: iPhone 13 mini OS version: iOS 18.4 Next Steps Please check the UIRequiredDeviceCapabilities key to verify that it contains only the attributes required for the app features or the attributes that must not be present on the device. Attributes specified by a dictionary should be set to true if they are required and false if they must not be present on the device. I have made sure the submitted app has only one value for UIRequiredDeviceCapabilities, arm64, which is required by Unity. Initially Metal was listed as well, but I've removed it in trying to fix this problem. Additionally, I've ran the app through TestFlight and it functions fine. I'm not sure what else to try to fix this issue, though I've seen from other posts that indicate this type of rejection could possibly be a bit of a red herring and the real issue could be something else. Any help would be appreciated

I use Expo EAS tool to submit to iOS and honestly I never had any issues before, at least on other projects. In the past few days I have been trying to submit a new build for an update of an older app but I am getting this error: A required agreement is missing or has expired. This request requires an in-effect agreement that has not been signed or has expired. (ID: O4YFH7VPB2LECAUAVXR6G4WRFQ) (403) I checked my agreements page and there is no clear indication of any missing agreements left to sign or what not. I have tried different builds of this project to no avail. I am stuck in a rut and I have been already waiting three days for customer support to acknowledge my issue and get back to me.

I don't get any idea why I am getting the following warnings when I tried to upload one of my apps:

I have an unpublished app that we use as our development environment, and we need to transfer it to another Apple Developer account. Since the app is not published, the standard App Transfer process in App Store Connect does not apply. Is there any workaround to transfer the app without creating a new developer account, changing the bundle ID, or reconfiguring all the associated certificates and provisioning profiles? We would like to avoid the need to rebuild and reconfigure everything from scratch. Any guidance on this process would be greatly appreciated!

CONTEXT: iOS: 18.2.1 || macOS: 15.4 || Xcode: 16.2 || App status: Not yet released || In-app purchase type: Subscription || App version: 1.0, Build 3 ISSUE:
 App Store Connect has rejected our latest app submission with the instructions “…submit your in-app purchases and upload a new binary in App Store Connect…”. Unfortunately, the required "In-App Purchases and Subscriptions" section is missing from the ‘version page’ of our submission. This is further complicated by the fact that we had already tested the subscription in App Store Connect’s sandbox, where it successfully returned the non-domestic storefront pricing for Hungary (HUF1,490.00/year). After reviewing nearly four dozen Apple pages of documentation and a dozen Apple forum posts, we found only one relevant link: https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/submit-for-review Unfortunately, the instructions under the disclosure triangle: "Submit an in-app purchase for the first time" confirm that the "In-App Purchases and Subscriptions" section is missing from our version page. Additionally, review of the blue warning box on the Subscription page includes the following instructions: "…Create your subscription, then select it from the app’s In-App Purchases and Subscriptions section on the version page…" Unfortunately, this section does not exist on our version page, confirming that there is no specific section labeled "In-App Purchases and Subscriptions" available. Similar issues have been reported by other developers. See this Stack Overflow thread for additional context: https://stackoverflow.com/questions/73098652/app-store-connect-in-app-purchase-and-subscriptions-section-missing HISTORY: Successfully created and sandbox tested the subscription in App Store Connect. Reviewed over five dozen pages of Apple documentation and forum posts as well as Stack Overflow. Have repeatedly loaded and checked the 'version page' for the "In-App Purchases and Subscriptions" section, which is unfortunately missing from our submission. QUESTIONS: Where is the "In-App Purchases and Subscriptions" section located, if not on the 'version page' of our submission? Is there an alternative method to submit in-app purchases and upload a new binary in App Store Connect? Do we need to remove any part of the submission to access the "In-App Purchases and Subscriptions" section? What is the risk of losing our app name 'Concensus' in the Apple App Store if we delete any portion of the submission? We would appreciate guidance on how to proceed with submitting our in-app purchase subscription along with our new app version. Grateful Indeed.

I have submitted an update for my app. Typically, my app reviews take less than 24 hours, but this time, it has been stuck "In Review" for several days. I have also tried resubmitting the app multiple times, but the status remains unchanged. Is there anyone who is experiencing the same issue? Any help would be greatly appreciated!

My app has been stuck in "Processing" in App Store Connect TestFlight for a couple hours. Normally this only takes like 5 minutes. The Status page (https://developer.apple.com/system-status/) indicates processing is working, but in our case it appears to be stuck.

I am trying to submit my app for review but when I click on the 'add to review' button, I am getting the message: Unable to Add for Review The items below are required to start the review process: There are still screenshot uploads in progress. However, there is nothing I am uploading... I tried removing all screenshots, nothing works. It has been 4 days, I cant update my app on the app store... impossible to get any response from Apple... Any inputs will be greatly appreciated.

Hi recent app update review was rejected because we were informed we had to implement the App Transparency Tracking UI to let users choose. (we had just successfully published two days prior to this, and we need to get some bug fixes out with a new submission) Nothing about the app with respect to data collection had changed between the successful submission and the rejection and still wondering why we were rejected for that reason. We do not track data. We do collect user info and info about app usage for user account login and app performance analytics, and also for our development cycle. So I updated the app to present the Tracking Transparency UI at startup and that is all good. Now I add the app to the submission form, and I go update our privacy policy to define what data we collect and how we are using it. I publish the updated privacy information. but now I am stuck. The submission page returns a message that I have to set up the privacy data to be able to submit for review Your app contains NSUserTrackingUsageDescription, indicating that it may request permission to track users. To submit for review, update your App Privacy response to indicate that data collected from this app will be used for tracking purposes, or update your app binary and upload a new build. Learn More But I have already defined and published that privacy data. It seems it is not finding the Privacy data or what? What could be going wrong here? Thanks for any ideas!

Hello everyone, I’m having trouble with our app’s subscription setup during App Store review, and I’m hoping to get some guidance. Our app, offers an auto‑renewable subscription. In App Store Connect, we created the subscription as an “Auto‑Renewable Subscription” with a product identifier. We do not offer consumable or non‑consumable in‑app purchases—only this subscription. However, Apple recently rejected our submission with the following message: “We have started the review of your app, but we are not able to continue because we cannot locate the in‑app purchases within your app at this time. Next Steps To help us proceed with the review of your app, please reply to this message providing the steps for locating the in‑app purchases in your app. Note that in‑app purchases are reviewed in an Apple‑provided sandbox environment. Make sure they have been appropriately configured for review in the Apple‑provided sandbox environment. If you are restricting access to in‑app purchases based on factors such as storefront or device configurations, please include this information in your reply along with steps to enable the in‑app purchases for our review.” I’m confused for a couple of reasons: 1. We only offer subscriptions—there are no consumable or non‑consumable products. Yet, Apple’s message refers to “in‑app purchases.” 2. It seems our subscription product is not being found in the sandbox environment. Our subscription is currently in “Waiting for Review” status in App Store Connect, so when using StoreKit 2 (via Product.products([…])) the array returns empty. 3. I’m not sure if we need to enable something else in App Store Connect for subscriptions to be testable in the sandbox, or if our configuration is insufficient for review. Has anyone encountered a similar situation? What are the steps you took to ensure your auto‑renewable subscription were testable for App Store review? Any tips on dealing with this loop—where the subscription must be approved for reviewers to find it, yet Apple won’t approve the app until they can test it? Thanks in advance for any insights or suggestions!

I am experiencing difficulties including subscriptions for the first time in a new binary version. The subscriptions are currently in “Developer Action Needed” status, and I am unable to reset them to “Ready to Submit”. I assume this is why the “Select In-App Purchases and Subscriptions” option is missing from the binary version page. Since subscriptions are a vital part of the app, their absence has led to the app being rejected in the review process. Any advice on how to proceed?

Hello, I've submitted my game to app store review and got rejected, I sent an appeal on Mar 2, but I didn't receive any confirmation email that the appeal has been sent, which was weird thing since Apple always send confirmation emails! and I didn't receive any response yet! My game is still in rejected state I didn't upload any new version as I wait for the appeal response. M questions are, do Apple usually sends a confirmation emails after submitting an appeal? and should I wait more for the response? (it has been 10 days). Thanks in advance for anyone who could share any insights.

I've built and released quite a few apps, and it always goes something like this App is "waiting for review" for 12-24 hours App is "in review" for 4-8 hours App is approved or rejected However, this time is different. I submitted a brand new app to the store. Within 12 hours, it moved from "waiting for review" to "in review". Pretty normal. Over 48 hours later, it's still "In review". I rejected it and resubmitted because I wanted to remove a distribution country. And again, same thing. Moved to "In Review". It's been over 4 days now. I don't understand whats taking so long here. This is incredibly frustrating as the app launched just fine on the Google Play store, and I'd like to start marketing them together. What can I do?

We are a team of developers, and our company is involved in creating mobile applications. Recently, our developer account was terminated, and all active apps were removed from the App Store. The email mentioned that our app violates section 3.2(f) of the Apple Developer Program License Agreement. We've been trying to identify the issue since then, but we're not involved in any fraudulent activities. Our company is facing a critical situation as it is essential for us to have the apps back on the App Store as soon as possible. We are unsure of how to proceed and would greatly appreciate any assistance or guidance. Thanks. Our app ID com.seriktes.kz App name Seriktes

Hey all, I'm experiencing an error, when trying to upload my app to the App Store using Transporter. I build my app with fvm flutter build ipa --release. When I try to upload this, I get the following error: I have already done a rebuild and checked my Provision Profile and certificate

Dear Apple Review Team & Develpers! Could anyone clarify why Apple Reviewers, when rejecting the app under Guideline 4.3(a) - Design - Spam, do not provide any specific details? Each time my app is rejected, I receive a generic, automated response. In contrast, I provide detailed information and request clarification on the exact reasons for the rejection- specifically, what aspects of the app do not meet Apple's requirements. However, the responses I receive are always the same standard message without any useful details. Am I correct in understanding that the review process is entirely automated, with no human evaluation, resulting in repetitive, unhelpful replies? I would appreciate a more detailed response that can genuinely help me address the issue and ensure my app complies with Apple's guidelines. Here is their standard generic response to any my reply where I provide details and ask questions, but Apple Reviewer answer alsway with the same text: Guideline 4.3(a) - Design - Spam This app duplicates the content and functionality of other apps on the App Store, which is considered a form of spam. Specifically, this app appears to be identical to apps already on the App Store from other developers. Apps that duplicate content or functionality create clutter, diminish the overall experience for the end user, and reduce the ability of developers to market their apps. Next Steps It would be appropriate to revise your app to provide a unique experience or submit a new app that does not duplicate the content and functionality of other apps on the App Store. Resources Some factors that contribute to a spam rejection may include: Submitting an app with the same source code or assets as other apps already submitted to the App Store Creating and submitting multiple similar apps using a repackaged app template Purchasing an app template with problematic code from a third party Submitting several similar apps across multiple accounts Learn more about our requirements to prevent spam in App Review Guideline 4.3(a). Support Reply to this message in your preferred language if you need assistance. If you need additional support, use the Contact Us module. Consult with fellow developers and Apple engineers on the Apple Developer Forums. Provide feedback on this message and your review experience by completing a short survey. Review Environment Submission ID: c4a62f43-b02a-40f0-b763-e00fcc996512 Review date: March 04, 2025 Version reviewed: 11.4.1202

Hello everyone, We’re facing an ongoing issue with our app being rejected under the 4.3(a) Spam guideline, and we’re hoping the community can offer some advice on how to resolve it. Our app is a free sports application that provides real-time score updates. It also features commentary from several top contributors and journalists. We offer exclusive features that are completely original—we don’t replicate or borrow any designs or functionalities from other apps on the App Store. Additionally, the app includes games that we have personally researched, designed, and developed from scratch without using any third-party libraries. We were flagged under 4.3(a) Spam after a very minor update, which primarily focused on fixing some interface-related bugs. Despite these minimal changes, our app was rejected under the Spam guideline. To address this, we have sent detailed information to Apple Review, including our development roadmap, screenshots of design versions, and even git logs to demonstrate the development process of our team. These materials clearly show that our app is not a repackage or spam app, as suggested. However, despite all these efforts, the responses we’ve received seem automated, and we have not been given clear explanations or a resolution. We’ve spent a lot of time trying to troubleshoot, removing dead code, and restructuring the project (as Apple claimed we might be sharing binary files with a mysterious app...), but all efforts have been in vain. I’m not sure how to resolve the issue of 'sharing similar binaries, metadata' with other apps if that’s the case. Could this be because I’m using Flutter and package on pub.dev like many other developers ? We’re at a point where we don’t know how to proceed. What steps should we take next to resolve this issue? Has anyone here faced a similar challenge and found a way to get a more detailed response from Apple Review? Any advice would be greatly appreciated! Thank you for your time and help! Kind regards, Michael

Hi there I've recently had my upload rejected in Xcode Organizer as a result of one of the frameworks we use containing bitcode. Error: [ContentDelivery.Uploader.XXXXXXXXXX] Validation failed (409) Invalid Executable. The executable 'Sam.app/Frameworks/Foo.framework/Foo' contains bitcode. Is there an accurate way to determine whether an .xcframework contains bitcode ahead of time without using Xcode Organiser? My current methodology is below, please can I get some confirmation that this is accurate, or suggest a more efficient approach? I have concerns about my approach and whether it throws false positives for empty bitcode markers. 1. get original framework size 2. run xcrun bitcode_strip -r framework_path -o temp 3. get new framework size 4. if new size is smaller than original, then it contains bitcode Thanks for the help, Sam

There’s only the page where I can see my email notification checklist or enrolling developer program.