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.

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

My app has been stuck 'in review' for 72+ hours. The last thing i got from the App Review team was an email saying "One or more In-App Purchases has been returned." This was the second time i've gotten this email. I feel like the people reviewing my app stops after testing my paywall and doesn't proceed with reviewing the rest of the app. Previously, i had an issue (which has been since solved) with the app review team even reviewing my app at all (waited over 9+ days). I submitted the app for review on a Friday and it's Monday now. I'm not sure if they stop reviewing apps over the weekend. But any help to solve the issue would help

Hi All, So I have been trouble publishing my app on App Store as it keeps rejected by App Review. Specifically guideline 2.3.10 and 3.1.1. Although I don't have any metadata for third-party services in my app or "tip" button anywhere within my apps binary. I do however have external links to my projects help and Github which have that information, which I am getting rejected for. However, I want those external links because I need to have google play on the projects github page so users can know that are visiting to github that they can also download it officially from those sources as well. It is also useful to tell users that those are the only official platforms that I support, and downloading from anywhere else is not advised. Is there an acceptable solution where the google play and donation link can be kept on the github page? It is not really built into the binary itself anyways so I thought it would be allowed. Here is an link to my projects repo in case that helps clarify: https://github.com/SrS2225a/custom_uploader Really hoping to resolve this. I’d love to get the app on the App Store as soon as possible.

Hi, I have submitted my app for review since 05/06/2025. Today is 09/06 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, I submitted my mobile game to the App Store with in-app purchase items. I initially sent my in-app purchases for review for the first time. I had fixed a bug before and thought I could submit a new build with the fix. (Before too much time has passed)I withdrew the previous build and re-submitted the new one. Now, I cannot select in-app purchase items in the new build, and the in-app purchases are still in “Waiting for Review.” Did they get stuck? It has been one day. Even if the in-app purchases get approved, I am unable to choose them in the new build.

I am stuck. Apple asked me to modify the Name/Description of one of my Subscriptions. But the subscription is "In Review" and everything (including the save button) is disabled. It's lierally impossible for me to update the Name/Description like they are asking for. I have tried rejecting my submission but they are still locked. I have asked Apple Review for help - like changing the status so that I can edit them but they won't. I can't get out of review until I modify the Name/Description of a Subscription but I can't update the Name/Description of a Subscription until I'm out of review. HELP!! 😭

Hello, my app was rejected with this reason - Guideline 2.1 - Performance - App Completeness. Bug description: Sign in with Apple requests the Apple ID password rather than entering a code. The issue is that I'm using Clerk inside Expo and they don't support native Apple signIn, only web based. But when users open signIn for the first time - they need to login for appleId via web. I already submitted rejection appeal with explanation. Did someone encounter similar problems? The flow works correctly. In fact even apple testers went through and created accounts.

My application has been in "In Review" status since May 30, 2025, and it is still in that status today. Please check the status of my app, LS Tools. Our customers are waiting for the latest version

Hello, our submission rejected by the apple team and now we can't remove cancel the current submission. This is api response when we attempt remove: { "errors" : [ { "id" : "e069078e-4c57-4aa6-ab3b-913ddf9e6314", "status" : "409", "code" : "STATE_ERROR.ENTITY_STATE_INVALID", "title" : "Resource state is invalid.", "detail" : "Resource cannot be canceled at the moment, please try again later" } ] } We need to publish app asap and can't do anything because of this bug.

