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.

Here are some tips from App Review for a smooth review experience. We’ve split them into two categories: Before You Submit and After You Submit. We’ve also made an easy-to-follow Submission Guide you can save and reference at any point on your App Store journey. Before You Submit Tips Enable a complete review. Make sure you’ve provided demo accounts or implemented an account demonstration mode before you submit. We’ll need to review the entire app experience, both with and without an account. Provide up-to-date demo account login credentials in the App Review Information section on the app version page in App Store Connect. If your app has multiple account types (such as admin and general users), use the Notes field to provide additional demo account credentials for each account type. If your app requires an authentication code in addition to the login credentials, provide the code in advance in the Notes field. Otherwise, a call may be required to complete the review. Apps that handle sensitive user information, or operate in highly regulated industries, can implement demonstration modes that exhibit full features and functionality while using demonstration data. Use the Notes field in App Store Connect to provide information to App Review. The App Review Information section of App Store Connect includes a Notes field. Provide any information that could be relevant to your submission’s review: Submitting a new app? Tell us about your app's concept, business model, and if your app is designed to only operate in certain locations. Submitting an update? Tell us about what’s changed and where to locate significant new content or features. Connecting to hardware? Attach a video, not a screen recording, that shows both the hardware and the app running on a physical Apple device as they pair and interact. Test your app on physical devices before submitting for review. Use TestFlight to distribute your app for beta testing. App Review evaluates apps the way your users will use them: installed on real devices and connected to networks with real-world conditions. Make sure your pre-submission testing includes running the app on each device platform where it could be used. Users expect the app to function on all the devices where it’s available. TestFlight will help you do quality assurance and beta testing on real devices. Share your beta app with internal testers on your Apple Developer Program account or to external users via an email invite or public link. Configure In-App Purchases for review in the sandbox environment. App Review assesses In-App Purchases in the same sandbox environment Apple provides for testing them. The sandbox lets us use real product data and server-to-server transactions, without incurring any financial charges. Take these steps to prepare your In-App Purchases for review: Accept the Paid Applications Agreement in App Store Connect. Submit the In-App Purchases in App Store Connect that you’d like reviewed. Follow the steps in TN3186: Troubleshooting In-App Purchases availability in the sandbox if your app fails to display your In-App Purchases. Note: In-App Purchases don’t need prior approval from App Review to function in review. Join a Meet with Apple event if you need assistance before you submit for review. Request an App Review appointment through Meet with Apple to chat with an App Review expert about how to prepare for review, ask questions about specific guidelines, and discuss other topics related to the review process. Appointments are subject to availability during your local business hours on Tuesdays and Thursdays. After You Submit Tips Contact App Review if you need assistance with an ongoing submission. If your submission doesn’t pass review and you have questions, contact App Review directly by clicking Reply to App Review in App Store Connect. You’ll receive a reply from a review specialist who’s familiar with your app. You can also use the Reply to App Review message window to request a call with an Apple representative. Include your preferred time and language for the call and we’ll do our best to accommodate your requests. Use the Bug Fix Submissions process to quickly deliver bug fixes and resolve other issues on the next submission. If an update includes bug fixes and is rejected, you will be given the option to resolve the issues on your next submission, as long as there are no legal or safety concerns. App Review will let you know if your submission is eligible by including this note at the top of the rejection message: Bug Fix Submissions The issues we've identified below are eligible to be resolved on your next update. To accept this offer, simply reply to the rejection message in App Store Connect and let App Review know you’ll resolve the issues on the next submission. Share ideas with Apple about how to improve or clarify the App Review Guidelines by submitting guideline feedback. Just as the App Store is always changing and improving to keep up with the needs of customers, the App Review Guidelines may be revised to provide new and updated guidance. If you have ideas for improving or clarifying our requirements you can suggest guideline changes. If your submission was rejected but you believe it follows the App Review Guidelines, consider submitting an appeal to the App Review Board. If your submission didn’t pass review but you have reason to believe it follows the App Review Guidelines, you can submit an appeal to the App Review Board. You can also file an appeal if you think we misunderstood your app or the review was unfair. The App Review Board will contact you as soon as they complete their investigation.

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'm developing a sandboxed clipboard history manager for macOS. When a user selects an item from their clipboard history, the app: Writes the data to NSPasteboard.general Posts a ⌘V keystroke via CGEvent.post(tap: .cgSessionEventTap) This requires the user to grant permission under System Settings > Privacy & Security > Accessibility (kTCCServicePostEvent). The app does not use any Accessibility framework APIs (AXUIElement, AXIsProcessTrusted, etc.) — only Core Graphics event posting. The app has been rejected twice under Guideline 2.4.5, with the reviewer stating that Accessibility features should not be used for non-accessibility purposes. My understanding is that kTCCServicePostEvent (used by CGEvent.post) is a separate TCC service from kTCCServiceAccessibility (used by AXUIElement APIs), but both appear under "Accessibility" in System Settings, which may be causing confusion. My questions: Is there an approved way for a sandboxed Mac App Store app to simulate a keystroke (specifically ⌘V) after writing to the pasteboard? If CGEvent.post is not appropriate for App Store apps, what alternative API should clipboard managers use to provide a "paste" action? Is there a way to use CGEvent.post that is compliant with Guideline 2.4.5? I have a minimal sample project (single Swift file, sandboxed) that demonstrates the behavior. I can share it if helpful. I was referred here by DTS (Case-ID: 19088416).

