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.

Hello, We are seeking guidance regarding our developer account, which is under a Pending Termination Notice under Section 3.2(f). We deeply respect the App Store Review Guidelines and the standards Apple sets to keep the ecosystem safe and trustworthy. We take these rules seriously and submitted an appeal to the App Review Board and, following our correspondence on May 29, provided a full set of additional corrective actions to address the issues identified and bring our products into full compliance — including a mandatory internal compliance process to ensure we meet Apple's standards going forward. It has now been about two weeks, and we have not yet received a response on these latest materials. We have an 8-year history as an Apple Developer Program member, and we want to resolve this properly and rebuild trust. We would be grateful for any guidance from Apple Team or the community on the best way to confirm our materials are under active review, and on any additional steps that would help. Thank you. Reference details: Case ID: 102900026351 Appeal Ticket: APL444296

Hello, My app (Gezo Gündem, a Turkish news app) has been rejected twice under Guideline 4.2.2 (Minimum Functionality), both times with the same generic template: "the app only includes links, images, or content aggregated from the Internet with limited or no native functionality." For the second submission, I provided detailed App Review Notes listing 8 distinct native iOS features with step-by-step testing instructions for each: A native AI summary modal with native favoriting A native theming engine (5 modes) + dynamic "Club Mode" theming via native state management Native offline article storage using the device's file system (fully functional in airplane mode) A native Text-to-Speech engine reading article content aloud Native push notifications when followed authors publish new content A native source/favorites aggregation dashboard A native pinch-to-zoom newspaper cover gallery WebView is used only to render the body text of individual articles — nothing else in the app relies on it. Despite this, the second rejection used the exact same template language, with no reference to any of the listed features. I've since replied via Resolution Center asking the reviewer to re-test following the specific steps in the notes, but I'm unsure if this is the right channel to get a reviewer to actually engage with documented native functionality rather than reissue a template rejection. Has anyone successfully gotten a reviewer to revisit a 4.2.2 rejection by providing this level of detail? Is there a more effective way to ensure the review notes are actually read before a decision is made? Any guidance would be appreciated. Thanks.

Hello. I am currently working on a branded app for a company that is built off an already existing open source application. If I change the logo, name and theme of the app to fit the company branding, would it be accepted by the App Store, or would the app be rejected because the underlying App/Source Code is essentially the same?

Bonjour j'ai crée un ticket pour une question sur feedback il ya une semaine et n'ai tujours pas eu de reponse (numéro de ticket : 102916971507) App name: Vytal AI Bundle ID: com.ciborgu.vytalai App Store Connect App ID: 6767160542 Team ID: JZF7CR3W8Z

Rejected under Guideline 4.2 - a native crypto wallet + Web3 browser flagged as "just a web browser." Looking for guidance. I'd appreciate the community's and Apple engineers' read on a 4.2 (Minimum Functionality) rejection, because I believe the guideline was misapplied and I want to resolve it correctly. WHAT THE APP IS Everything Black is a native iOS app (SwiftUI, iOS 18+) built to platform Black-owned businesses, history, culture, and content, and to preserve it in one place. There is nothing else like it on the App Store. It combines a community hub, a Web3 layer, and an on-device crypto wallet. Native non-custodial wallet (GuapcoinX / GUAP token). This is core, and none of it is possible on the web. A 12-word recovery phrase is generated on the device with native BIP-39 / BIP-32 key derivation. The private key is stored in the iOS Keychain, so it never leaves the device or touches a server. Every transaction is gated by Face ID via the native LocalAuthentication framework. Transactions are signed on-device (secp256k1) and broadcast to the GuapcoinX network. Web3 and blockchain domains. The app registers and resolves on-chain domain names, .guap and .hbcu, and routes to them. These are real blockchain writes initiated and signed by the user. To my knowledge this is the only iOS browser that resolves these domains natively. Native AI assistant. A native SwiftUI chat that returns tailored Black-owned business recommendations from a ZIP code. Native directory and Discover. A native SwiftUI feed and search over a directory of Black-owned businesses, news, podcasts, wikis, resources, and a community board, preserving Black culture and content in a single app. A browser tab is included so users can open community and Web3 sites and reach their .guap and .hbcu domains. It is one tab among several, not the substance of the app. THE REJECTION Guideline 4.2, Design, Minimum Functionality. The app provides a limited user experience as it is not sufficiently different from a web browsing experience. Including features such as push notifications, Core Location, or sharing do not provide a robust enough experience to be appropriate for the App Store. (Screenshot of the rejection attached.) WHY I THINK 4.2 DOESN'T FIT The rejection says the experience is not sufficiently different from a web browsing experience. But the core of the app is a native crypto wallet doing on-device key generation, Keychain storage, biometric-gated signing, and on-chain transactions, capabilities a website physically cannot provide. The App Store hosts many approved apps that pair an in-app browser with a native wallet and an AI assistant, which is exactly the combination here. I suspect the native functionality was missed because the app opens on the Home and browser tab, so the reviewer may not have reached the Wallet and Assistant tabs. MY QUESTIONS First, for those who've cleared a 4.2 on an app with a genuine native wallet: did a Resolution Center reply work, or did you have to change the app or metadata? Second, is it worth changing the default launch tab to a native screen such as the Wallet, so the native functionality is the first thing a reviewer sees? Third, is there any guidance from Apple on how an in-app browser should be positioned so it isn't read as the whole app? Thanks in advance. G u i

