I'm hoping that others may be able to assist with my first app submission. **Guideline 2.1 - Performance - App Completeness Issue Description** The app still exhibited one or more bugs that would negatively impact App Store users. Bug description: The app did not load its content. Review device details: Device type: iPad Air (5th generation) OS version: iPadOS 18.3.1 The app pulls in a website embedded to allow them to login to their accounts/place orders. I've tested it on multiple physical devices and using the simulator. It works fine and loads without any issues. The review team would not give me any other information or support to help get this app approved. Any help would be appreciated.

Hi, I uploaded my app to TestFlight and released but mistakenly enabled support for iPads. However, the app does not support iPads, and whenever I submit it for approval, the App Store rejects it due to design issues. When I disable iPad support and re-upload it to TestFlight, I get an error stating that it does not support the previously uploaded platforms. Can anyone please guide me how can i disable it any way around?

Recently, my app was deactivated due to guideline 3.2f, and not only the app but also my account is at risk of being deactivated. After reading the guidelines, we disagree with the pre-judgment made by Apple. During the review process, we addressed EVERY point requested by the review team by correcting the issues. We submitted a new bundle to fix the problems we had with app distribution and ad performance. The first bundle sent was removed after being published on the store for a few months; this was our MVP—a simple and unattractive app that was meant to be improved in the future. Then we launched two other bundles; one of them was canceled and we continued with another bundle to adjust problems we had with Firebase and some libraries. In the screenshot below, it is possible to see the other apps that were supposed to be "deleted," since Apple itself does not allow the deletion of these apps—I do not know why. After we submitted the third bundle to address Apple’s requests and attempted to publish our app, it was approved but exactly 4 days later it was denied and removed from the store, and our developer account was threatened with deletion. We did not commit any fraud in any step of the Apple process; all the steps for an app to be inserted into the store were followed. Our app is a social network that requires location access and permissions—all of which have been configured, implemented, and are requested when the app is opened. We have ads; however, they are completely valid because they are real companies that pay to advertise in our app, and all we do is direct the user to a company’s page when they click on an ad. Our social network includes reporting tools, blocking, unblocking, encryption with locations, among several other best security practices—even our login is SSO. I tried to file an appeal, but Apple’s website itself is broken and the provided link does not allow any kind of appeal. Our app was called Find-u until we secured the patent, and we have the legal right to use this name in Brazil. We also have a company and have started the process of migrating the account from an individual to a corporate account. I would like a response, some guidance. We can prove in many ways that we have done nothing fraudulent, and we are prepared to take legal action for all the trouble that the review team is putting us through. The first version of our app had more than 200 users in the database, and this third version, which resulted in our account being canceled, has infinitely better features and prettier screens than the MVP. It simply does not make sense to cancel our account; if the app presents any defect, we will fix it just as we did before so that it can be approved. CNPJ: 52.070.419/0001-13

Hi everyone, I’m an indie developer and recently published our first app on the App Store. It was an exciting milestone, but on April 4, 2025, after the app had been live for about 1–2 weeks and one update had been pushed, we received a notice from Apple stating that our app had been removed from the store and that our developer account is scheduled for termination within a month. Understandably, this was incredibly alarming—but we stayed calm, carefully read through the allegations, and tried to handle the situation with patience and professionalism. The reason given was: App submissions from your account have engaged in concept or feature switch schemes to evade the review process, such as dynamically populating different app content after review, submitting apps with hidden features, repeatedly submitting misleading apps, and/or submitting apps with concrete references to content that you are not authorized to provide or is otherwise not appropriate for the App Store. This was cited as a violation of Section 3.2(f) of the Apple Developer Program License Agreement. We were accused of dynamically changing game content after review, but we do not have the capability to do anything like that. The game has stayed exactly as it was when submitted, and the single update we pushed included only the changes listed in the “What’s New” section. They also mentioned hidden features. While we don’t hide anything, our game does include progression-based unlocks (such as new upgrade cards or mechanics unlocked as you play). We believe this is standard for many games, and we’ve explained this in our appeal. We also addressed another possible issue—some light pop culture jokes in push notifications—which we are more than happy to remove immediately if they were deemed inappropriate. We’re not here to argue or avoid accountability. If we’ve made any mistakes, we’re more than willing to correct them. But terminating the entire account for a first-time submission, without any discussion or specific feedback, feels incredibly harsh—especially for a small team trying to break into the industry. We submitted an appeal to the App Review Board over a week ago but have not received any response or update since then. So I’m posting here in the hopes of catching someone’s attention—whether that’s Apple or anyone in the community who’s been through something similar and can advise. I know the $99 annual fee might not be a huge deal for many developers, but for someone just starting out, it represents more than money—it’s a foot in the door. I’m not looking for sympathy, just a chance to make things right, follow the rules properly, and keep building on the platform I admire. Thank you for reading, and I truly hope someone can help guide us on the next steps. Best, Veekshith Kolanupaka

