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

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

We submitted our app for Review on June 3. The submission was put in "In Review" status on the same day. Today is June 10 and we did not receive any status update. Our customers are waiting for the release of our app. This is delaying our promised release date. Can someone review our app?

Hey everyone, I’m submitting my first version of an iOS app to the App Store and ran into an issue I can’t seem to resolve. The app was rejected because during review, Apple couldn’t see the In-App Purchase product on the purchase screen. That’s their only complaint — everything else works fine. Here’s what’s going on: • In debug mode via Xcode, the product shows up correctly, and everything works as expected. • In TestFlight builds, the product doesn’t show up at all — neither for me nor for Apple. • The IAP is currently marked as “Waiting for Review”, not “Ready to Submit”, and it is linked to the current app version in App Store Connect. I’m not sure if the IAP being in “Waiting for Review” is the reason it doesn’t show up in the TestFlight version — but I assumed Apple would still be able to access it for testing. Has anyone experienced this? Do I need to wait for the IAP itself to be approved before it works in TestFlight and can be reviewed? Any insights would be super helpful. Thanks!

We implemented a feature to receive name and email address after Sign in with Apple, and it works perfectly in our testing. However, during the app review, they says it doesn't work, and the app is rejected. Why does it work differently?

Hello all, One of my app submission got rejected saying deletion feature wasnt available. We allow de-activate our user accounts after our customer support representative speaks with customer to confirm and then delete the account. But while submitting our app for release we got this message?? The app only offers to deactivate the account. Temporarily deactivating accounts is not sufficient to meet the account deletion requirement. Any help how to overcome this issue pls? Thanks K

Hello, I represent a registered business operating under a developer account that has always followed Apple’s guidelines, complied fully with review requests, and submitted documentation whenever asked. We have never knowingly violated any policy, and we categorically deny any dishonest or fraudulent behavior. Last week, our developer account was suddenly terminated without any prior warning or opportunity to address concerns. The message provided no specific reason, no actionable details, and no path to resolution. This has left us completely locked out — unable to appeal through standard channels, and unable to contact anyone directly. It’s shocking, disorienting, and devastating to a legitimate business with employees, users, and operations depending on this platform. To make matters worse, this is not the first time. A previous termination notice was sent weeks ago and then — after we submitted a respectful and professional appeal — Apple quietly reversed the decision overnight, without any explanation or follow-up. We were left to assume it was a mistake. We had hoped that incident was rare and behind us. Now it’s happening again, without explanation, and without a human conversation. We are losing money and users every day, and we’re still in the dark about what Apple believes we did wrong — because no one has told us. We submitted a support ticket (ID: 102590329012), but have received no reply. We are committed to transparency, and we’re ready to provide any information needed. But we need someone to acknowledge this issue and help us find a path forward. If anyone has experienced something similar or knows of escalation methods that worked, please share. We’re doing everything we can to resolve this respectfully — but we are shocked and deeply concerned. Thank you.

Hello Developer Community and Apple Staff, Like many others I've seen posting here recently, I'm facing persistent Guideline 4.3 Spam rejections for my puzzle games. I'm hoping for guidance as I believe I've identified and corrected the initial technical cause, but I'm still facing rejection and need help understanding why. My Situation: I develop grid-based puzzle games in Unity, often using my own well-developed reusable codebase (for GridManager, Tile logic, etc.). My last successfully approved app ("Seat Em All!") used my standard workflow: New empty Unity project + import my necessary code = No 4.3 issues. The 4.3 rejections started with my next game ("Twisty Train"). My mistake: Duplicated the entire "Seat Em All!" project folder, including all .meta files/GUIDs. I now understand this likely triggered spam flags due to identical technical IDs, despite adding new mechanics. My subsequent game ("Egg Pack") unfortunately repeated this flawed copy process from "Twisty Train" and was also rejected under 4.3. Corrective Actions Taken for Latest Submission: For my most recent submission, ("Egg Factory: Sorting Puzzle" - conceptually similar to Egg Pack but built to fix the issue), I took specific, major steps to address the technical duplication: Used a new, unique Bundle ID. Used the "GUID Fixer" tool to regenerate unique GUIDs for ALL assets within the entire project folder. Used a new app name and icon. The Current Problem: Despite these steps to eliminate technical duplication and ensure unique identifiers, "Egg Factory: Sorting Puzzle" was still rejected under Guideline 4.3 Spam. Seeking Specific Feedback & Potential Causes: I'm now trying to understand what, beyond unique technical identifiers, is causing this. I design my games ("Seat Em All!", "Twisty Train", "Egg Factory") to have distinct core mechanics and themes, even if they share my Unity codebase and a visual style. Could the automated review be detecting structural similarities in my own reusable code, even with unique GUIDs, and potentially misinterpreting it as template usage (similar to issues some devs using specific game engines have reported)? Is the consistent visual art style across different themes being flagged? Is the core puzzle/sorting loop considered too similar despite mechanical differences? Request for Call: Getting generic 4.3 feedback isn't helping me resolve this. I've seen other developers mention that a direct call with the App Review team was invaluable for clarifying complex situations like this. Would it be possible to schedule a call to discuss my case? Understanding the specific reason "Egg Factory" is still flagged, despite the technical fixes, is crucial for me to move forward correctly and ensure compliance. Any insights from the community, or specific guidance/a call from Apple Staff, would be incredibly helpful. Thank you, UtkuG

