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.

HI, Following up on this thread, the situation has escalated significantly. After my app was stuck in review for nearly 2 months, I received a Pending Termination Notice on my entire developer account citing section 3.2(f), concept or feature switch schemes. All of my apps have been removed from the App Store, including apps that were already live and had not been submitted or modified in any way. The notice states that automation may have been used as part of the review process, and I received the exact same notice for every single app on my account, which suggests this was a blanket automated action rather than a specific finding per app. I have already submitted individual app appeals and a full account reinstatement request through the official channels. I am an independent developer based in France under the Small Business Program and this account represents years of work. I would kindly ask if this can be looked into and escalated to the appropriate team. I am happy to provide any information needed. THANK YOU

I have a question. After how many days in the “Waiting for Review” status should I conclude that there is an issue with my app review request and contact the support team?

Hello Apple Review Team and Community, I hope this message finds you well. I am reaching out regarding our app (Apple ID: 6743547441), which has been stuck in the "Pending Review" status since May 5th — now more than 8 days with no updates or feedback. I fully understand that review times can vary and that the queue may currently be experiencing higher-than-usual volume, and I truly appreciate the hard work the review team puts in. I am not looking to escalate — I simply want to make sure everything is in order on our end. Could anyone kindly help confirm whether: There is a specific issue or blocker with this submission that requires our attention Any additional information, documentation, or clarification is needed from our side Or whether the app is simply still awaiting reviewer assignment We are happy to provide any further details or make any necessary adjustments as quickly as possible. Thank you so much for your time and support. We look forward to hearing from you. Best regards

Hi, I have resolved the issues reported regarding the guidelines 2.3.10 and my app is stick waiting for review for days. re: https://developer.apple.com/forums/thread/826280

Hello, I would like to check the status of my app, as it has been stuck in "waiting for review" for almost a month (ID: 6746933136). Thank you

Hello, My app (Apple ID: 6766249889) has been in "Waiting for Review" status long time after resubmission and answer/replay to Apple Review Team. The account is in good standing, all agreements and banking information are active. Could someone from the App Review team please check whether there is any issue with this submission, or confirm that it is simply pending reviewer assignment? Thank you.

Hello, My app (Apple ID: 6768121501) has been in "Waiting for Review" status long time with no progress and no messages in the Resolution Center. Could someone from the App Review team please check whether there is any issue with this submission, or confirm that it is simply pending reviewer assignment? Thank you.

Hello, Following a rejection, I resubmitted my application for review on May 8, 2026, and requested an expedited review. The status changed to 'In Review' but there have been no updates since then (it has now been 5 days). I have already reached out to developer support but have not yet received a reply. Usually, approval takes only 1 or 2 days, so this delay is unexpected. Has anyone else experienced a similar situation recently? Thank you for your time.

Hello, I submitted an update for my app for review on April 27th. Since then, the app has remained in the “Waiting for Review” status. I contacted support by email after one week and again after two weeks, but both of my messages were left unanswered. Please provide me with an overview of what is going on with my app submission for review. Thank you.

Hello Apple Developer Support, My app has been stuck in “Waiting for Review” since February 7, and I have submitted multiple inquiries without receiving any response. This delay has now become extremely concerning. Missing a planned launch due to an indefinite review timeline is very difficult for independent developers. If there is an issue with the submission, I would appreciate clear communication. If there are review delays, transparency would help us plan accordingly. I respect the review process, but the lack of updates after this amount of time is frustrating. I would sincerely appreciate clarification on the status. I kindly ask for a specific and personalized response regarding my case, as my previous inquiries received only general or automated replies without addressing the actual issue. Thank you.

