Hi everyone, I’m seeking some advice on a recurring rejection for our app, tassie., regarding Guideline 3.1.1 (In-App Purchase). The Situation: Our app offers walking tours. While we sell public tours via In-App Purchases (which works perfectly), we also create bespoke, private tours for corporate clients (e.g., a specific company teambuilding event or a private anniversary tour). These tours contain company-specific info and are not available for sale to the general public. The Issue: We use "Partner Codes" (Access Codes) to allow employees of these companies to unlock their private tours. Apple keeps rejecting us under 3.1.1, claiming we are bypassing the IAP system. Our Argument: We believe this falls under Guideline 3.1.3(c) (Enterprise Users). The content is bespoke and created for a specific organization. The end-user (the employee) does not pay for this content; it is a B2B transaction between us and the corporation. The content is not relevant to the general public and therefore not suitable for the public IAP storefront. The Question: Has anyone successfully navigated this? We’ve tried explaining the B2B nature in the App Review notes, but the reviewers seem to hit a wall as soon as they see an "input field" for a code. Should we move the "Partner Code" field deeper into the Profile/Settings to distance it from the Shop? Is there a specific way to document the "Bespoke" nature of the content to satisfy the reviewers? Would an Appeal be the best route, or should we request a phone call (which we are currently scheduled for)? Any insights or experiences with Guideline 3.1.3(c) would be greatly appreciated! Thanks in advance, Danique | tassie.

Hi everyone, I'm hoping to find some guidance — or perhaps connect with others who've faced something similar — regarding multiple app updates from our team that have now been waiting in "Waiting for Review" for well beyond the standard timeframe. To give some context on the timeline: we submitted 3 separate app updates between February 6 and February 12, 2026. As of today, none of them have moved through review. That's now approaching 2–3 weeks of waiting across all three submissions, with no status change in sight. We're a small, independent development team, and like many here, we operate with limited resources and tight planning cycles. These updates carry new features that our existing users have been anticipating, and that we've built our near-term roadmap around. Having all three stalled at the same stage — simultaneously — with no visibility into when they might move, makes it genuinely difficult to plan what comes next, communicate with our users, or commit to any kind of delivery timeline. We've done everything we could on our end: Filed an Expedited Review Request after waiting well past the typical window Followed up with Apple Developer Support via email — it's now been over 4 business days with no response received The uncertainty itself is the hardest part. For a larger organization, an unpredictable review timeline is an inconvenience. For a small team, it touches everything — sprint planning, communication with users, and confidence in the roadmap we've laid out. When multiple apps are affected at once, that pressure multiplies significantly. We have full respect for the review process and everything Apple does to maintain the quality of the App Store. We're simply asking if anyone from the App Review team might be able to look into our submissions, or if fellow developers have found effective ways to navigate situations like this. Any help or insight would mean a great deal to us. Thank you.

Dear Apple Review Team, I am writing to urgently follow up regarding our pending account termination and appeal, as we have not received any response despite multiple attempts to contact your team. For reference, our timeline is as follows: January 31, 2026: Received Pending Termination Notice January 31, 2026: Submitted appeal and corrective update February 7, 2026: Responded to DPLA compliance notice February 12, 2026: Submitted follow-up via Review Board February 23, 2026: Submitted additional summary follow-up via Review Board and Contact Us February 23, 2026: Contacted Apple Support by phone for status inquiry We have fully addressed all identified compliance issues and submitted all requested verification documentation, including government-issued identification, proof of address, and relevant licensing documentation. As of today, our corrective update remains marked as “In Review,” and we have not received any acknowledgment or update from your team. With the February 28 deadline imminent, the lack of communication is extremely concerning. We respectfully request: Confirmation that our appeal and corrective submission are actively under review Clarification on whether any additional information is required from us An estimated timeframe for a decision We are fully committed to complying with Apple’s policies and guidelines and have made every effort to respond promptly and thoroughly. We would greatly appreciate your urgent attention to this matter. Thank you for your time and assistance. We look forward to your prompt response. Sincerely, Tien Nguyen