Hello, I ran into an issue today after receiving a metadata rejection. My current situation: Rejection (Guideline 2.3.2): My app was rejected for its Metadata — I needed to update the description to clearly disclose that full access requires an in-app subscription as requested by the reviewer. Accidental Resubmission: Before reading Apple's instructions carefully which stated I did not need to resubmit and only save the new app description, I accidentally hit "Add for Review" instead of simply saving the updated description and replying via App Store Connect. App Store Connect Reply Option: After cancelling the accidental submission, the App Store Connect reply option became inaccessible. Current State: I've since resubmitted via "Add for Review" with the corrected description already in place. Previous Review time: I have previously experienced an unusually long "Waiting for Review" period — significantly past the 24–48 hour window before my review. Current App Status: My Current App Status shows "Waiting for Review" again and I am afraid I may have restarted the entire review even though my app was only rejected for the App Description and I may have to wait a long time now as I did for my previous review. Developer Support Email (Case ID: 102905099480): I've also contacted app support and have received no response as of yet. Developer Support Phone Call: When navigating to App Review under Apple Support, the option to request a phone call is not available for this issue. Has anyone else had this problem? And what should I do? Thank you.

I am experiencing a critical and frustrating delay with an internal business application review. I would highly appreciate any insights or advice from the community or the Apple team on how to move forward, as our business operations are heavily impacted. Here is the exact timeline of our submission process: May 14 & May 19: Submitted the initial builds. On both occasions, the app transitioned to In Review within 4 hours but was rejected due to specific metadata/compliance deficiencies. Resolution: We thoroughly addressed all the points mentioned in the rejection notes, completed the missing requirements, and prepared a fully compliant build. May 22: Resubmitted the corrected build. Unlike the previous quick turnarounds, the app became completely stuck in the queue (Waiting for Review) with zero communication or updates for over a week. June 1: Out of concern that the submission was caught in a system glitch, I canceled the review and resubmitted it. It is currently still waiting with no status change. Expedited Review: I submitted an Expedited Review request detailing our urgent operational needs, but we have received no response or acknowledgment yet. Business Impact & Context: This is an essential internal tool for our business operations. We currently have 20 employees utilizing it via Ad Hoc distribution, but we are actively onboarding new personnel who need immediate access to the app to perform their daily duties. The limitations and manual management of Ad Hoc distribution are now causing a severe bottleneck in our daily workflows. Given that the first two reviews started within hours, it feels like the app has been flagged or placed into a different administrative review queue after the rejections, but the complete silence is hurting our business. Has anyone dealt with a similar sudden freeze after fixing rejection points? Are there any alternative communication channels available when both App Store Connect and Expedited Review forms go completely unanswered? Thank you in advance for your time and help.

