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, I am seeking advice or assistance regarding a significant delay in the review process for my app, Preppy (App ID: 6443527187). The app has been on the App Store for over 4 years and has been featured as "App of the Day" on three separate occasions. We have always maintained a good standing, but we are currently facing an unprecedented bottleneck that is negatively impacting our users. The Timeline: Version 2.6: Approved successfully ~3 weeks ago. Version 2.6.1: Submitted shortly after to address a critical bug. It was rejected due to the screenshots (which were the same as in 2.6), but I changed them according to the feedback. It remained in review for another 7 days. Even after requesting an expedited review, there was no movement anymore. Action taken: I rejected the build and resubmitted with a new build and updated screenshots again, hoping it would help. It sat for another 5 days with no status change again. Phone Support: I spoke with support via phone and was advised to increment the build/version number and resubmit and was told the app is in the expedited queue, so it will be reviewed shortly, which did not happen. Version 2.7: Uploaded 4 days ago with a new version number, updated screenshots yet again, and an improved description. It has been stuck in "Waiting for Review" since then. I have sent multiple emails to the App Review team explaining that this update contains a critical bugfix. Because of this delay, we are now receiving a wave of negative 1-star reviews from users who are experiencing the bug that is already fixed in the pending build. I have had no response to my follow-up emails, and the "Contact Us" forms haven't resulted in any updates. Has anyone else experienced this recently with a long-standing app? Is there any other way to escalate this beyond the standard expedited review form (which has already been used)? Thank you for any help or guidance.

Hello Everyone, I have recently purchased an app and its source code and am currently reviewing its metadata and functionality to make sure my upcoming update complies with the App Store Review Guidelines. The app was previously removed from the App Store as it had some screenshots showing WhatsApp's name. My intention is to make any necessary changes before submitting the next version for review. I would like to understand whether it is permitted under the App Store Review Guidelines to use the term “Whats” or "WA" as an app title. For reference, I am attaching links to several apps currently available on the App Store that appear to use “Whats” in their title and also in their app name. I understand that the presence of similar apps does not necessarily mean the wording is permitted, which is why I am writing to request clarification before submitting my update. Example Popular Live Apps with the Same Name: https://apps.apple.com/mx/app/whats-web-watsapp-web/id6444021754 https://apps.apple.com/mx/app/whats-web-para-whatsapp/id6471455409 https://apps.apple.com/mx/app/whats-web-whatsweb-chat-app/id6464555232 https://apps.apple.com/mx/app/whats-web-dual-app-para-wa/id6720725024 https://apps.apple.com/mx/app/whats-web/id6444548565 https://apps.apple.com/mx/app/whats-web-dual-messenger/id6476896406 https://apps.apple.com/mx/app/whats-web-app-clonar/id1635526052 https://apps.apple.com/mx/app/whats-web-dual-app-messenger/id6738838803 https://apps.apple.com/mx/app/whatsweb-click-to-chat/id6479015034 And there are like 20 more of these with the same name. Please note that I checked these examples in the Mexico App Store. They may appear with different names in other storefronts. Please advise, Thank you for your guidance!

Hi, My app LiveShift passed review in its first two versions without this issue. After that, I added more native functionality, including a monthly calendar with shift templates, but now the app keeps getting rejected under Guideline 2.3.1(a) and 4.2. The rejection says the app has hidden features and feels similar to a web browsing experience. That’s confusing to me because the app is fully native, has no webview or embedded website, and all features are available through the main tabs: Home, Calendar, Shifts, and Settings. The app includes real-time shift tracking, Live Activities / Dynamic Island, shift history, overtime and extra pay rules, notifications, export, and now Calendar planning. Has anyone had this happen after adding more features? Would better Review Notes, a demo video, or an appeal be the best next step?

Hello everyone, my initial app release (Version 1.0) has been stuck in the 'Waiting for Review' status for 6 days now. It is a comprehensive app that includes localization for 14 different languages. I understand that initial submissions and extensive localizations can take longer to review, but 6 days seems unusually long. Is anyone else experiencing similar extended delays with App Review recently? Any insights would be appreciated. Thank you.

