App Review

RSS for tag

Understand the technical and content review process for submitting apps to the App Store.

App Review Documentation

Posts under App Review subtopic

Post

Replies

Boosts

Views

Activity

Preventing Copycat and Impersonation Rejections
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.
0
0
2.7k
Nov ’25
Tips from App Review
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.
0
0
3.7k
Dec ’25
Support your app on compatible devices
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.
0
0
464
5d
App stuck in "Waiting for Review" for 5+ days - Version 1.4
Hi everyone, I submitted a new version (1.4) of my app,last Wednesday at 9:02 AM. It has been in the "Waiting for Review" status for over 5 days now. My previous updates were usually processed within 24-48 hours, so I’m concerned if there might be an issue with this specific build or if there's a general delay in the review queue. Has anyone else experienced similar delays recently? Should I continue to wait, or is it time to contact the App Review team directly?
1
0
18
35m
Unusually long “Waiting for review” status, anyone experiencing the same?
Hello everyone, I’m currently experiencing significantly longer than usual review times and wanted to check if others are seeing similar delays recently. Here’s the timeline of my submissions so far: [Feb 5] Initial submission (Submit #1) [Feb 10] Sent expedited review request #1 [Feb 11] Canceled and resubmitted (Submit #2) [Feb 21] Canceled again → Uploaded new build → Resubmitted (Submit #3) [Feb 24] Sent expedited review request #2 My apple ID: 6757330278 The app has remained in “Waiting for Review” for an unusually long period across multiple submissions. Even after submitting two expedite requests, there hasn’t been any updates or response yet. What’s confusing is that I see other apps getting approved during the same timeframe, so I’m unsure whether this is: A broader review backlog A regional queue issue Or something specific to my account/app I’m just hoping to understand whether this is a widespread situation at the moment. If anyone has experienced similar delays recently, I’d really appreciate hearing about your timeline or any insights you may have. Thanks in advance, and good luck to everyone currently in review 🙏
1
1
39
37m
App Stuck in “Waiting for Review” for Over 2 Weeks (Since Feb 20)
Hello everyone, I am an iOS developer based in South Korea, and I’m currently experiencing an unusual App Store review delay that I have not been able to resolve through the normal support channels. My app has been stuck in “Waiting for Review” for more than two weeks, and there has been no progress at all during this time. It has not moved to “In Review”, and I have not received any rejection message or request for additional information from the App Review team. App Information Platform: iOS App Name: WOOTA Apple ID: 6759412826 Status: Waiting for Review Submission Date: February 20, 2026 Developer Account Region: South Korea What I Have Already Tried: I have already attempted the following steps: Submitted an inquiry via App Store Connect → Contact Us → App Review Received a response from Developer Support saying they understand my concern and that they contacted the review team However, since then there have been no updates at all. The app status remains “Waiting for Review”, and there are no messages in the Resolution Center. Questions I would appreciate any insight into the following: Is it normal for an app to remain in “Waiting for Review” for more than two weeks without any status change? Are there any recent delays in the App Review queue that could cause this kind of situation? Is there any other support channel I should try in order to get more information (for example phone support or another ticket)? Is it possible that some hidden issue with my account or metadata could cause the submission to remain stuck in “Waiting for Review”? What I Verified I double-checked the following: All required metadata fields are completed Screenshots and app information are properly filled The status shows “Waiting for Review”, not Metadata Rejected or Missing Information There are no messages in the Resolution Center Previous versions of the app were approved without issues Concern I am worried that the submission might be stuck somewhere in the review queue or blocked for an unknown reason. This update contains important improvements and fixes for existing users, so the long delay is quite concerning. If anyone has experienced a similar situation recently, I would really appreciate your advice. If any Apple staff member happens to see this post, I would be extremely grateful if you could help check whether there is any issue with this submission. Thank you very much for your time and assistance. Best regards, Lee Yuchang
1
0
34
38m
Mac App Review Sudden Delays?
We are an App Developer for past 16 years so have seen a lot happen with App Review over the years (even back when 2 month review times were the norm). However, we have all come to expect app review to take only 48 hours typically. We submitted several macOS Tahoe updates in Feb all approved within 24 to 48 hours, but 2 updates submitted on 25th Feb are stuck in 'waiting for review'. Very strange indeed and checking this forum, it seems many other devs are having the same issue, but from way earlier than us. Is this a known issue currently? I suspect their are different app review queues by region and maybe even app category and popularity of the app, but even accounting for all that, this is unusual. There seems to be no logic to which apps are approved same day vs those kept stuck in 'waiting for review'.
4
1
84
39m
Apps stuck on 'Waiting for Review' for over 14 days
Hello, I am experiencing the same severe delays as many other developers on the forum recently. I have multiple apps ( 6759218500 and 6758253704)that have been completely stuck in the "Waiting for Review" status, with one sitting there since mid-February. I have already tried reaching out via the "Contact Us" form multiple times, but my open support case (Case ID: 102828235824) has received no follow-up or resolution. Could someone from the app review team please look into this, any assistance would be greatly appreciated, as the standard support channels seem to be unresponsive. Thank you.
1
0
33
40m
Rejected for "Guideline 4.2 - Design - Minimum Functionality"
Of all the reasons I thought I might be rejected, I never thought this might be a possibility! "The usefulness of the app is limited by the minimal functionality it currently provides. " My app lets you track where you are in TV shows - you can add a show, tag shows (which appear as tabs), expand a show's seasons, mark an episode as watched, tap an episode to view its summary, and (if you have It installed) open the episode in Callsheet. You can also get a notification when a new season of a show drops. **Does anyone have experience with dealing with this kind of rejection? ** I'm wondering if they are dealing with an onslaught of "vibe coded" apps and are being more liberal with this rejection (this is not vibe coded!). The whole point of this app is that I didn't want a cluttered app with recommendations and other nonsense - I specifically wanted a simple, clean UI. https://tvnext.app Thanks, Damian App Id: 6757971087
2
0
58
40m
App review process takes long time
Hello iOS Developer Community, I submitted my app for review on February 19, 2026, and as of today (March 3, 2026), its status in App Store Connect still shows “Waiting for Review.” I contacted Apple Developer Support regarding this delay and received the following automated response: “Thanks for submitting your support request. We’ve received your support request and will get back to you as soon as possible. Your case ID is 102831222355.” It has now been more than ten days without any further communication or status update. Could anyone advise on the appropriate next steps in this situation?
2
1
71
40m
stuck in “Waiting for Review” since February 7
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. Apple ID: 6758804549 Thank you.
5
2
219
41m
stuck in “Waiting for Review” since February 9
Hello Apple Developer Support, My app has been stuck in “Waiting for Review” since February 9. I have submitted multiple inquiries without receiving any response. This delay has now become extremely concerning. 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. Apple ID: 6755156178 Thank you.
1
0
28
42m
Multiple iOS app updates stuck in “Waiting for Review” for 4–5 weeks
Hello, I have multiple iOS app updates (for already live apps) that have remained in “Waiting for Review” status since early February (approximately 4–5 weeks). These are standard updates (minor improvements / maintenance). All builds are properly attached, agreements are active, and there are no compliance or metadata warnings in App Store Connect. The apps were moved to “Waiting for Review” on February 6–11 and have not progressed to “In Review” since. Has anyone else experienced unusually long review times for updates recently? Could this indicate a queue issue at the account level? I have already contacted App Review Support and one of the submissions was marked for expedited review approximately one week ago, but the status remains unchanged in “Waiting for Review.” Thank you in advance.
2
1
45
43m
Urgent Follow-up on Pending Review – 4 Apps Affected
Dear App Review Team, I hope you are well. I am writing to respectfully follow up on my recent submission (Dev ID: 1770951123), which has now been in “Waiting for Review” status for approximately 12+ days. Currently, four of my applications are in a similar state, including one update for an app that was previously approved without issue. Given my past experience, reviews have generally been completed within a reasonable timeframe. While I fully understand that review times may vary depending on workload, the extended duration in this case has raised some concern. I previously submitted an expedited review request and opened a support case (Case ID: 102832785901). However, I have not yet received any response regarding the status of the review or the case. To better understand the situation, I would sincerely appreciate clarification on the following points: Whether there are any issues or flags currently preventing the review process from proceeding Whether any additional information or documentation is required from my side Or whether the submission is simply pending assignment to a reviewer I completely understand that the App Review team may be experiencing a high volume of submissions. Nevertheless, given the duration and the number of affected apps, I would be very grateful if someone could kindly review my case and advise on the current status. Thank you very much for your time and assistance. I look forward to your response. Kind regards, Lovesoft
1
0
30
44m
App stuck in “Waiting for Review” for 3+ weeks (Case ID: 20000107493507)
Hi everyone, My iOS app “TaskCal: Task Manager” (version 1.2.8) has been stuck in “Waiting for Review” for more than 3 weeks, and I’m not sure what else I can do at this point. Here are the key dates (GMT+8): Jan 30, 2026 – Version 1.2.3 was approved and marked “Ready for Distribution”. Jan 31 – Feb 8, 2026 – I submitted version 1.2.8 multiple times. Several submissions were later marked as “Removed” in App Store Connect. Feb 9, 2026, 12:39 AM – I submitted version 1.2.8 again. This submission has been in “Waiting for Review” ever since. Today is Mar 3, 2026 (Taipei time) – The status is still “Waiting for Review” with no change. Because of this, I contacted Apple Developer Support multiple times through Contact Support. I only received one reply, on Feb 21, 2026, which said: Hello Alan, Thank you for reaching out to Developer Support about your app, “TaskCal: Task Manager.” I understand that you’re concerned. After reviewing your app’s submission history, I can confirm that your apps is still in the “Waiting for Review” status as of February 8th 2026. To address your concern about the duration of your of the review, I’ve contacted the review team to bring this to their attention. At this time, there’s no further action required from your end. If the review team needs any additional information to complete the review, they’ll reach out to you directly. We appreciate your patience during this process. Your case number is 20000107493507. Stephanie Developer Support Since then, there has been no visible progress and no follow‑up messages. The App Review page still shows: Version: iOS 1.2.8 Status: Waiting for Review Case ID: 20000107493507 I completely understand that review times can vary, but: My previous version (1.2.3) was reviewed and approved normally. This is a relatively small productivity app with no major policy changes. It’s been over 3 weeks in “Waiting for Review” for this specific submission, with multiple earlier submissions of the same version being “Removed” without clear explanation in the UI. My questions: Is there anything I may have done wrong in the submission process (for example, causing multiple “Removed” submissions) that could block or delay this review? Is there any other official channel I can use to get more clarity beyond contacting Developer Support (which only confirmed that it’s “Waiting for Review”)? Has anyone here experienced a similar long “Waiting for Review” state recently, and if so, how was it resolved? I’m worried that there might be some issue with this build or with my account that I’m not seeing in App Store Connect. At the same time, I don’t want to keep canceling and re‑submitting if that could make the situation worse. Any advice from Apple or other developers who have gone through something similar would be greatly appreciated. Thank you, Alan
2
0
139
44m
App Rejected – Guideline 5.1.1(iv) – Location Permission Pre-Prompt With “Not Now” Button
Issue from App Review: My app shows a custom explanation screen before triggering the system location permission dialog. This screen explains why location access is needed. It includes: A “Continue” button → triggers the system permission dialog A “Not Now” button → dismisses the explanation and delays the permission request Apple states that: “The user should always proceed to the permission request after the message.” They are asking me to remove the exit button from the pre-permission message. My Questions Is it now against policy to include a “Not Now” option in a pre-permission explainer screen? Are we required to immediately show the system permission dialog after any pre-permission explanation? What is the recommended UX pattern if the feature depends on location but I don’t want to force the permission immediately at launch? Would it be compliant to: Remove the “Not Now” button, OR Remove the custom pre-prompt entirely and rely only on the system dialog? The feature in question requires location to function properly, but I want to implement it in a user-friendly way that respects user choice and avoids unnecessary denial rates. If anyone has recently resolved a similar 5.1.1(iv) issue, I’d really appreciate hearing how you handled it. Thank you in advance for your help!
1
0
13
1h
Apps stuck on 'Waiting for Review' for over a month
Hi. I've been trying to reach Apple Developer support over the past week now regarding the status of my app reviews. My apps (ID: 6759058241 & 6759189808) has been waiting for review since the start of February 2026. I raised a support request two weeks ago but did not receive any updates or follow ups. May I know how I can get some help on this please? Thank you.
1
0
37
10h
App review stuck in “Waiting for Review” for over 3 weeks (TaskCal: Task Manager)
Hi everyone, I’m an iOS indie developer based in Taipei, and I’m running into a strange App Review delay that I haven’t been able to resolve through the usual channels. My app “TaskCal: Task Manager” (iOS), version 1.2.8, has been in the “Waiting for Review” status since February 9, 2026 in App Store Connect. It’s now been more than 3 weeks with no movement at all — no change to “In Review”, no rejection, no message from App Review. Here are some details: Platform: iOS App name: TaskCal: Task Manager Version: 1.2.8 Status: Waiting for Review Submitted: 2026-02-09 (Asia/Taipei time) Region: App Store Connect account registered in Taiwan I’ve already tried the following: Used App Store Connect → Contact Us → App Review to submit a support request. Got one reply from Developer Support saying they “understand my concern” and that they would “reach out to the appropriate team.” After that, there’s been no further update — the status is still stuck on “Waiting for Review,” and I haven’t received any additional emails or messages in Resolution Center. What I’d like to understand is: Is it normal for an app to stay in “Waiting for Review” for this long (3+ weeks) without any change? Are there any known issues recently with App Review queues or regional review delays that could explain this? Is there any other channel I should use (e.g., calling support, submitting another ticket, or contacting a specific team) to get clarity on what’s happening with this submission? Could there be some hidden problem with my account or app metadata that would cause it to be stuck at “Waiting for Review” instead of moving to “In Review” or “Rejected”? From my side, I’ve double-checked: All required fields and screenshots are filled in. App status shows “Waiting for Review,” not “Missing Information” or “Metadata Rejected.” No messages or required actions in the Resolution Center. Previous versions of this app have already been approved and released without issues. I’m worried that there might be something wrong in the backend, or that my app has somehow been stuck in the queue. As an indie developer, this update is important for my existing users (it includes bug fixes and small UX improvements), so I’d really appreciate any guidance on how to proceed. If anyone has experienced something similar recently, or if an Apple staff member could help check whether this submission is blocked for some reason, that would be super helpful. Thanks in advance for your time and help!
1
1
124
10h
App stuck in review after resubmitting with requested changes
Hi developer community, First time iOS developer here. I originally submitted my iOS app for review on Friday February 20th and was asked to make a small change on Monday February 23rd, which I did promptly and resubmitted with a new build that evening. It's been a week since I resubmitted and wondering if I may have done something incorrectly when reattaching a new build to the review submission. I requested an expedited review on Friday February 27th and contacted support this morning but haven't seen any movement on the "waiting in review" status yet. My app is highly dependent on seasonality (winter sports) and I missed a key opportunity at an event last week to promote the app while the app has been stuck in review. Any guidance or assistance would be super welcome so I can get my app out into the world before we get into the Spring season! App ID: 6759411804 Thanks
1
0
83
10h