I'm getting repeatedly rejected under Guideline 2.1(b) - App Completeness, with the message that the in-app purchase products "failed to load." This has happened on multiple submissions now, and I'm stuck because everything works fine on my end. My setup: 2 auto-renewable subscriptions + 1 in-app purchase, all in "Waiting for Review" status and attached to the current version (1.0.0). All three products load and purchase successfully when I test via TestFlight with a Sandbox account. No errors at all. Paid Apps Agreement, banking, and tax forms are all Active. I have another app on the same account where IAPs are live and working, so I don't think it's an account/agreement issue. Review device was iPad Air 11-inch (M3), iPadOS 26.5. One detail that might be relevant: this account was migrated from an individual to an organization account a while back, and there were some app transfers involved on the account (though not for this specific app). What I've already tried/confirmed: Product IDs in code match App Store Connect exactly. Products are attached to the build (there's no separate section to re-attach them on resubmit, which I understand means they're already linked). Resubmitted multiple times with the same result. My questions: Has anyone seen IAPs load fine in Sandbox/TestFlight but consistently fail in App Review specifically? What was the root cause? Could the individual-to-organization migration or prior app transfers cause IAPs to fail loading only in the review environment, even when agreements show Active? Is there anything region/storefront-specific that would make SKProductsRequest / Product.products(for:) return an empty list for the reviewer but not for me? Any pointers would be hugely appreciated. Thanks!

Hello everyone, I'm facing an unusual issue with App Store Connect. My app has been in the "Ready for Distribution" status for over 2 weeks (17 days) now. Normally, distribution starts within a few hours after approval, but in this case nothing happens. What I already did: The app successfully passed the review (status is green / approved). Distribution is set to automatic release (I also tried manual — no difference). I submitted a ticket to Apple Developer Support via the official form few days ago. Ticket number: Case ID: 102898955253 I haven't received any response from Apple so far — not even an automated acknowledgment beyond the initial one. Checked spam/junk folders — no emails from Apple. My question to the community: Has anyone experienced such a long delay in the "Ready for Distribution" state recently? Is there any way to "nudge" the process without waiting for Apple Support? Would re-submitting a new build (incrementing the version number) help reset the state? Any advice would be greatly appreciated. Thank you.

Hello App Review Team, My app was first submitted (version 1.0.0) on May 6. Since then, I have submitted multiple bug-fix updates, but none of them have ever entered the actual review process – they have remained stuck in "Waiting for Review". My latest version is ready and currently waiting for your team to begin the review so it can be released on the App Store. App information: App ID: 6764726742 First submission date: May 6 Latest version waiting: 1.1.1 I would like to ask: Is there any account, agreement, or metadata issue preventing my app from entering the review queue? When can I expect the review to actually start? Our users and business have been waiting for the iOS version for a long time. Any clear guidance from your team would be greatly appreciated. Thank you for your time and help.

Hello Apple Developer Support Team, I would appreciate your assistance regarding a prolonged review delay for my app. App Name: Chat Mate for Messenger App ID: 6762255821 My app was previously rejected, and after addressing the review feedback, I resubmitted the update. However, it has now been 14 days and the app remains in "Waiting for Review" status without any further communication or review activity. This project is extremely important to me and my team. We have worked diligently to resolve all issues raised during the previous review and are very eager to launch the app. The extended delay is significantly impacting our planned release schedule and ongoing work. Could you please investigate the status of this submission and help move the review process forward if possible? We would greatly appreciate any update or assistance in getting the app reviewed and, if approved, made live as soon as possible. Thank you for your time and support. Best regards, Muhammad Ahmed

Hello Apple Developer Support, I am posting here as a third attempt to get assistance with an App Review issue that has now been ongoing for more than one month and is causing significant harm to our business. Our app has been going through a prolonged back-and-forth review process for over a month. The issues raised during review have been relatively minor and administrative in nature. For example, one review asked us to confirm subscription pricing, and another asked us to make subscription names more unique, even though those same names had not previously been flagged as problematic. Each time we address the requested changes and resubmit, we wait again, only to receive another simple clarification request weeks later. As a result, we have been unable to launch our product despite making every effort to respond quickly and comply with all review requirements. This situation has become extremely critical for us. We already have a marketing team and launch activities prepared around this product, and the inability to obtain a basic approval after more than a month is causing substantial business damage. I have also attempted to contact Apple Developer Support by phone today. I requested a callback and received one, but I was unable to proceed because the automated phone system did not recognize my keypad responses. Additionally, when requesting support callbacks, the website frequently displays an error message stating that there was a problem processing the request, despite callbacks sometimes still being generated. We have already posted in the Developer Forums twice regarding this matter and were informed that the issue was being looked into. Unfortunately, the situation has never been resolved, which is why I am posting again. I would greatly appreciate if someone could: Escalate the review of our submission. Investigate why this review process has been stalled for over a month. Contact me directly via email or phone regarding this case. This matter is now highly time-sensitive and has a direct impact on our business operations. Thank you for your time and assistance. Best regards, Jevgenij App ID: 6765609730 Current Status: Waiting for Review Case ID: 102905910960