Can someone please guide me on the entire process of integrating ads in an IOS application using google's admob sdk? Not related to code but things related to Apple's privacy policy. Which options do need to select or specify in my app profile's privacy policy (identifier) section?

Hi, I'm working on a large application, and the designers have proposed a new look for the tab bar. The app has been in development for 14 years, and while many views are now in SwiftUI, navigation between screens is still handled in UIKit, since most screens are still UIKit-based. Currently, we're using the native UIKit TabBar. I'm going to check if it's possible to customize the appearance of the native TabBar. However, I remember that over 10 years ago, when I changed the height of the TabBar, the app was rejected during review for not complying with Apple's Human Interface Guidelines. It looked something like this: An app rejection related to a tab bar's height update in Swift, likely due to not adhering to Apple's Human Interface Guidelines, can be addressed by ensuring the tab bar's height remains at the default 49 points and avoiding any modifications that don't align with the HIG, according to Apple's documentation. How does it look nowadays? Has anyone here submitted an app to the store with a heavily customized TabBar height and had it approved? In UIKit, I see it's possible to do something like this: https://stackoverflow.com/questions/23044218/change-uitabbar-height Would something like this pass app review without issues? Do you know of any apps that have a non-standard, significantly increased TabBar height?

I'm using iTunes RSS api for fethching reviews for app store to get customer reviews . In my web-app , I want to show links that will directly open the particular review for an app by the user ,in iTunes or on web . For example , when I make this API call , https://itunes.apple.com/rss/customerreviews/id=1040200189/sortBy=mostRecent/json Response contains: "author": { "uri": { "label": "https://itunes.apple.com/us/reviews/id21684416" }, "name": { "label": "T2theY" }, "label": "" }, "im:version": { "label": "2.1.1" }, "im:rating": { "label": "5" }, "id": { "label": "1431036926" }, "title": { "label": "Love this app" }, "content": { "label": "I use this app to create color boards and to capture simplified shapes as inspiration for art. The best part is they sync seamlessly with all my Adobe applications and appear in libraries automatically. It's so cool and so easy to use. Adobe is making some of the best apps on the market right now!", "attributes": { "type": "text" } }, "link": { "attributes": { "rel": "related", "href": "https:/ } }, "im:voteSum": { "label": "0" }, "im:contentType": { "attributes": { "term": "Application", "label": "Application" } }, "im:voteCount": { "label": "0" } } In above , as far as I cab understand uri : https://itunes.apple.com/us/reviews/id21684416 should take directly to review , however it just opens iTunes's Home and doesn't go any further . Can someone please help me understand how to get link to a particular review that would open iTunes showing that review directly