Hi everyone, I’m using StoreKit 2 with .storeButton(.visible, for: .policies) inside my SubscriptionStoreView. The buttons appear correctly, but when tapped, a sheet opens that says “Terms of Service Unavailable” or “Something went wrong. Try again.” I’ve already added the required URLs (Privacy Policy and Terms of Use) in App Store Connect under App Information, but they still don’t show in the sheet. Does anyone know how this is supposed to work? • Are the URLs pulled directly from App Store Connect? • Do they only appear correctly in production? • Or do we need to manually set them in code for testing/TestFlight? Any insight would be greatly appreciated — just want to make sure everything is in place before submitting for review. Thanks!

Hello Developer Community, I'm encountering a persistent issue with app rejections related to iPad compatibility, even after explicitly removing iPad as a supported device family in my Xcode project for the latest submission (Version 1.0.1, Build 11). The Apple Review team continues to test on iPad devices (specifically an iPad Air 5th generation running iPadOS 18.4.1) and rejects the build under Guideline 2.1 - Performance - App Completeness, citing a login issue with demo credentials that leaves the app stuck on the login page. In my previous submission and subsequent resubmission, I clearly targeted only iPhone in the Xcode project settings (Target -> General -> Deployment Info -> Devices: iPhone). I also confirmed that the "Targeted Device Families" setting reflects only iPhone. Despite these changes, the review team's feedback indicates they are still evaluating the app on an iPad and encountering the same bug. Their response to my clarification about removing iPad support was: "Regarding 2.1, as we mentioned in our previous correspondence, users expect apps they download to function on all the devices where they are available. Since your app may be downloaded onto iPad devices, it is important that it also function as expected for iPad users." This response is confusing, as my intention with the latest build was to explicitly limit availability to iPhones due to unresolved issues on iPads. ** My Questions are: ** 1: Is there any other setting or configuration in Xcode beyond "Targeted Device Families" that I might be missing to ensure the app is only intended for and tested on iPhones for this specific build? 2: Has anyone else experienced a similar situation where the App Review team seems to be testing on devices explicitly excluded in the build settings? If so, how did you resolve it? 3: What are the potential reasons why the app might still be installable or visible on iPads in the App Store despite the Xcode configuration?

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.

I submitted for the first time my app and in app subscription together. do the subscriptions get approved separately? it seems like a loop. in the paywall of my app only for apple its failing to load payments/subscription info which im assuming to be the fact that my in app subscription didn't get approved yet, its currently waiting for review (first time submitting subscription). Meanwhile the app gets rejected multiple times because the reviewer can't seem to go beyond the paywall due to failure to load payments. Is this the similar experience anyone had? Do you have info that'd be helpful to give to the reviewers?

Hello, We’re seeking urgent help or guidance regarding a serious issue with our app review process. We submitted our iOS app last month. It was rejected three times for various reasons, and each time we promptly resolved the issues and resubmitted. After the most recent resubmission (over a week ago), the app has been stuck in the “Waiting for Review” status. The last communication we received from Apple was: We’ve tried to follow up multiple times via email, as phone support is not available in our country. However, we’ve only received automated responses saying that the review requires additional time. No actual progress or update has been communicated since then. Our launch date is now critically close, and we're concerned that we may miss it due to the continued delay and lack of visibility into the review timeline. If anyone from the App Review team is reading this, or if any developers have been through a similar situation and can share advice, we would deeply appreciate your input. Thank you for your time and support.