Hello everyone, I'm encountering a blocking issue with my first-time Non-Consumable In-App Purchase​ after a rejection. Here is the exact workflow: Initial State: My App and IAP (com.marryflow.app.premium.lifetime) were linked and submitted together for the first time. Rejection: The IAP was rejected, and the App was consequently rejected as well (metadata rejection). Resubmission: I fixed the IAP issues and submitted it again. Its status is now "In Review". The Block: When I uploaded a new binary and went to the App Version page (under the "In-App Purchases" or "Subscriptions" section), the IAP that is "In Review" does not appear in the list. The interface only seems to allow selecting IAPs with "Ready to Submit" status. My Questions: Is this an expected system restriction? Meaning, once a first-time IAP enters a standalone review cycle, it cannot be manually re-attached to an App version? If so, is the correct resolution to ask the App Review team to reset the IAP's status back to "Ready to Submit"​ so that I can select it on the App Version page and submit them together? Currently, my App is submitted (without the IAP attached) and the IAP is stuck in "In Review". Any guidance on the proper workflow would be greatly appreciated. Thank you!

So i submitted my app what seems like a dozen times now and they keep rejecting it due to Guidelines 5.1.1(i) - Privacy - Data Collection and 5.1.2(i) - Legal - Privacy - Data. The full section is: Issue Description The app appears to share the user’s personal data with a third-party AI service but the app does not clearly explain what data is sent, identify who the data is sent to, and ask the user’s permission before sharing the data. Apps may only use, transmit, or share personal data after they meet all of the following requirements: - Disclose what data will be sent - Specify who the data is sent to - Obtain the user’s permission before sending data - Identify in the privacy policy what data the app collects, how it collects that data, all uses of that data, and confirm any third party the app shares data with provides the same or equal protection Next Steps If the app sends user data to a third-party AI service, revise the app to explain what data is sent, identify who the data is sent to, and ask the user’s permission before sharing personal data with a third-party AI service. If it does not already, the app’s privacy policy must also identify what data the app collects, how it collects that data, and all uses of that data, including if it is shared with a third-party AI service. Note that only including this information in the app's Terms of Service or Privacy Policy is not sufficient. If the app does not send user data to a third-party AI service or does not include a third-party AI service, reply to this rejection to confirm and add this information to the App Review Information section of App Store Connect. So i did this. My app uses 3rd party Ai services for facial scans and Ai morph features. Ive explained what data is used, what data i sent, etc. This is in my Privacy Policy and ive aded a section in both pages for Scans and Ai Morph since they are 2 seperate operations, but there a notification that pops up when the user first uses the feature and on the same screen theres a text that says 'By using Facial Scanning you agree to our Privacy Policy and Terms" and the same for Ai Morph except it says Ai Morph Feature and not face scan.. And yet Apple keeps rejecting it. So what else do they require me to do?

Currently our app Juris: Learn the Law has consumable IAPs available publicly. We've recently added a subscription to a new update, but since we already added consumable IAPs, we can only submit new IAP on their own and cannot attach it to a new binary. The issue is that when we submit the subscription for review, it gets rejected and the reviewers respond that the subscription needs to be included with a new binary, even though we can't attached it to a new binary. We submitted a new binary at the same time we submitted a new subscription, but the new binary would be approved and the subscription would be rejected. The update with the subscription is available, but the subscription isn't, meaning users cannot use the new features which require the subscription.