I've exhausted standard channels and we're at the point where this delay is creating real financial harm for our business and our customers. App ID: 6761686513 Our initial submission was reviewed within 2 hours and we received feedback. We addressed every item in the rejection, resubmitted, and the app has now been sitting in "Waiting for Review" for with no movement. We submitted an expedited review request, contacted Apple Developer Support by phone, and emailed. None of which have produced a clear answer or estimated timeline. Today, May 1st, was our planned hard launch. We have hundreds of paid subscribers: small business owners who specifically scheduled their first billing cycle to begin on launch day so they could use the platform's full feature set, including the iOS app, from day one. Our app supports their booking system, payment processing, client management, and day-to-day operations. Because the app didn't get approved in time: We had to issue full refunds to every subscriber charged today, since they're paying for a product they can't fully use. Our subscribers are now in limbo. They've already onboarded their clients onto our system and are running their businesses through it, but the iOS experience that was promised at launch isn't available. Each additional day of delay compounds this. Our small team is fielding messages from subscribers asking when the app will be live, and we don't have an answer to give them because we don't have one ourselves. I understand review times vary and the queue is real, and I'm not trying to jump the line unfairly. But the advised 24–48 hour window hasn't held this round. Our initial review came back the same calendar day we submitted, and we resubmitted within hours of receiving the feedback. We're now far past that original turnaround with no signal that anything is moving, and no response from expedited review or Developer Support to indicate where we stand. If anyone from Apple sees this and can take a look at App ID 6761686513. I'd be incredibly grateful. Happy to share any other detail that helps. We just want to get unstuck. Thank you.

Hello, I am seeking assistance with our submission that appears to be stuck in the "Waiting for Review" stage. While our previous updates were processed quickly, this version has seen no movement for a significant period across multiple attempts. App Details: App Name: Koda: Cozy Self-Care App ID: 6758280298 Version: 1.1.8 We have already tried reaching out through apple support and already requested an Expedited App Review but we're still stuck in 'Waiting for Review' status. We have contacted Developer/App Review Support as well, but received no response from them. Our Case ID is 102880034374. We are concerned there may be a technical issue or a status preventing the build from reaching a reviewer's queue. Could someone from the team please verify if this submission is active and correctly queued? This is a critical release for us, including our new "End of Month" feature and bug fixes/improvements. Despite multiple attempts we have been unable to resolve the issue. Thank you for your time and help.

Hello, I've been trying the last week trying to get my app approved for the App Store. It's my first app and I'm not really sure what's going on. My app is getting rejected due to "App Completeness". Here's the rejection message: App Review Guideline Issue This is an automated message. The review of this submission cannot proceed. See below for more information. The app crashed after the initial launch. Apps that crash negatively impact users. Test the app on supported devices to identify and resolve crashes and stability issues before resubmitting for review. Learn more about testing a release build. When we submitted the first time we got rejected because our Apple sign in did not auto fill the user's name and we didn't have the EULA Link in the description. So the app didn't crash here as a tester sent screenshots and was in our app. We resubmitted and then we started getting these crashes. I examined the code we added from the first revision and tested the start up and everything worked fine on ours and our 30+ beta testers end. The thing is we're not getting a crash log from Apple testers or Apple's automated tester (if automated testing exists?). We are creating a fitness app that implements HealthKit. We have the required HealthShare and HealthUpdate messages in the signing and capabilities of our target. I'm not sure this would be the issue since the app actually executed the first run though. I've researched and some articles did say long load times on bad internet could make iOS terminate an app. So we worked to get our initial load network calls down from 10 seconds to about 1-2 seconds. This did not work either. We are using SwiftData to cache exercises fetched from our backend locally but we haven't made any changes to the entity's. So I wouldn't expect bad data to cause a crash especially because we flush even if it were bad data anyway. I've ran with instruments to see if this was a memory issue: With an Authed User with data loaded it gets to about 33MiB With a fresh install memory usage is about 17MiB I did have a point of interest in my profile: api.revenuecat.com is not listed in your app’s NSPrivacyTrackingDomain key in any privacy manifest. It may be following users across multiple apps and websites to create a profile about users of apps that contact this domain. I don't use revenue cat for tracking for Ads so I probably shouldn't add it to the NSPrivacyTrackingDomain right? I'm really lost here any advice would be much appreciated. I guess my questions are if Apple has an automating testing environment how can I closely match that for testing on my end? If this is an actual tester why am I not getting a crash log or steps to repeat this issue? Has anyone else experienced the pain I'm currently suffering?