I want to clarify why both email and phone number are mandatory at registration, while still allowing users to log in with either method if one fails. Email Address (Collected at Registration) Account Creation & Verification: We use email to establish a unique, verifiable account for each user. This prevents duplicate or fraudulent profiles. Primary Communications: All booking confirmations, trip updates, support requests, and in-app chat messages between care seekers and carers are sent via email. This ensures users have a reliable record of every transaction and message. Phone Number (Collected at Registration) OTP-Based Security: We send a one-time password (OTP) via SMS during registration and login. This SMS-OTP step is critical to confirm that the user owns the provided phone number and to safeguard against unauthorized account access. Critical Trip Notifications: During a booked trip, carers and care seekers must receive time-sensitive alerts (e.g., gate changes, flight delays, check-in reminders) even if they’re not actively using the app. SMS ensures immediate delivery—even if a user’s internet connection is unavailable. Support & Emergency Contact: If there’s an urgent issue mid-trip (e.g., a missed flight, sudden cancellation, or a medical concern), our support team can reach users directly via phone to resolve issues in real time. Flexible Login Options Fallback Mechanism: If a user cannot access their email (e.g., server delay or no internet), they can request an OTP via SMS to log in. Conversely, if SMS delivery fails (e.g., network outage), they can choose to receive a OTP by email. This redundancy guarantees that users aren’t locked out due to a single point of failure. We believe both email and phone number are directly tied to our app’s security model, communication requirements, and overall user experience. All collection and usage details are transparently disclosed in our Privacy Policy (https://b4t.com/legal/privacy-policy) and User Terms and Conditions (https://b4t.com/legal/user-terms-and-conditions).

My app uses Apple IAP. With the recent US external payment changes (May 2025), I plan to use Stripe via Superwall. Superwall allows me to remotely toggle my paywall for US users between Apple IAP and Stripe checkout without a new app build. Is it permissible to activate Stripe for new US users on an already live app version (approved with only Apple IAP) without first submitting a new build for Apple to review the Stripe integration? Or does this dynamic switch create a risk of takedown/compliance problems? Concerned about new users hitting an unreviewed Stripe flow during any potential review period for a new build. Seeking clarity on Apple's stance or community experiences. Thanks!

Hello we just submitted our app one week ago. First submission was rejected and we have resubmitted it after resolving issues with it. but it has been more than 5 days. And we still haven't got any feedback from apple team. We need to publish the app ASAP. Thanks in advance for your help. Looking forward to hearing back from you.

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

in review for long time Apple ID: 6742814997

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?

Build is currently rejected but the submission status is marked as "complete" (even though it isn't). I think this is what's preventing me from replying to the reviewer who is now waiting on info from me. How am I supposed to reply to them if the option is no longer available? I already submitted another build - will they eventually just review that or not? If I expire the build that is rejected, will that get them to stop reviewing it?

Hello, Our new app keeps getting rejected against Guideline 5.1.2(i) - Legal - Privacy - Data Use and Sharing. Submission ID: 65088313-ab97-4557-bef9-8c1cd631e04d The reviewer comment: "The primary purpose of the app still is to encourage users to perform digital tasks in exchange for compensation, watch ads and/or perform other marketing-oriented tasks, which is not appropriate." Next Steps: "Review the app concept and incorporate different content and features." After thorough review of the mentioned guideline (5.1.2(i)) we think our app is totally compliant and transparent, and we feel the rejection reason is not valid neither justified on guidelines. Regarding the reviewer comment: On our app, ads are totally optional. Users do not have to watch any ad on our app to enjoy it's core functionality. We don't require users to perform digital tasks in exchange for compensation, watch ads and/or perform other marketing-oriented tasks. Regarding Guidelines 5.1.2 Data Use and Sharing (i): We don't use, transmit, or share someone’s personal data without first obtaining their permission. We provide access to information about how and where the data will be used in our Privacy Policy and Terms & Conditions, and is only shared with third parties to improve the app or serve advertising (in compliance with the Apple Developer Program License Agreement). User or device data from our app is linked to third-party data solely on the user’s device and is not sent off the device in a way that can identify the user or device, hence we aren't required to use App Tracking Transparency APIs. Our app does not require users to enable system functionalities in order to access functionality, content, use the app, or receive monetary or other compensation. Given these facts, we believe our app rejection is not fair as we are in good standing compliance-wise with App Store Review guidelines. Has anyone else faced this rejection reason before? Any advice on how to approach this situation? Any help would be greatly appreciated, as we have been dealing with the review process for over 2 weeks now...

Dear Apple Team, We would like to bring to your attention an issue regarding our app release schedule. To prepare for our scheduled pre-order launch on June 13, we uploaded our app on April 30. However, that version was closer to a test build than the final release. In anticipation of the official launch, we submitted the final version for review on June 5. Unfortunately, by June 11, the review was still not complete, so we resubmitted the latest final build for review on June 11. Then, quite unexpectedly, the version we uploaded on April 30 was released on June 12 at 11:00 PM. In response, we urgently removed all release countries to stop further downloads. However, due to pre-order notifications, many users downloaded a version that was not intended for public release. Moreover, deleting the countries also canceled the pre-order setup, resulting in the loss of approximately 17,000 users. We would like to emphasize that the build intended for pre-order was clearly set to manual release, with a release date of June 13. Furthermore, that particular build had not even entered the review process as of June 12. We have attempted to reach out through various channels, including email, but have yet to receive a response. We are deeply concerned and have suffered significant damage as a result of this situation. May we kindly ask if something has happened on Apple’s side that might have caused this issue? We would sincerely appreciate your urgent review and support on this matter. Thank you very much.

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?

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?