Hey everyone, hoping someone here has seen this one because Apple support has basically gone silent on me at this point. Quick rundown of the situation: I submitted my app for review for the first time about 2 weeks ago, with my in app subscriptions attached to that first binary. That worked exactly like it's supposed to, subs and binary went into review together. The binary got rejected and the subs got rejected with it. Since then, every single time I create a new app version, the option to submit my subscriptions alongside it just isn't there. There's no "attach subscriptions" prompt anywhere in the new version's submission flow. So the only way I can actually submit the subs is on their own, straight from the Subscriptions page. And every time I do that, they come back rejected for one reason only, that they need to be submitted with a new app version. Which I literally cannot do, because that UI option doesn't appear in my ASC anymore. It worked the first time, and ever since that very first rejection it's just vanished from my account. What I've already tried: Multiple new builds over the past 2 weeks, each one addressing every bit of review feedback Bumping the version number a full major release (1.x to 2.0) incase ASC was caching something Leaving detailed review notes asking them to please review the subs alongside the current binary even though they aren't formally tied to it Including screen recordings in App Review Notes showing the option just isn't there on my end Submitting through the developer contact form, multiple times. Replying directly in Resolution Center on the rejection itself The usual stuff, refresh, clear cache, different browsers, Safari and Chrome. Same result everytime Honestly I'm fairly demoralised at this point. The hard part is that this is me costing real money for every day it drags on, users genuinely cannot upgrade to a paid plan because the subs aren't live, and as a 18 year old solo dev this aint easy. My actual question is, has anyone here run into this specific thing where the "attach subscriptions to a new version" option just disappears from ASC after the first rejection? Is there a known workaround, or a particular contact form topic that actually gets a human response within a reasonable timeframe? With all this being said I could be a complete idiot and theres something im missing and thats why its not working. If thats the case please just tell me im being stupid and that im missing something because i deserve it lowkey... I've even started thinking about deleting the subs and recreating them from scratch as a complete last resort, but that feels nuclear and I'd rather try anything else first. All help would be greatly appreciated thanks everyone 😄

Hi everyone, I’d appreciate guidance on a 2.5.2 rejection. My app was rejected with this message: “During review, the app installed or launched executable code. Specifically, the app allows users to install apps created by other users.” What my app actually does: Users create/share tool templates (not binaries/plugins). A template contains only: form configuration (text fields, dropdowns, checkboxes, sliders, etc.) At runtime, placeholders like #TextField are replaced with user input, then the final prompt is sent to a server for AI response. *The iOS app does not download/install/execute native code, scripts, frameworks, or dynamic modules on-device. I suspect review interpreted the word “install” in my UI as real app/code installation anyone knows what can i do to fix this problem. thank you,

Hello, I am seeking guidance or an internal escalation regarding our app (App ID: 6480077134), which has been in the "In Review" status for over 30 days. Despite several attempts to resolve this through standard channels, we have not received a status update or a response to our latest correspondence. We have already: Requested a phone callback (Result: "We'll email the review team," but no follow-up). Submitted a formal Expedited Review request 14 days ago with no response. Attempted to contact the review team via email over a week ago (exceeding the 72hr response window). Our last correspondence addressed feedback regarding Guidelines 2.3.2 and 2.1(a) as follows: Guideline 2.3.2 – Promotional Images & Price References Removed all promotional images from IAP products. Removed price references from display names (e.g., changed "90 Day Free Trial" to "90 Day Trial"). Guideline 2.1(a) – App Completeness (Conversations) Provided clear reproduction steps for the "Conversations" feature, clarifying its contextual design. This version is an update to an existing app already on the Store, and this delay is now significantly impacting our business. We are concerned the submission may be stuck in a technical queue or an un-notified account hold. Any assistance or visibility from Apple staff or the community would be greatly appreciated.

My app has been pending review in App Store Connect since April 13, 2026. I have already contacted Apple Support ticket 102873493392, but I’m still stuck in the same situation with no clear explanation or timeline. This delay is becoming really frustrating, especially after following the required process and receiving no meaningful update. I would appreciate it if the App Review team could look into this case and let me know what is blocking the review.