I am experiencing a significantly long review period for my macOS app. I submitted my app for review on May 25th at 8:58 PM, and it has been stuck in the 'In Review' status since then. It has now been over a week without any updates or feedback. I have noticed a recurring pattern of macOS app reviews taking much longer than usual lately. Is there a known backlog or a change in the review process for the macOS platform? It would be helpful to know if others are facing similar delays to understand if this is a broader trend at the moment. Thanks in advance.

We’ve been waiting for an extended period on a financial application, and unfortunately the version currently live on the App Store contains performance issues that have already been fixed in our pending update. We’ve submitted an expedited review request and contacted App Review twice, but haven’t received any guidance. At this point we’re honestly a bit lost on what else we should be doing. Any advice from developers who have gone through something similar would be greatly appreciated. App id 6753857720

Dear Apple Developer Support, I am writing to bring to your attention that our app has been stuck in “Waiting for Review” status for 5 days now with no progress whatsoever. We have already resubmitted the app, but since resubmission, the app has remained in “Waiting for Review” with no movement. This app is critically important to our business, and the speed of publication has never been more urgent. Every day of delay is directly impacting our operations and our users who are waiting for this release. Additionally, we have attempted to submit an expedited review request multiple times through the official Apple expedited review request form. However, each time we try to submit the request, we receive the following error message: “Sorry, we didn’t receive your request. An error has occurred and your submission wasn’t completed. Please go back and try again. If you continue to have issues, contact us.” Because of this issue, we are unable to submit an expedited review request through the normal process. We kindly request that you: Prioritize our app for review and move it forward as soon as possible. Provide an estimated timeline for when the review will begin. Contact us if any additional information is needed — we are ready to respond immediately. Help us manually process or escalate the expedited review request, since the official expedited review request form is not working. We would greatly appreciate your help in expediting this process. Apple ID: 6760743106

Hi everyone, I'm building an iOS app (a language-learning app) with an unusual monetization model, and I'd like to confirm how StoreKit / IAP guidelines apply before I implement payments. The model Users set a "commitment": they pledge to complete one short quiz every day. If a user skips (no activity for two consecutive days), a pre-agreed penalty amount (e.g. 500 JPY) is automatically charged to the card they registered at sign-up. The app itself, and all learning content, is free. Users are NOT paying to unlock features, content, levels, or any digital goods. The charge is purely a commitment/accountability penalty, similar in spirit to services like Beeminder or stickK. The money is a consequence of NOT acting, not a purchase of anything. My question Would this penalty charge be considered a purchase of "digital content or services" that must go through In-App Purchase (per Guideline 3.1.1)? Or, because the user is not buying any digital goods/features and the charge is a real-world commitment penalty, would it be acceptable to process it through an external payment provider (e.g. Stripe)? I've read Guideline 3.1.1 and 3.1.3, but I'm unsure which category a "penalty for inaction" falls into, since it doesn't unlock anything in the app. Any guidance, or pointers to relevant guideline sections or precedents, would be greatly appreciated. Thank you!

My app OneNest (App Store ID: 6762323106) has had in-app purchase localizations in "Waiting for Review" status for nearly 2 weeks. My subscriptions were approved but the localization for both the subscription and lifetime purchase IAPs remains pending. This is actively blocking customers from completing purchases in my live app. I have an open support ticket but have not received a response in 2 weeks. Has anyone experienced this? Is there a way to escalate IAP localization review specifically? Any guidance would be appreciated.

Hello, I've been experiencing an unusually long wait for my app review. My current situation: Status: Stuck in "Waiting for Review" — significantly past the 24–48 hour window with no progress. Developer Support (Email): I've submitted a Developer Support case (Case ID: 102905099480), no response received as of yet. Developer Support (Phone):When attempting to contact Apple Support, the option to request a phone call does not appear to be available for this type of issue. Has anyone else encountered this issue? And what should I do? Thank you.