Here is the English translation of your content:  Section 1: Our game was developed using Cocos Creator 3.8.5, written in TypeScript. The team spent nearly two years completing it. Initially, our submission wasn't classified under Guideline 4.3(a). The first four reviews provided normal feedback, which we addressed. However, after a subsequent rejection citing 4.3(a), we considered whether similarities in gameplay concepts, narrative, or art assets might exist. In response, our team introduced unique features not found in other App Store applications. We completely redesigned our original art assets to ensure originality and extensively modified aspects potentially resembling other developers’ work. This included removing all third-party SDK modules except Apple Pay and Sign in with Apple. Despite these significant efforts, we still received a 4.3(a) rejection. We have now iterated over 20 versions but continue to face this issue.  Section 2: Our game’s business logic code (excluding the Cocos engine code) is entirely original and should not duplicate others' work. Could the rejection stem from similarities in compiled JSC files or binaries generated from JavaScript? Would it be possible for the review team to examine our source code for verification? We are deeply committed to launching on the App Store and can provide comprehensive proof of originality, including but not limited to: Full GIT commit history and source code from inception to present  Documentation proving original art creation  Evidence demonstrating unique gameplay mechanics distinct from other developers  Cocos Creator Engine: https://www.cocos.com/creator-download Games developed with Cocos have successfully launched on platforms like WeChat Mini Games and Android app stores in China, where they are well-received by users. Honorable Review Team, could you please conduct a manual inspection of our source code and evaluate the gameplay? We believe Apple—the world’s most innovative technology company—employs highly professional and insightful experts dedicated to delivering unique, high-quality experiences for players. However, the persistent 4.3(a) rejections are concerning, especially since numerous Cocos-based games are approved globally. We’ve revised the game over six months across 20+ versions, yet each rejection cites identical reasoning:  Apple's Rejection Message Translation: Hello, The issues we previously identified still require your attention. If you have any questions, we’re here to help. Please reply to this message in App Store Connect. Review Details Submission ID: 68 bd1e 18-6 EAA-4a 19-976 e-c 7 B2 E1 ff 0 e 44 Date Reviewed: June 28, 2025 Version Reviewed: 2.3.0 Guideline 4.3(a) - Design - Spam We continue to find that your app shares a similar binary, metadata, and/or concept as other apps submitted to the App Store with only minor differences. Submitting similar or repackaged apps constitutes spam, creates clutter, and diminishes user discovery of genuinely new applications. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review your app concept and submit a truly original application with distinct content and functionality. Support Reply in your preferred language if you need assistance. For further support, use the Contact Us module.  Seek advice from fellow developers and Apple engineers on the Apple Developer Forums.  Request an App Review consultation via Meet with Apple (availability varies based on local hours, Tuesdays and Thursdays).  Provide feedback on this process and your review experience by completing a brief survey.

Hi, I have submitted my app for review since 23/05/2025. Today is 28/05 it still in Waiting for Review status. Please help me look into this issue. We need to release it ASAP AppName: 小马AI学 AppleID: 6745546153 Thank you