Hello, My app has been in “Waiting for Review” status since May 28. App ID: 1471317275 The app was transferred to my developer account about two months ago. Since the transfer, previous reviews were completed without any issue, and I have not received any message in the Resolution Center or any indication that something is wrong with this submission. I am not sure if the app transfer could have affected the review queue, but the current submission has now been waiting for an unusually long time. Could someone from Apple please advise what I should do in this situation? Should I continue waiting, contact App Review Support directly, or resubmit the build? Thank you for your help.

Hello App Review Team, My app, SUB PREMIUM TV (Apple ID: 6769972609, Version 1.0), has been in “Waiting for Review” status for several days. I would like to confirm whether there is any issue with my submission or if any additional information is needed from me. Thank you for your time and assistance. Best regards, Babucarr Ngum

My app review has been stuck. The app includes IAP. When displaying purchases, it first needs to retrieve the price list. This price list is hosted on Apple's servers. Retrieving it is handled by the SDK. Possibly due to the sandbox environment, the price list is very difficult to obtain right when Apple's California office starts work. But at other times, it's very fast. Apple's reviewers have never been able to see the prices. I suggested they change their test time to noon or afternoon, but they still couldn't see the prices. This suggests that the network environment used by Apple's review team has poor connectivity to Apple's own sandbox servers. When I received the review start notification, I tested it myself, and it worked perfectly — the price list loaded quickly. I recorded a video and took screenshots to show the reviewers. But they are still testing within their own network environment, so they couldn't see the price list. I suggested they switch to an open network environment for testing, such as cellular mobile data or a coffee shop Wi-Fi. But that doesn't seem to have helped. They still say they cannot retrieve the prices. This has been going on for a week. They test once a day, and I resubmit once a day. I don't understand why they won't test just once in an open network environment — that would allow them to see the price list load quickly, and would also prove that Apple's SDK and sandbox are functional. If the app works fine in the user environment, then there is no problem. If there's an issue in their test environment, it's a network environment issue. Our code has no problem — I can see that it retrieves the price list and purchases work normally. Every day I can only resubmit without uploading a new version. But I can't keep this up forever. I think maybe a supervisor or someone in charge needs to look into this. Our app is com.ayi9.phone.