we have been offered a phone call by apple and we are going to do that but we need to be as ready as possible so here is the rejection we are getting We think we have addressed the issues but are unable to clear this message "Notes from App Review Guideline 2.1 - Performance - App Completeness We have returned your in-app purchase products to you as the required binary was not submitted. When you are ready to submit the binary, please resubmit the in-app purchase products with the binary. Next Steps Learn more about offering in-app purchases in App Store Connect Help. " This is the original message Guideline 3.1.2 - Business - Payments - Subscriptions Issue Description The submission did not include all the required information for apps offering auto-renewable subscriptions. The following information needs to be included in the App Store metadata: A functional link to the Terms of Use (EULA). If you are using the standard Apple Terms of Use (EULA), include a link to the Terms of Use in the App Description. If you are using a custom EULA, add it in App Store Connect. A functional link to the privacy policy in the Privacy Policy field in App Store Connect Next Steps Update the App Store metadata to include the information specified above. Resources Apps offering auto-renewable subscriptions must include all of the following required information in the app itself: Title of auto-renewing subscription (this may be the same as the in-app purchase product name) Length of subscription Price of subscription, and price per unit if appropriate Functional links to the privacy policy and Terms of Use (EULA) The app metadata must also include functional links to the privacy policy in the Privacy Policy field in App Store Connect and the Terms of Use (EULA) in the App Description or EULA field in App Store Connect. Review Schedule 2 of the Apple Developer Program License Agreement to learn more. Support Reply to this message in your preferred language if you need assistance. If you need additional support, use the Contact Us module. Consult with fellow developers and Apple engineers on the Apple Developer Forums. Request an App Review Appointment at Meet with Apple to discuss your app's review. Appointments subject to availability during your local business hours on Tuesdays and Thursdays. Provide feedback on this message and your review experience by completing a short survey. Request a phone call from App Review At your request, we can arrange for an Apple Representative to call you within the next three to five business days to discuss your App Review issue.

I have submitted a new update on February 9th and it's still waiting for review. I will go crazy. There is no way to reach developer support as well. Can someone suggest me what should I do? I emailed, I applied for expedit review but there is no follow up.

I realize there are already several posts here about the unusually long review times for app submissions. There are some replies from Apple stating that they are looking into it or that specific issues have been resolved, but the problem persists and no one seems to understand what is actually happening or what can be done to improve the situation. I have been experiencing the same issue over the past six weeks. My app (submission ID: 75aed892-ee07-49e1-b62b-fdd54f1b04f8) was rejected because the reviewer stated that it needed “citations, such as links to resources.” I therefore added citations with functional links to online resources directly on the page where the claims were made, yet my app was rejected again with exactly the same copy-and-paste feedback. I then asked for clarification, but my question has remained unanswered for a week. There seems to be a fundamental problem in the App Store review process. For me, it has become a cumbersome issue, as the unexpectedly long response times are causing me to miss deadlines with my customers. We fix and resubmit our app within minutes, literally, but every time we have to wait weeks for the next reply from Apple. Should we pause submissions for a while and focus on other activities, and manage expectations with our customers accordingly? Or is this a temporary situation that is likely to improve soon? Any insights or tips would be much appreciated. Thank you.

Hello, I would like to formally raise a concern regarding an ongoing lack of communication in the review process. Two of my applications have been in the “Waiting for Review” stage for an unusually extended period. During this time, I have: • Sent multiple support emails • Submitted an expedited review request • Attempted to follow up through official channels Despite these efforts, I have not received a single response or status update. I understand that review timelines can fluctuate depending on workload and complexity. However, prolonged silence without acknowledgment creates uncertainty and directly impacts release planning, user acquisition strategy, and overall operational decisions. This is not a complaint about review duration alone. It is primarily about the absence of communication. Even a brief confirmation or estimated timeline would significantly improve the situation. I respectfully request clarification on the status of these submissions and the reason for the continued “Waiting for Review” state. I sincerely hope this matter can be resolved promptly. Thank you for your time. Best regards, Berkay