Hello, I’ve uploaded a new build of my macOS app with the first two in-app purchases, but it was rejected under 2.1.0 Performance: App Completeness. After further investigation, it seems that the Apple review team is unable to fetch products. The following code: private let productIDs = ["co.app.freetrial", "co.app.full"] self.products = try await Product.products(for: productIDs) is returning an empty array. (In the TestFlight build, it correctly returns the products.) For me, everything works as expected via Xcode and on a fresh machine using TestFlight. Here’s what I’ve tried so far: The in-app purchases were added to the binary with the first build. I confirmed that each in-app purchase is free of any yellow or red warning messages. Downloaded the app from TestFlight and confirmed that all in-app purchases are available. Updated the in-app purchase price in App Store Connect and verified that the new price is reflected in the app (to rule out any ID mismatches). Reviewed all agreements to ensure no missing signatures. (A few sources online suggested that this could potentially cause issues with in-app purchases for the review team.) I created a new build using a 3rd-party certificate and a provision profile. (Older builds - before adding in-app purchases - were signed with a development certificate and no provision profile, yet they still made it to the App Store. I’m not sure how that was possible or if it contributed to this issue.). Despite these steps, the app continues to be rejected for the same reason. I’m struggling to understand how products are successfully fetched for testers via TestFlight while the review team repeatedly sees zero products. Any guidance on how to resolve this would be greatly appreciated. Thank you

Guideline 3.2 - Business We found in our review that your app is intended to be used by a specific business or organization, including partners, clients, or employees, but you've selected public distribution on the App Store in App Store Connect. Since the App Store is intended for apps with a public audience, we recommend reviewing the other distribution options available to you through your Apple Developer Program Account.

Guideline 3.2 - Business We found in our review that your app is intended to be used by a specific business or organization, including partners, clients, or employees, but you've selected public distribution on the App Store in App Store Connect. Since the App Store is intended for apps with a public audience, we recommend reviewing the other distribution options available to you through your Apple Developer Program Account.

Hi everyone, the testflight version of my app has been waiting for review for 10 days and the first version of my app has been waiting for review for 7 days. This is the first time in 2-3 years, does anyone know what is going on?

Hello Apple dev world and teams , I am experiencing anormal Waiting for Review for our app, now for more than a week and decided to post the issue here and hopefully get help. We had successfully upgraded to organization membership and the process with Apple support was really enchanting really responsive, hoping to have the same experience with this issue for review also.

Hello everyone, I’m hoping the community (and maybe someone from App Review) can point me in the right direction. I submitted my new game on 22 April 2025. The build was rejected, so I filed an appeal the same day and re‑submitted it twice after that. The appeal has shown “Waiting for Review” ever since, and I’ve never received the usual “We got your appeal” email, just the generic “We’re seeing higher volume” message. Although this is a fresh developer account, I’ve shipped 50+ apps for other organizations over the years and never ran into a delay like this, so I’m pretty sure the hold‑up isn’t about the actual build. Why it’s urgent:
Influencer promos, community streams, and some paid ads were all timed around the original launch window. After four weeks of silence people assume the game’s been cancelled, and traffic/comments are sliding fast. What I’ve tried so far: Emailed App Review → same volume auto‑reply Used the Contact Us form twice Added a short note in Resolution Center every few days If anyone from App Review sees this or if another dev has broken out of a similar appeal limbo any tip or nudge would be hugely appreciated. Thank you in advance for your time.

My crypto app has been stuck in “Waiting for Review” for 42 days, I’ve contacted Apple and got this response: “At this time, there's no additional information to share regarding your app. It's still in review. We'll contact you if we need further information.” There are just no updates and nothing is moving. Has anyone else experienced this kind of delay recently? especially with crypto-related apps? Would love to know if there’s anything I can do to speed things up? As a note: We already did: - contact them via email - request for expedited app review none of them helped Thanks.

Hi, I have submitted my app for review since 11/05/2025. Today is 13/5 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

Hi everyone, I recently submitted my app for review and it was approved and is now live on the App Store, but the In-App Purchases (IAPs) I created for the same app are still marked as “Waiting for Review” in App Store Connect. When I first submitted the app for review, I did see the option to include the In-App Purchases in the submission, and I did link them. However, that first review was rejected. When I submitted a new version for the second review, I no longer had the option to include the IAPs, and ever since then, even when I create new versions to submit, I’m not given the option to include the IAPs in the submission. As a result, the purchases remain stuck in “Waiting for Review”. I’ve already confirmed that: • The IAPs are correctly linked to the app version. • There are no configuration errors. There’s no option to resubmit the IAPs for review manually, and I haven’t received any communication from Apple about their status. Has anyone else experienced something like this? Any suggestions on how to fix this? Should I contact Apple directly? Any help or guidance would be very much appreciated. Thanks in advance!

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.