Hello, I am experiencing a persistent issue with auto-renewable subscriptions during App Review. Despite verifying all configurations, the subscription purchase flow fails and the app continues to be rejected under Guideline 2.1(b). Environment App built with FlutterFlow (no Xcode access, Windows-only development environment) purchases_flutter SDK v9.9.5 (RevenueCat) iOS deployment target: iOS 13+ Review device reported by Apple: iPhone 17 Pro Max, iOS 26.4.2 Configuration verified App Store Connect: Subscription group plateup_pro created and configured Products plateup_pro:monthly (1 month) and plateup_pro:yearly (1 year) created with all required fields Both products status: Waiting for Review Paid Apps Agreement: Active as of May 8, 2026 All tax forms active: Brazil Tax Form, W-8BEN-E, W-8BEN Banking account: Active RevenueCat dashboard: In-App Purchase Key configured and validated: Valid credentials confirmed App Store Connect API Key configured and validated: Valid credentials confirmed Apple Server to Server Notifications: configured correctly Entitlements, Offerings and Packages: correctly configured and linked to both products Purchase tracking: All purchases in RevenueCat (default) App (FlutterFlow): RevenueCat Purchase action configured for both $rc_monthly and $rc_annual packages Action output variables isMonthly and isYearly checked after purchase Both FALSE paths now display an informational alert: "Purchase unavailable. Please try again later." Paywall screen includes subscription title, duration, price, auto-renewal disclosure, EULA and Privacy Policy links, and Restore Purchases button The problem When the reviewer taps "Start 7-Day Free Trial", the RevenueCat Purchase action returns false for both isYearly and isMonthly, causing the informational alert to appear instead of completing the purchase. The reviewer sees this as a bug. Our diagnosis suggests this may be caused by one or more of the following: Subscription products stuck in "Waiting for Review" status — StoreKit may not return products that have not yet been approved, even in the sandbox environment. This appears to be the circular dependency described in this forum thread: https://developer.apple.com/forums/thread/818349 First-time subscription submission flow — The App Store Connect UI shows the message: "Your first subscription must be submitted with a new app version. Create your subscription, then select it from the app's In-App Purchases and Subscriptions section on the version page before submitting the version to App Review." We have attempted to add the subscriptions to the version page before submitting, but the option to select them was not consistently available. Possible SDK compatibility issue with iOS 26 — The purchases_flutter SDK version is managed by the FlutterFlow platform, and we cannot rule out a compatibility issue between the SDK and StoreKit on iOS 26.4.2. Sandbox testing limitation We are unable to reproduce or verify the issue locally because: The app is developed entirely on Windows using FlutterFlow We have no access to Xcode or macOS Enabling Developer Mode on the iOS test device requires Xcode, which we do not have Without Developer Mode, the Sandbox Account option does not appear in iOS Settings → App Store Our only available testing method is TestFlight, which does not support sandbox purchases without Developer Mode enabled This means we cannot confirm whether the purchase flow works before submitting to App Review, creating a dependency on the reviewer's sandbox environment. Questions Can StoreKit return subscription products in the reviewer's sandbox environment while those products are still in "Waiting for Review" status? Or must the products be approved first? Is there a way to correctly attach auto-renewable subscriptions to the app version submission from App Store Connect, given that we do not have access to Xcode or the App Store Connect API? Is there a known compatibility issue between purchases_flutter v9.9.5 (RevenueCat) and StoreKit on iOS 26.4.2 that could cause the purchase action to return false? Is there any alternative way to test sandbox purchases on iOS without enabling Developer Mode — for example, directly through TestFlight? Any guidance would be greatly appreciated. We have now gone through multiple review cycles with the same result and have exhausted all configuration options we can verify from our environment. Thank you.

Dear Apple Team, My app was rejected during App Store review on the basis that it must provide the same functionality as the web version. I respectfully asked the reviewer to clarify where this requirement is stated, as I could not find it in the App Store Review Guidelines. However, my question was not addressed, and the app remains in Rejected status. Could you please advise on the best next steps and the expected timeline for resolution? Thank you.

Hello, My app (Apple ID: 6760485927) has been in "Waiting for Review" status since May 7, 2026 — now over 5 days with no progress and no messages in the Resolution Center. The account is in good standing, all agreements and banking information are active, and no action appears to be required from my side. Could someone from the App Review team please check whether there is any issue with this submission, or confirm that it is simply pending reviewer assignment? Thank you.