I'm not sure where to go from here, I've filled in the "appeal" form but had no response. My app has somehow been interpreted to 'only work with specific hardware' - this is not the case it works wither either specific hardware OR a third party piece of software (which is freely available) The third party software provides a TCP server and my app connects to it as a client. I have been rejected four times now because I haven't provided a 'video to show the paring process with the dedicated hardware' There isn't a 'pairing process' any more than there is a pairing process between Safari and a website or Mail and an IMAP server, it literally connects to the specified IP and Port. I've provided a video of this (showing a screen capture of the software in question, and a screen capture from an actual iOS device - my iPhone - showing me connecting to the other application in the app, and demonstrating the functionality of the app - but keep being told I need to provide a video with hardware. I don't own the hardware version, I use the software version. It's exactly the same process and software whether it is running on hardware or software.

Apple platforms make it easy to distribute your app to a variety of compatible devices, so it’s important to maximize your app experience on each platform you support. Here are some tips from App Review to help you understand how device compatibility impacts your app’s distribution — and how to make sure your apps shine on every platform they’re on. Understand device compatibility There are many ways an app built for one Apple device can run on other Apple devices: Apps designed for iPhone can run on iPad devices in compatibility mode if there are no dependencies on iPhone device capabilities. Compatible iPhone and iPad apps can run unmodified on Macs with Apple Silicon. Compatible iPhone and iPad apps can run unmodified on Apple Vision Pro. Xcode provides options to configure settings for apps on multiple platforms. You can specify which platforms your app’s target supports in the Supported Destination field. However, it’s important to note: People may still be able to run your app on a device even if you remove it or don't include it as a Supported Destination in Xcode. For example, as long as an app designed for iPhone doesn’t depend on a capability that’s only available on iPhone, it can be downloaded from the App Store onto iPad. Adding or removing iPad as a Supported Destination in Xcode won’t change that app’s availability on iPad. To view examples of cases where it's appropriate to restrict availability, see Restrict device distribution below. Follow compatibility best practices 1. Plan and test for compatibility modes so your app works on every device where it can be downloaded. Do: Use Xcode simulators to verify basic functionality across different device types. Leverage TestFlight with external testers who have access to a wide range of Apple devices. Don't: Don’t submit for review without testing your app’s behavior in compatibility modes. Don’t assume removing a supported destination in Xcode prevents distribution to that device type. 2. Build adaptive interfaces that work across device variations. Do: Build interfaces that respond to different screen sizes and orientations. Adapt features based on available hardware, providing alternatives for a consistent experience. Don't: Don’t design rigid interfaces that assume only one type of device or input method. Don’t let your app crash or become unusable when optional hardware is unavailable. Restrict device distribution Wherever possible, it’s best to make your app available on multiple platforms to increase its reach and provide people with a consistent experience across devices. But there are cases where it does makes sense to restrict an app’s availability. For example: iPhone apps that rely on iPhone-specific hardware won’t function as expected on iPad. Use the UIRequiredDeviceCapabilities key in the information property list file to specify hardware dependencies. Note: Apps should only use the UIRequiredDeviceCapabilities key for genuine hardware dependencies, not to indicate distribution preferences. Navigation- or camera-based apps are not well suited for visionOS. Learn more about managing availability of iPhone and iPad apps on Apple Vision Pro. Apps that rely heavily on touch inputs that can’t be replicated on a keyboard are not well suited for macOS. Learn more about restricting distribution to Apple Silicon devices. Learn more about how to configure multiplatform apps in Xcode. Support If you need more assistance, explore these support options: 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 through Meet with Apple. Appointments are available during local business hours on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board.

I am looking for some guidance regarding a significant delay in the review process for my app update. Platform: iOS Submission Date: February 10, 2026 Current Status: Waiting for Review It has now been 16 days, and the status has not progressed to "In Review." I have checked my App Store Connect "App Review" section, but there are no outstanding requests for information or messages from the review team. I have already attempted to contact the App Review team via the official "Contact Us" form but have only received generic automated responses. Is anyone else experiencing similar delays this month? Are there currently known backlogs, or should I consider canceling this release and re-submitting? Thank you for any insights.

When creating the marketing/promotional material for my app, I reviewed many popular apps to see what was permitted and accepted to the app store. I saw many apps like headlines and image content of text saying "Quit Porn" or similar. Upon submitting my app for review, it was later rejected and one of the reasons was having titles and texts in the marketing saying "Quit Porn". Why is this? (The app is an app to quit porn addiction)

