I'm building a movie app. For content service, im using cloudflare streaming service. So, I got rejected in my last review. So , how can i solve it ? and the reviewer said, provide en evidence that you have a rights of the content. What kind of permission do i need ?

Hi, I launched and released my app in the App Store after first App build is approved. But its subscriptions are still in the status of Pending Binary Approval. So currently in my App subscription is empty. Is this normal to wail a bit? or should i do something asap. It's very strange for users to see no subscription options in a launched App I think.

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!

Hey everyone, We’re running into a frustrating issue with Xcode Cloud builds submitted to App Store Review. After every build, we must manually delete all code signing certificates generated by Xcode Cloud; otherwise, the reviewers can’t open the exported App Store app. When they try to open it, they see the error: “Apple Information Security: A process was blocked from running and moved to Trash: [Our App Name]” Oddly enough, if we delete all Xcode Cloud-generated certificates and then trigger a new Xcode Cloud build, the problem temporarily disappears—until the next submission, where we have to repeat the process. Has anyone else encountered this issue? Any recommendations on how to prevent this from happening? We’d rather not keep trashing certificates after every build. Thanks!

Hi All, I have been bouncing back and forth with Appstore connect reviewers all week and have jumped through all of their hoops to get the app I am publishing up to the standards required by Apple. The latest problem I get is this: – A functional link to the Terms of Use (EULA) Next Steps To resolve this issue, please add this missing information. If the above information is present, please reply to this message in App Store Connect to provide details on where to locate it. If you are using the standard Apple Terms of Use (EULA), you will need to include a link to the Terms of Use in your App Description. If you are using a custom EULA, add it in App Store Connect. This relates directly to the end-user license agreement whereby we (and I'm sure lots do) use the default Apple EULA. I sent the above attachment only about 15 minutes after receiving hte rejection notice and have waited nearly 8 hours for the app to be reviewed. I have asked for a call-back but nothing. I also advised them there is a link to the relevant privacy policy and terms of use within the app and the privacy policy URL has been provided in App Details, in App Store Connect. I appreciate Cupertino is 15 hours behind where I am, but I am just trying to get my head around how the process is meant to work. Another app I had in review at the same time, had a screenshot that displayed a test ad banner. Fair enough that was rejected, but rectified within 5 minutes of the rejection notice and we are waiting for the review process. Sorry for venting here, but after several days of the to and fro, my patience has worn thin. I am trying to understand the review process and need to know if I have done something wrong, and how best to fix it. Michal C.

Hello, I've developed a dating app and published it on Google Play Store without any problem. I tried to publish it on Apple App Store. But it was rejected because of Guideline 4.3 - Design - Spam reason. I changed some design elements, added some new features and tried to publish it to Test Flight, so my friends with iPhone can test and send feedback to me. But my app was rejected again on Test Flight too with same reason. I guess all new dating apps are being rejected with Guideline 4.3 - Design - Spam reason. I saw a lot of posts about dating apps rejected with same reason. In fact dating app that I developed is for a small group of people and there are (as far as I count) only 5 more dating apps in App Store for same small group of people. My dating app would be the 6th of them, if it was published. I think 6 apps for same group of people should not be too much. So my question is what should I do next? What should I do to be able to pass Guideline 4.3 - Design - Spam and publish this app at App Store? For example should I wait for success of android version of this app. If many users are regularly using this app on android and many iOS users give me feedback as they want an iOS version of this app, and if I present these requests to apple review team, is that help to be published on App Store? Thanks for reply.

My app has been rejected twice (on March 5 and March 11) . 1. Response to Initial Rejection (March 5) After the first rejection on March 5, I thoroughly reviewed the feedback and provided the following evidence to demonstrate the originality of my app: Design Documentation: I shared multiple iterations of the app’s design process, including early sketches and final mockups. Code Provenance: I provided Git version control logs to show the development history and prove that the code was written entirely by me. Explanation of Uniqueness: I explained how my app differs from existing productivity and wellness apps, particularly in its combination of focus and relaxation features. Despite this, my feedback was rejected. I took the feedback seriously and made significant improvements to the app before resubmitting. 2. Changes Made After First Rejection To address potential concerns and enhance the app’s value, I implemented the following changes: Added New Features: Introduced a breathing guide with visual animations and haptic feedback. Expanded the background music library with additional tracks and genres. Redesigned the User Interface: Simplified the layout to improve usability. Rebuilt the Project: Created a new Xcode project to ensure a clean and optimized codebase. Updated the app’s metadata and descriptions to better reflect its purpose and functionality. These changes were made to ensure that the app is not only original but also provides a high-quality user experience. 3. Response to Second Rejection (March 11) After the second rejection, I am concerned that there may be a misunderstanding regarding the app’s originality or purpose. To clarify: No Copying or Spam Behavior: My app is not a copy of any existing app, nor is it a “shell” or “template” app. It has been developed from scratch with a unique design and feature set. No Multiple Submissions: I have not submitted multiple versions of the same app under different Bundle IDs. This is the only version of the app I have submitted to the App Store. So, I appealed to the review team for a reasonable response.

An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

App Reviews are not visible I want to know why my app on the App Store does not show the correct amount of reviews. I asked multiple customers to leave us a review and they did some time ago, but when I check to see the number of reviews, it does not represent the good number. What might be the problem here and what can I do to speed up the process of getting those reviews? Thank you.

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.

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

My application has been stuck in the 'In Review' status for several weeks. After that, I removed it from verification and increased the build number, but still nothing has changed. Today marks 3 days without any response, even though initially I was receiving responses within 24 hours. Are there other people experiencing the same problems, or does anyone have solutions, please? Thank you.

Our app encountered guideline 3.2.1(viii) issues during the review of the updated version. We have been receiving feedback on guideline 3.2.1(viii) since the previous version. After communicating with Apple over the phone and changing our account to use an enterprise email, we successfully passed the review. However, upon submitting this new version, we received the same 3.2.1(viii) guideline feedback again. We have made five subsequent modifications to this version, but Apple's reviewers continue to respond with the same feedback, which prevents us from identifying the root cause of the issue. If you have encountered a similar issue and successfully resolved it, please inform us. We would greatly appreciate any help! Currently, our application is repeatedly rejected due to guideline 3.2.1(viii). I quote as follows: Guideline 3.2.1(viii) - Business - Other Business Model Issues - Acceptable We still found the app provides loan services but the domains listed on the app's Product Pages are not clearly under your control or ownership. Since users may use these domains to contact you to request support, the domains used on the Product Page for loan apps must be under your control or ownership. Next Steps Update the Product Page metadata in App Store Connect to only include domains that are associated with Apple Accounts registered to your developer account. Please note that apps used for financial trading, investing, or money management should be submitted by the financial institution performing such services, as required by App Review Guideline 3.2.1(viii).

Hello fellow devs! My app only has "Sign-in with Apple" sign-in. Should I provide the demo account details for App Review in this case? If yes - how? I just realized that if I give them email & password - it still will not work, cause Apple requires SMS verification from my number linked to that test account. Or should Reviewers be able to test my app with their own test Apple accounts? P.S. I also have ApplePay in-app purchases in the app.

I have a connected application that retrieves Json (3 or 4 times in a session and 670 bytes on average) from a server based on application data. Apple refused my application by providing me with screenshots with very precise states and crash logs .. that I could only reproduce after 2 hours of testing by asking XCODE to place the iPhone in very specific conditions: 100% of packets lost on the network, which is a very rare case you will agree. Does Apple's app validation team use this network mode to test applications? It would be usefull for developer to know.

I'm currently running into an issue during the App Store review process where my reviewer isn't liking how the Screen Time API is being used to hide apps. For some context, my app uses the Managed Settings and Device Activity frameworks in the Screen Time API to allow users to set restrictions on their personal devices and save those restrictions into a preference object that they can switch between. This was detailed as my app's primary purpose in my Family Controls & Personal Device Usage Entitlement Request, which was approved last year. After around a year of working on this app, it's finally done and ready for submission to the App Store. However, my App Reviewer recently rejected the app with this single complaint: Guideline 2.5.1 - Performance - Software Requirements The app uses public APIs in an unapproved manner, which does not comply with guideline 2.5.1. Specifically, your app uses ScreenTime API to hide apps. Since there is no accurate way of predicting how an API may be modified and what effects those modifications may have, unapproved uses of public APIs in apps is not allowed. Next Steps Please revise the app to ensure that documented APIs are used in the manner prescribed in the documentation. All I'm doing is passing a set of Application objects to ManagedSettings.ApplicationSettings.blockedApplications, I'm not doing anything special. The documentation for this API itself states: The system hides blocked applications and prevents the user from launching them. In my reply, I let the reviewer know Regarding Guideline 2.5.1, I believe my use of the Screen Time API appears to align with Apple's documented intended functionality. The specific API I'm using, ManagedSettings.ApplicationSettings.blockedApplications, is explicitly documented by Apple as: "The system hides blocked applications and prevents the user from launching them." This is why I used the term "hide" in my app's marketing and functionality descriptions - I was directly referencing Apple's own terminology for this feature. The documentation clearly indicates this is an approved capability of this API. The source for this documentation can be found here: https://developer.apple.com/documentation/managedsettings/applicationsettings/blockedapplications-swift.property. I've also provided a screenshot of this documentation below. Despite providing a link to the documentation and a screenshot that shows the text from Apple explicitly stating "The system hides blocked applications", the App Reviewer just copy-and-pasted the same text in their reply and rejected the app. I should also note that we don't have control over how the system handles the Application set we pass into ManagedSettings.ApplicationSettings.blockedApplications, the system will always try to "hide" these apps as specified in the documentation. We can't change this behavior. Has anyone else faced this sort of rejection before? Is using ManagedSettings.ApplicationSettings.blockedApplications now considered an illegal use of the API? Or are we not allowed to use the words noted in the documentation of this API? The app rejection suggested I "consult with fellow developers and Apple engineers on the Apple Developer Forums." Any guidance here would be much appreciated as I continue to appeal this. For any Apple staff members reading this post, I can provide the Submission ID of the App Review privately if needed to help resolve this issue.

Hello everyone, After eight months of development, we’ve reached a roadblock and are hoping someone here might have insights into resolving our issue. Our journey started when we decided to create a betting tips app. We initially purchased a template, customized it extensively, and after three months, the app was ready for iOS submission. However, upon review, we received a 4.3 Spam rejection, citing similarities to other apps on the App Store. We scheduled a call with an Apple representative, who informed us that the issue was code-related—the same code had been used in other apps. Taking this feedback seriously, we spent a month modifying the code, but repeated rejections led us to a more drastic decision: we started over from scratch, avoiding templates, AI-generated code, and GitHub repositories. Three months later, we had a brand-new app with a fully redesigned UI, freshly written code, and additional features we had not seen in any other betting tips app on iOS. We submitted the new app under a new package, only to be rejected again for 4.3 Spam. This time, Apple stated that our submission was similar to another app we own. The only issue? Our previous app had never been published—it was only ever rejected. We reached out to Apple for clarification, explaining our situation and asking whether we should update the original app with this new build instead. Unfortunately, the response was vague, and they could not provide clear guidance on how to proceed. Taking a different approach, we updated the original app with a new name, a new description, new screenshots, and the completely rewritten app build. Despite these changes, we were still rejected for 4.3 Spam. We’ve emphasized to Apple that our app contains unique features not found in any existing iOS apps. While they acknowledged our effort in bringing something new to the platform, the spam issue remains unresolved. At this point, we’re considering small design adjustments, such as changing how tips are displayed horizontally instead of vertically, but we’re running out of ideas and hope. Has anyone else encountered a similar situation? If so, how did you resolve it? Any advice or guidance would be greatly appreciated. Thank you in advance!

Has anyone experienced all review delays? We usually get reviewed very fast or within 24 hours. Our last version was stuck in "waiting for review" for 6 days. We resubmitted a newer version yesterday and it's been stuck in the same status. I know apple has introduced a new app submission UX, maybe that's the issue? Anyone is having same delays?

I have tried to appeal many times with clearly mentioning that I am totally innocent in this case but I am getting a same auto generated reply. I think Apple review board doesn't bother reading the appeals and once a developer account is caught by the algorithm, you can't prove that you are right because your appeals will be dealt by the auto generated replies. I am amazed that how a platform like Apple never try to think for even a second that a 3-4 year old developer account with more than 18 high quality games can be terminated within a blink of an eye, don't they even think that this account could be a hope for so many people?. I am really disappointed that I cannot even talk to a human to address how innocent I am and everything is closed just because I got caught by algorithm mistakenly.