Hello, As I searched and know from other developers app review mostly take 24 Hour or less to be reviewed. My app is not revieds since 15 april. Does someone know why it can be happened :( p.s. I wrote support too no answer from them too.

Section 1: Our game was developed using Cocos Creator 3.8.5, written in TypeScript. The team spent nearly two years completing it. Initially, our submission wasn't classified under Guideline 4.3(a). The first four reviews provided normal feedback, which we addressed. However, after a subsequent rejection citing 4.3(a), we considered whether similarities in gameplay concepts, narrative, or art assets might exist. In response, our team introduced unique features not found in other App Store applications. We completely redesigned our original art assets to ensure originality and extensively modified aspects potentially resembling other developers’ work. This included removing all third-party SDK modules except Apple Pay and Sign in with Apple. Despite these significant efforts, we still received a 4.3(a) rejection. We have now iterated over 20 versions but continue to face this issue.  Section 2: Our game’s business logic code (excluding the Cocos engine code) is entirely original and should not duplicate others' work. Could the rejection stem from similarities in compiled JSC files or binaries generated from JavaScript? Would it be possible for the review team to examine our source code for verification? We are deeply committed to launching on the App Store and can provide comprehensive proof of originality, including but not limited to: Full GIT commit history and source code from inception to present  Documentation proving original art creation  Evidence demonstrating unique gameplay mechanics distinct from other developers  Cocos Creator Engine: https://www.cocos.com/creator-download Games developed with Cocos have successfully launched on platforms like WeChat Mini Games and Android app stores in China, where they are well-received by users. Honorable Review Team, could you please conduct a manual inspection of our source code and evaluate the gameplay? We believe Apple—the world’s most innovative technology company—employs highly professional and insightful experts dedicated to delivering unique, high-quality experiences for players. However, the persistent 4.3(a) rejections are concerning, especially since numerous Cocos-based games are approved globally. We’ve revised the game over six months across 20+ versions, yet each rejection cites identical reasoning:  Apple's Rejection Message Translation: Hello, The issues we previously identified still require your attention. If you have any questions, we’re here to help. Please reply to this message in App Store Connect. Review Details Submission ID: 68 bd1e 18-6 EAA-4a 19-976 e-c 7 B2 E1 ff 0 e 44 Date Reviewed: June 28, 2025 Version Reviewed: 2.3.0 Guideline 4.3(a) - Design - Spam We continue to find that your app shares a similar binary, metadata, and/or concept as other apps submitted to the App Store with only minor differences. Submitting similar or repackaged apps constitutes spam, creates clutter, and diminishes user discovery of genuinely new applications. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review your app concept and submit a truly original application with distinct content and functionality. Support Reply in your preferred language if you need assistance. For further support, use the Contact Us module.  Seek advice from fellow developers and Apple engineers on the Apple Developer Forums.  Request an App Review consultation via Meet with Apple (availability varies based on local hours, Tuesdays and Thursdays).  Provide feedback on this process and your review experience by completing a brief survey.

My app was accepted onto the app store yesterday, but i just found out that my subscriptions were rejected for some reason. The localization of each subscription said there was something wrong with it so i changed them and resubmitted them. The issue/question that i have is that now that my app has been accepted with my 1.0.0 version, do i have to submit an update for them to review my subscriptions? or do they review the subscriptions separately because you have to submit the subscriptions for review, the same way you have to submit builds. I just don't want to be waiting around because i can't market my app without those subscriptions accepted

Hello Team, We have Advanced App Clip Experiences live but we have add App Clip experience URL since long ago but status remains as Received and never changed to Published, can you please help us to fix this issue. Please see attached. Thanks

We received a notice from App Review on June 8 requiring us to make some changes. We submitted an updated version on June 10, but the app has remained in the "In Review" status since then. As the review team mentioned that issues must be resolved within 14 days, we’re now getting a bit worried, since the deadline is approaching and there has been no further update. Does anyone know how we can help speed up the review process?

My app has been under review for exactly 35 days. There are no response since the first day, it is just waiting in the In review stage. I canceled it thinking it was a bug and sent it again, but there is no progress. I have sent more than 10 tickets, but no response. I opened a topic in the forum, but there is no response eitheri this is second. There is no place I can reach or ask for help. The Apple team is working great, you are great :) They will probably reply to this post with the words "click this link to get support" and direct me to the link I have previously submitted +10 tickets and have not received a response.

Dear App Review Team, We are raising serious concerns regarding the ongoing review process for the app (App ID: 6737148404), which has once again been escalated to the App Review Board—just days after the previous issue was finally resolved. We submitted a new build on June 18 containing a standard feature update. The app entered "In Review" promptly, but after 3 days with no communication, it has now been escalated to the board again, likely. This pattern is deeply troubling. What’s particularly alarming is that it appears the current reviewer lacks the necessary context or understanding of the app, and instead of engaging with us or taking ownership of the review, they’ve defaulted to escalating it without providing any rationale or feedback. This repeated hand-off to the board without accountability or explanation is effectively grinding our release process to a halt. Based on past experience, we suspect we are now waiting for another board meeting early next week—which means yet another week lost to silence and uncertainty. This is not a scalable or sustainable process. This is one of the top performing apps on visionOS, and yet every iteration—regardless of how minor—is delayed by escalations and inaction. These delays are damaging to our business, destabilizing to our user experience, and increasingly eroding our trust in the App Review process. We urgently request: Immediate clarity on the current review status A direct line of communication with someone accountable for the review An explanation as to why nearly every update requires board involvement We’ve complied fully with all App Store guidelines. All standard support channels have already been exhausted without resolution. This cycle must change. We are ready and willing to work collaboratively, but we need responsiveness and consistency from Apple in return. App ID: 6737148404

Hello, My app Native Talk! has been "waiting for review" for +24 hours. I want to know if this hold up is because of something I need to do on my end or if this is normal. Thank you! Matt

Hello everyone, my app is designed to help people sleep. It has been rejected multiple times due to issues with version 1.4.1 during the submission process. However, the app simply evaluates users’ insomnia and anxiety status based on their responses to questions and provides some relaxation methods. It does not involve any medical-related content. The reviewer provided screenshots of the assessment results page and some relaxation techniques. How should I handle this issue?