Hello, I would like to raise a concern regarding the review status of my apps. Both of my submissions have been in the “Waiting for Review” stage for an extended period of time. Additionally, I have sent multiple support emails and even submitted an expedited review request. Unfortunately, I have not received a single response to any of them. As a long-time Apple developer and someone who genuinely values the Apple ecosystem, I find this prolonged silence concerning. Extended waiting periods without any feedback create uncertainty and negatively impact the overall developer experience. I fully understand that review times can vary. However, the lack of communication is the primary issue here. Even a brief status update would be greatly appreciated. I sincerely hope the review process moves forward soon and that we can resolve the current “Waiting for Review” situation as quickly as possible. Thank you for your time and consideration. Best regards, Berkay

More than 2 week's ago submitted 3 apps, and it's still stuck on "In Review" status with zero updates. No updates in statuses. No updates from email support Apple Team. We create some tickets on support tab, but no updates from Apple Team. Apple’s review process usually isn’t this slow, so I’m starting to wonder if something’s broken on their end… Would appreciate any insights or updates from others who’ve managed to get through this too!!! Can you please help us to resolve this issue?

Hello, I have a policy-related question regarding App Store Review for dating apps. As a development agency, we build apps based on client requirements. Recently, we received feedback from App Review stating that the dating app category is saturated and that the app should demonstrate unique features to avoid being considered spam or a duplicate of existing apps. In such cases, what is the recommended approach for developers working on client projects? If a client requests a standard dating app with common features (profiles, matching, chat, etc.), is it likely to be rejected under the spam/duplicate guideline (4.3)? Should developers proactively advise clients to include clearly differentiated features before submission, even if the app is functionally complete and complies with technical guidelines? Any clarification on how App Review evaluates dating apps for uniqueness under Guideline 4.3 would be very helpful. Thank you.

I’ve been building iOS apps since 2011, took a 4-year break, returned with two new apps, and it feels like organic visibility and indexing have changed drastically compared to earlier releases. Has anyone else noticed slower indexing, fewer automatic mentions, and almost zero organic traction—has discovery changed, or is it just saturation?

When creating a new App Store version to update ASO keywords and metadata, I notice that elements like the app icon and other details are missing and I am looking for a way to copy the existing metadata from the previous version. Also, is it possible to submit a new App Store version solely for ASO improvements without uploading a new build and still have the changes applied successfully.

I take a lot of screenshots such as tickets, ideas, chats, and receipts, but I often forget about them later, so I am considering building an iOS app that asks the purpose of a screenshot as soon as it is taken, lets you assign it to a category, and reminds you after a set number of days to turn screenshots into actions instead of clutter. Before starting development, I would love to know if this feels genuinely useful, whether you would consider paying around $2 per month for it, and what features you would like to see, as I truly appreciate any honest feedback.

Hello Apple Review Team, I am writing to inquire about the review status of my two apps, which are still in the “Waiting for Review” stage: Healthoria: Health Diary – Submitted on Feb 5 at 7:01 PM OrbitGoals – Submitted on Feb 17 at 4:11 PM Could you please provide an update on the expected review timeline? I want to ensure there are no issues or missing information delaying the process. Thank you for your assistance. Best regards, Berkay

Hello everyone, I am facing a very frustrating situation and wondering if anyone else has experienced this or if an Apple engineer can help. My app (App ID: 6756897429) has been stuck in "Waiting for Review" for 13 days (since Feb 12). I had a previous rejection for a Guideline 5.2.1 (Trademark) issue. I completely fixed it, uploaded a new build, and submitted it for review. Since then, total silence. I have tried: Opening a ticket (Case ID: 102820782519) -> No response. Sending follow-up messages via Contact Us -> No response. Uploading a new build to "wake up" the system -> Still stuck in Waiting for Review. I am not asking to skip the line; I just want to know if my app is stuck in a system glitch because 13 days of silence is not normal. Can any Apple representative here please check my App ID or escalate this? I am totally blocked.

New version of our App was uploaded 2 days before. Still it is in waiting for review, not yet available for testing. It is just a minor version that is being updating to. No major changes have been included as part of the new release, still it is taking high time even for getting the build available for testing. Please expedite the process.