Our app update has been stuck in “Waiting for Review” for more than 8 days, and it appears the submission may have been overlooked or affected by a system issue on Apple's system. App ID: 1600450223 Bundle ID: com.asbing.woomanager Version: 5.3.1 What we’ve already tried: Requested an Expedited App Review Contacted Developer/App Review Support, but received no response (Case ID: 102878632497) Cancelled and resubmitted the update, but it remains in “Waiting for Review” for several days Could you please confirm whether this update is still in the review queue or if any issues are blocking the review? This is a critical release for us, and despite multiple attempts, we have been unable to resolve the issue.

Hello App Review Team, I’m reaching out regarding my first app release, Smala. App ID: 6762228514 Bundle ID: SmalaApp.Smala The app has now remained in Waiting for Review status for 8 days. I also submitted an expedited review request, which was approved, but the status has still not changed. This delay is creating significant launch issues for our team, as this release is time-sensitive. We would sincerely appreciate any assistance or status update when possible. Thank you very much for your time.

Hi, I had developed a app with IAP that works perfectly on my own device and simulators. But somehow Apple rejected it, stating it as "App loaded non-stop when we tapped on the upgrade to pro button" as of Guideline 2.1 - Performance - App Completeness. This really confused me. As i did some research, I found out that this was (hopefully) not my problem, but Apple's testing environment, since there are many similar posts. If anyone could explain what to do, that would be a great help. Thanks!

Hello Apple Developer Community, We are very excited to release our first apps on the App Store. I wanted to kindly ask for guidance because our first submissions appear to be taking longer than expected, and we want to make sure there is nothing missing or blocking the review process from our side. Our first app has been waiting for more than 15 days in total. App ID: 6761379839 Latest Submission ID: 8e767ece-a348-469a-9230-7e695e84ca44 After we first submitted the app, it entered review on the first day. App Review then requested a screen recording / walkthrough video. We prepared and submitted the requested screen recording immediately. After that, the submission did not appear to move forward for an extended period. While waiting, we continued development and completed a newer version of the app. Since the older submission had not progressed, we removed the previous build and submitted the newer version with an updated screen recording. One thing we noticed is that the subscription and in-app purchase products for this app appear to be “In Review.” We are not sure if this is expected behavior because the app version itself still appears to be waiting, or if there may be some kind of dependency or review state issue causing the submission to remain stuck. We also contacted Apple Developer Support regarding this situation. Case ID: 102882849875 We have another app on the same account that is also waiting for review. App ID: 6762281533 Submission ID: 0e4b607e-9e28-4d13-9c2a-98afe8c2e9aa This second app has been waiting for around 3 days. Could someone please advise or help us. Thank you very much.

Hi everyone, I’m writing this to share (and vent about) a disastrous experience I’m having with my first-time app submission. I’ve already missed my scheduled launch date because the review process has been stuck in a loop for over a week. I wanted to see if anyone else is facing this level of inefficiency. There are three main points that have made this process incredibly frustrating: • 1. Vague Copyright Flags: I initially received generic messages regarding copyright issues with zero context. I practically had to beg the reviewers to tell me exactly what the problem was. It’s impossible to "fix" an issue when the feedback is a riddle. • 2. Non-existent Communication: Every single response takes more than 48 hours. Even worse, many of my clarifying questions in the Resolution Center are simply ignored. I requested an Expedited Review to get things back on track, but it took another 48 hours just to get a response that wasn't even a resolution. • 3. Unwillingness to Test Basic Functionality: The latest hurdle is the most baffling. The app uses a simple QR Code system for peer-to-peer interaction. The reviewer claimed they couldn't test it and asked for a video of the feature in action. It feels like the tester is simply unwilling to use two devices to verify a core feature, choosing instead to stall the process further. It’s disheartening to see this lack of support for a first-time submission. We put months of work into development, only to be met with "minimal effort" testing and a wall of silence. App Details: • App ID: 6762914422 • Status: In Review (1 Week+) • Latest roadblock: Request for video of a 2-device QR scan. Has anyone else dealt with this specific "request a video" tactic for simple hardware features lately? Any advice on how to escalate this beyond the standard Resolution Center?