I am writing to bring to your attention that our app has been stuck in "Waiting for Review" status for 4 days now with no progress whatsoever. However, since resubmission, the app has remained in "Waiting for Review" with no movement. This app is critically important to our business, and the speed of publication has never been more urgent. Every day of delay is directly impacting our operations and our users who are waiting for this release. We kindly request that you: Prioritize our app for review and move it forward as soon as possible. Provide an estimated timeline for when the review will begin. Contact us if any additional information is needed — we are ready to respond immediately. We would greatly appreciate your help in expediting this process.

Hi all — looking for any escalation path for two production-impacting submissions currently stuck in WAITING_FOR_REVIEW. Both apps' live App Store versions are broken for 100% of users; the submissions contain minimal, scope-limited fixes (no new APIs, entitlements, data collection, or UI). The Android equivalents are already live and verified working. MeetingMind: AI Note Taker (Apple ID 6757317991) — v6.1.2 / build 49, submission ID f88195d3-6c35-4e6d-a7a9-6f34b44bf0e7. Waiting since 2026-05-24 (3+ days). Bug: outbound phone calls fail to relay audio from the called party to the caller. Fix: ~5 lines in VoipService.swift. ReadAloudAI: Voice Reader (Apple ID 6757346255) — v7.9.1 / build 38, submission ID 21f4510f-4690-4d15-b559-437f89e037ca. Waiting since 2026-05-26. Bug: backend Cloud Run URLs retired, text-to-speech (core feature) fails for all users on v7.9 and earlier. Fix: configuration-only URL migration to Fly.io. Already done: expedited review filed via the contact form earlier today (no acknowledgment), email to appreview apple.com, Notes for App Review updated with reproduction + verification steps. Has anyone had success with another escalation channel in similar situations? Any Apple staff who could take a look would be deeply appreciated.

Hello, I am requesting urgent assistance with my app review. I have been through multiple rejection cycles, addressed every issue raised, and resubmitted, but I have not received any response on my most recent submission despite having an active expedited review request. Here are my details: App Name: BitzaHugs Original Submission Date: 05/24/2026 Expedited Review Requested: 05/30/2026 Current Status: Waiting for Review Support Case #: 102903001544 I have fully resolved all previously cited rejection reasons and resubmitted accordingly. My intended launch date has now passed by two days and every additional day of delay has direct business impact. I am not seeing any flags or errors in App Store Connect on my end. I would greatly appreciate any escalation or update on the status of this review. Thank you for your time, Amanda Benavidez

Hi App Review Team, Our app was rejected under Guideline 1.1. After implementing all requested changes, the app was approved. The next version was approved without any rejection. The following version — with no new functionality added — was rejected again under the same Guideline 1.1. Our follow-up correspondence with the App Review Team did not produce results, and our requests for specific clarification went unanswered. We submitted an appeal to the App Review Board on May 15, 2026. As of today, no response or decision has been received. Contacted Developer Support as well on May 28 via Contact Us → App Review → App Review Status (case ID 102901983790), also no response yet. Could the App Review Team please look into the status of our appeal and confirm it is in the queue? Any guidance on next steps would be greatly appreciated.

Dear Apple Developer Support, I am writing to bring to your attention that our app has been stuck in "Waiting for Review" status for 4 days now with no progress whatsoever. However, since resubmission, the app has remained in "Waiting for Review" with no movement. This app is critically important to our business, and the speed of publication has never been more urgent. Every day of delay is directly impacting our operations and our users who are waiting for this release. We kindly request that you: Prioritize our app for review and move it forward as soon as possible. Provide an estimated timeline for when the review will begin. Contact us if any additional information is needed — we are ready to respond immediately. We would greatly appreciate your help in expediting this process.

Hello, I submitted an update for my app a week ago "May, 26 at 8:28 PM" . The app was previously reviewed and rejected, and after that I carefully followed all the review feedback and guidelines, made the requested changes, and updated the Review Notes with much more detailed explanations about the gameplay experience. Since then, I’ve been waiting more than a week for the new version to move forward in review. This update also contains an important RTL fix that I urgently need to release for users. I would really appreciate any guidance or help, and thank you very much for your time.