Hi everyone,  I'm a relatively new developer and I just received my first App Store rejection. I'm posting here because I'm genuinely stuck and hoping the community can help me figure out where to even begin.  The Problem:  My app was rejected under Guideline 5.6 - Developer Code of Conduct - Review Suspended. The full message is the standard one: the app doesn't meet the "required quality standard," it's "not eligible for resubmission," and I should "ensure every screen, interaction, and piece of content has been thoughtfully designed" before submitting a new app.  Here's why I'm confused:  The rejection came with ZERO attachments. No screenshots. No screen recordings. No crash logs. No specific mention of a buggy feature, a broken button, or an unfinished screen. It's just a blanket statement about "quality" and "polish."  in my case, there's absolutely nothing to go on.  What I've checked so far:  I've tested the app on multiple physical devices (iPhone 12, 14, 15) – no crashes. I've reviewed every screen for placeholder text, "Lorem Ipsum," or dummy images – none found. I've checked the In-App Purchase / subscription screen for proper legal disclaimers and auto-renewal text – all present. I've made sure there are no debug logs or test toggles left in the production build. Everything looks fine to me, which is why I'm so lost. Without specific feedback, I don't know if the issue is:  A UI inconsistency I'm blind to? A subtle crash that only happens on a device I don't own? An issue with the paywall flow that I've misunderstood? Something about the metadata, screenshots, or app description? My questions for the community:  Has anyone else received a Guideline 5.6 rejection with no attachments? Is this common, or does it suggest the reviewer flagged the app as "low-quality" purely based on first impressions (like the design feels outdated or the concept is too simple)? Since the message says replies and resubmissions of this binary won't be reviewed, and I can't get clarification from the reviewer, what's the safest way to proceed? Should I:  Create a completely new App ID and submit as a new app? Or can I submit a new version under the same App ID? (I've heard mixed answers on this.) More importantly – how do I figure out what to fix? Without a starting point, I'm worried I'll fix the wrong things and get rejected again, which I know can lead to account termination after repeated violations. Are there any "hidden" quality checks that reviewers apply that aren't obvious to developers? For example, does Apple penalize apps that:  Have a generic icon or unpolished splash screen? Take too long to load on first launch? Have unclear navigation or confusing user flow? Lack a proper onboarding/tutorial for first-time users?   Thanks in advance for any help you can offer. I really want to get this right and not waste my one or two remaining chances. my app id : 6764726742

Hi everyone, I'm hoping someone from Apple or a senior community member can help escalate my situation. About four weeks ago, I received a termination warning on my developer account related to an app called Checklist Buddy (originally named Cessna Checklist Buddy). I renamed it after realizing I didn't have formal written permission from Textron Aviation, even though I had verbal approval. I believe that name change — or possibly code similarity between apps — may have triggered a flag. I have three apps on the store: WIB 26, Checklist Buddy, and Pure International 2026. WIB 26 is live and functioning fine. Pure International 2026 is the critical one — it's an event app for a pageant happening next week and delegates are counting on it. I have submitted multiple appeals and tickets over the past four weeks with zero acknowledgment from Apple. Last week I called Apple Support and spoke with a representative. He pulled up my account and confirmed there were notes showing an appeal on file, but no reason whatsoever was documented for the termination warning — even he couldn't see why. He escalated my case to a senior advisor and told me I would hear back within 3 business days. It has now been 7 days with no contact. I understand Apple has a high volume of cases, but this is affecting my livelihood. I have a real event with real attendees next week who need this app, and I cannot distribute it or push updates because my account is in a restricted state pending this appeal. If any Apple staff reads this — my case has been escalated to the senior advisor team and is sitting in an email queue. I just need a resolution or at minimum a reason for the original warning so I can address it properly. Any advice or help from the community is also appreciated. Thank you.

Hello App Review team, I am an individual developer and I appear to be experiencing a systemic, account-level delay rather than a normal queue wait. My current app "Color Grading App - Gradee" (Apple ID 6778543702) has been in "Waiting for Review" since June 10 - about 10 days - and has not yet entered review. This is a recurring pattern on my account: previous apps also stayed in "Waiting for Review" for an unusually long time (weeks to months) before review even began, regardless of the app's content. Because every submission on this account is affected the same way, I am concerned my account may be under a review hold or flag. Could someone please: Confirm whether my Apple Developer account is under any review hold, enhanced review, or flag. Let me know if anything is required from my side to resolve it. I have open support cases (102914638162, 102918134058) but have not yet received a response. I am not trying to flood support - I just want to understand what is happening so I can fix it. There is also time sensitivity: a marketing video for this app has gone viral and many users are actively searching for it right now. Thank you very much for your help.

Hello, Our U.S.-registered company recently submitted a new mobile app for App Review on June 11. Since then, the app has only entered review once. We received a rejection, addressed the issue within a few hours, and resubmitted the app for review. Since June 16, the app has remained in “Waiting for Review” status with no further updates. We also submitted an expedited review request on June 18, but we have not received any email response, and the app status has not changed. We are becoming very concerned because this is a serious product for our company. We have signed agreements with business partners, which we provided during the review process, as well as important marketing commitments tied to the app launch. The delay is now putting our business agreements and launch schedule at risk, and our marketing partners have limited flexibility regarding timeline changes. We have provided everything requested for review, including business documentation, legal information, partner agreements, demo accounts, and clear review instructions in a structured format to make the review process as straightforward as possible. We would be very grateful for any advice on what else we can do in this situation, or whether there is any way to help ensure that the app is reviewed as soon as possible. Thank you in advance for your help.

The owner of the app has cancer & every moment is counting as the situation is getting worse by the hour. It may sound weird, but as you guys know, cancer patients have a lot of requests; he wants to see his app live. I sent the app for review 2 days ago, but it's still in "waiting for review". I will appreciate it if any Apple staff watch this post, will be grateful & begging to review this amazing app faster & make it live. please!

I submitted an update for my app 7 days ago and it's still sitting in "Waiting for review". This isn't a new app submission—it's an update containing important bug fixes that users are waiting for. I've already contacted Apple Review to ask about the situation and request assistance, but so far I haven't received any update/reply. What makes this even more frustrating is that I've submitted other apps after this one, and those apps were reviewed and approved first. I genuinely don't understand how the review queue works if later submissions can move ahead while an older submission remains untouched. The delay is causing real damage: Users are leaving negative reviews for bugs that have already been fixed in the pending update. Some subscribers have canceled because they assume the issues aren't being addressed. The app's rating and reputation are taking a hit while the fix is effectively locked behind the review process. I'm attaching the email I sent to Apple Review. Has anyone else experienced unusually long review times recently? Have you found any effective way to get visibility into what's causing the delay? I'd be interested to hear whether this is an isolated case or if other developers are seeing the same thing.

Hi everyone, Our app has been in “Waiting for Review” status for 7 days. There are no outstanding actions, messages, or compliance issues shown in App Store Connect. Has anyone experienced similar review delays recently? If so, how long did it take for the review to begin? App ID: 6759098797 Submission ID d6c075db-883c-44fe-8220-005de5a2ed1e Thanks in advance for any guidance.

Hi guys We have tried to push our app live for over a month now, and there is total radio-silence from apple. Trying to call the Danish/Irish number, no one picks up the phone - we have tried several times and it just keeps playing waiting tone for hours. We have tried writing, but nothing gets back. From may 12th, we got a response on may 28th to update a few things in the app. That was done and then resubmitted. Then again on June 3rd. But from june 3rd, radio silence until june 15th. And now, again radio silence from 15th. We have clients who are waiting for the app, and all of our income relys on this. But no response. I was expecting more from one of the worlds biggest companies.

Hi, Was there an issue or something with the recent App Review queue? Since our app has been in "Waiting for Review" status for about 1 week and got nothing from the review team. App ID: 6759098797 Submission ID: d6c075db-883c-44fe-8220-005de5a2ed1e I'm wondering if we could get any support or help here by posting the issue.

Stuck in "In Review" for 2+ weeks - tens of clients waiting, not sure what to do Hi everyone, Our app has been sitting "In Review" for more than two weeks now, with no update and no rejection — just silence. We've already shipped to TestFlight and everything works, so this is purely the App Store review stage holding us up. The hard part: we have tens of clients waiting on this launch, and every extra day is putting real pressure on us. We don't know whether we did something wrong, whether we're flagged for extra review, or whether this is just a long queue we have to wait out. we've actually been accepted to the expedited review but it didnt push anything forward. A few questions for anyone who's been through this: Is 2+ weeks in review without any response normal, or a sign something is stuck? Did Apple grant it? Is there a better channel — Developer Support phone/chat, escalation, anything — that got a human to actually look at the submission? We'd really appreciate hearing how others got unstuck. Trying to figure out the right next move instead of just waiting blindly. Thanks in advance.

Hello, my app id 6756081224 Waiting for Review 10 day ago Help me please

Hi everyone, I'm hoping someone from App Review (or anyone who's been through this) can help, because I'm a bit stuck. My app Mingle (Apple ID: 6770285096, Version 1.0.1) has been sitting in "Waiting for Review" for well over a week now. I first submitted at the start of June, and after it sat there for ~6 days with no movement at all, I figured something might be wrong, so I canceled and resubmitted. The new one has now been waiting since June 15 with the same silence: Submission ID: c919ad21-902a-4a3c-a6cc-a5fbd9f7e2b1 Every previous review of this app went through in under 48 hours, so this is really out of the ordinary. I've already opened a support request through Contact Us, but I haven't heard anything back yet. This is genuinely blocking me - I've been trying to get this release out since the beginning of the month and everything on my end is ready and waiting on the review. Is there anything I can do to move this along, or any reason a submission would get stuck like this? If anyone from App Review could take a look, or point me to the right channel, I'd really appreciate it.