Hi everyone, I recently submitted my app for review and it has been in the “In Review” status for more than 24 hours now. From my past experience, reviews were usually much faster, so I’m starting to wonder if this is still within the normal timeframe. There haven’t been any rejection messages or requests for additional information so far — it’s just been sitting in review. Is this something you’ve experienced recently? Are review times currently longer than usual? Any insights or shared experiences would be really helpful. Thanks in advance!

We are developing a non-custodial cryptocurrency wallet app with the following characteristics: Architecture: Users hold their own private keys at all times (we never custody any assets). The app includes identity credential verification: KYC-verified identity data (Verifiable Credentials / DID-based) is exchanged between the payer's iPhone and a counterparty device for identity verification purposes. NFCTagReaderSession is used only to exchange identity credential data via our proprietary, non-payment ISO 7816 AID with the counterparty device. Cryptocurrency transactions are submitted entirely over the internet (blockchain RPC), completely independent of the NFC session. NFC is NOT used to: Transmit cryptocurrency or payment instructions. Interact with any EMV payment AID or Secure Element. Replace or emulate Apple Pay or any payment card. Jurisdiction & licensing context: The app is being developed by a Japanese company for initial launch in Japan. While this question is posted from an individual Developer account for inquiry purposes, the app itself will be submitted under an appropriate Organization Developer account of the operating company, in compliance with Guideline 3.1.5(a)(ii). We are working with Japanese legal counsel to obtain any applicable Japanese financial-services license (e.g., 電子決済手段・暗号資産サービス仲介業 / Electronic Payment Instruments and Crypto-Asset Service Intermediary Business under the 2023-amended 資金決済法 / Payment Services Act) prior to App Store submission, and a written legal opinion will accompany the submission. We are not seeking to qualify as a 暗号資産交換業 (crypto-asset exchange) or 資金移動業 (funds transfer service operator), as our non-custodial design is intended to fall outside those categories under Japanese law. Question: Under Guideline 3.1.5, does a non-custodial wallet that uses NFCTagReaderSession solely for identity credential data exchange (not for transmitting cryptocurrency or payment instructions over NFC) fall under the "Wallets" sub-category — requiring an Organization Developer account only — or does NFC involvement for identity verification shift it toward a sub-category requiring additional licensing, entitlements, or financial institution credentials?

Hello App Review Team, Kindly assist with a response to the message sent on app submission. For the review team drop a message on the message trail and we responded but no feedback has been shared. Our submission ID - 8b32ad4d-9912-4f25-837c-13b15323a258. Thank you very much for your time and assistance.

Hi, just wanted to follow up on my application that has been stuck in the "In Review" state for 5 days now. Thank you!

Hello App review Team, Our app have been stuck in awaiting review since April 20th 2026 and no feedback. The submission ID - 8b32ad4d-9912-4f25-837c-13b15323a258, Is there a reason for this long waiting.When can we expect the review to proceed? Thank you very much for your time and assistance.

Hello, I’m reaching out regarding a critical delay in the app review process for App ID: 6743190232.😭😭😭😭 Despite submitting for review several days ago, the status remains unchanged. We have upcoming time-sensitive events tied to this release, and the current delay is causing significant disruption to our roadmap. I have already initiated a support ticket (Case No. 102878799248) and requested an expedite, but I have not received any feedback so far. I would deeply appreciate any assistance in moving this forward or providing a status update so we can plan accordingly.

Hello, this is my app (App ID: 6761799912, Team ID: D5QC3QDLAY). Since submitting for review, the status has been pending for several days. I requested an expedite, but I have received no feedback. I contacted Support (Case No.: 102870515950) but have not yet received a response, and I am unable to proceed with important events. I would appreciate it if you could review this as soon as possible.

Hello, My first app, Dodge? (Apple ID: 6757125102), has been in review for over 53 days. This app was already live on the App Store, and this submission only includes UI improvements. Additionally, my second app, Widgety – Desktop Widgets (Apple ID: 6761670888), has been in review for 13 days. This is my first time submitting this app for review. I have already contacted Apple support regarding this issue, but have not received a resolution so far, which is why I am posting here in the forums. Both apps have been pending for an unusually long time. Since Dodge? is just a UI update and Widgety is a standard first-time submission, I would expect a much faster review process. Could you please check the status of these submissions and let me know if any additional information or action is required from my side? Has anyone experienced similar delays or knows what might be causing this? Thank you.