Our app Heat Game (iOS, version 1.15.0) has been in the "In Review" status since April 18th. We have received no feedback, rejections, or communication from the App Review team for over 10 days, despite a "last touched" update on April 22nd. Submission Timeline: Submitted: April 17, 2026 In Review since: April 18, 2026 Last Activity: April 22, 2026 Current State: IN_REVIEW (No metadata issues or rejections flagged) Why this is critical: This is not a routine feature update. Version 1.15.0 contains critical fixes for broken payment flows currently live in the production version. These bugs are actively preventing users from completing purchases, leading to: Direct Revenue Loss: Significant daily financial impact on our operations. Steps taken so far: We have already reached out via the App Store Connect Resolution Center, but have not received a substantive response. Request to Community/Apple: Has anyone successfully escalated a review specifically for time-sensitive, revenue-blocking bugs? Beyond the Resolution Center, are there documented channels or specific keywords that help flag a case for "Expedited Review" when it involves significant business impact? We appreciate any guidance or assistance the community or Apple staff can provide.

Hello, I'm hoping someone from Apple or the community can help me get some clarity on my situation. Two months ago, my app was rejected by App Review, and I immediately filed a formal appeal. Since then, I have received absolutely no response — not an acknowledgment, not a status update, nothing. In the meantime, I have also reached out to Apple Developer Support via email on multiple occasions. Again, no response of any kind. I understand that review and appeal timelines can vary, but two months of complete silence — across both the appeal process and direct support emails — makes it very difficult to know whether my case is even being reviewed or if something has fallen through the cracks. If anyone from the App Review team or Apple Developer Relations sees this, I would appreciate any guidance you can offer. And if any developers have been in a similar situation, I'd like to know what worked. Thank you.

Is anyone have issues with builds not appearing under the Build section in itunesconnect?I've successfully submitted multiple builds, but the builds do not appear in itunesconnect. I know that it's in the system because when I try to upload a build with the same version and build number, it errors out saying the version has already been uploaded.

Hi, App ID 6756673679 has been approved in prior cycles relatively quickly. The current review cycle began on April 17, and entered "In Review" as quickly as prior submissions. After working through Resolution Center on some items, we spoke with Apple Developer Support on Wednesday (case 102875923017), who applied an expedited flag and advised us to resubmit. It's now been ~27 hours since it was expedited, and ~6 days since the submission cycle began. Would someone from App Review be able to take a look and confirm whether there is any specific blocker or provide any update on expected timing? Thank you.

Our app (id 1611398578) has been stuck "In Review" in App Store Connect for 15 days, after being approved quickly by App Review. We contacted Apple Support multiple times through email and phone, but we did not receive any response. Today we tried re-submitting a new version hoping it will trigger a system reset and fix the issue. The submission for iOS was approved very fast by App Review, but it is again stuck "In Review". PLEASE APPLE HELP US GET THIS ISSUE RESOLVED!

Hello, Our app has been stuck in "In Review" for 7 days, after being approved. The iOS version was approved on April 9th and the macOS version was approved on April 12th. Since then, both versions show "In Review" and there has been no status changes or messages in App Store Connect. • April 8 ---> Waiting for Review • April 9 ---> In Review (Approved) • ... • April 16 ---> In Review We contacted Apple a week ago (case ids 102865508515 and 102865870578) but there was no response. We also talked to Apple Support, they told us the issue has been escalated to the technical team. There are also leaderboards that were archived before these last versions and they are still showing in the Games App and Game Center. Possibly because of this same issue, we suspect. At this point we don't know what the issue is, how long until these very important updates will go live, or when we can push other updates. App ID: 1611398578 Thanks.

Hi, My app (Team ID: H4DH43B9X7), despite the requested expedited review, has been stuck in “Waiting for Review” since Thursday. This occurred after the app had already been approved multiple times and then received an incorrect rejection referring to “gender,” whereas the app actually requests biological sex, clearly described in the UI as required for metabolic calculations (BMR/TDEE), which are core to its functionality. Since this is causing us financial problems, I would greatly appreciate an update on its review status as soon as possible.

Hi, I'm using AppTransaction.originalAppVersion to detect whether a user originally purchased the app under the old paid model, so I can automatically unlock the app for them as a courtesy when migrating to freemium. Background On iOS, originalAppVersion returns CFBundleVersion (the build number). When I transitioned the app from paid (v1.x) to freemium (v2.0), I defined a numeric threshold for CFBundleVersion to distinguish legacy purchasers from new users: Build number below the threshold → v1.x purchase → auto-unlock Build number at or above the threshold → v2.0+ install → requires IAP In Production, originalAppVersion correctly returns the actual build number, and the comparison works as intended. Detection logic (simplified) // Determine environment via receipt URL func detectStoreEnvironment() -> String { if let url = Bundle.main.appStoreReceiptURL, url.lastPathComponent == "sandboxReceipt" { return "Sandbox" } return "Production" } // Legacy check using numeric comparison static func isLegacyPaidUser(version: String, threshold: String) -> Bool { guard !version.isEmpty else { return false } return version.compare(threshold, options: .numeric) == .orderedAscending } // In checkLegacyPurchase(): let version = appTransaction.originalAppVersion let isLegacy = isLegacyPaidUser(version: version, threshold: legacyBuildNumberThreshold) let env = detectStoreEnvironment() let shouldAutoUnlock = isLegacy && env != "Sandbox" The problem I know that in the Sandbox environment, originalAppVersion always returns "1.0" — this is mentioned in the AppTransaction documentation. My code already suppresses the auto-unlock for Sandbox (env != "Sandbox"). However, it appears that the App Review environment also returns "1.0" for originalAppVersion. Because the receipt URL path component is "receipt" (not "sandboxReceipt"), my environment detection classifies it as "Production" — so the Sandbox suppression doesn't apply. The reviewer is incorrectly identified as a legacy paid user and the app is unlocked without a purchase. This caused our v2.0 submission to be rejected under Guideline 2.1a. Questions Is it documented that the App Review environment returns "1.0" for AppTransaction.originalAppVersion, similar to Sandbox? Is there a reliable way to detect the App Review environment specifically — separate from both Sandbox and Production? For example, does the receipt URL differ, or is there another API? Is using originalAppVersion for legacy paid-user detection a supported pattern? If so, what is the recommended approach to handle the App Review case? Any guidance would be greatly appreciated. Thank you.

I have a new app which has been submitted for review, and has been rejected.. The tester unable to see subscription settings.. He/she has not looked very far, they are in the app settings tab, and that was noted in the app submission. The likely issue is that this is an iPhone app, and specifically not for iPad.. Yet the reviewer used an iPad to test! This is the third consecutive rejection for administrative issues which have nothing to do with the app itself, and which, if the reviewers were to look properly, are not actually issues at all. This feels as though the reviewers are trying to get through as many reviews as possible in the shortest time possible, and not taking the time to examine an app submission properly. They are undermining months of hard work with a 30 second scan.

My app (Markets: Global Trading 24/7, version 1.0.6, App ID 6756673679) was rejected on April 20 for Guideline 1.2. Apple's rejection message offered the option to demonstrate compliance via a screen recording, which we provided in Resolution Center the same day. The submission has remained in Rejected status while we await a response. Do we need to click "Update Review" to surface this to App Review, or are we supposed to wait in "Rejected" status until we get a Resolution Center reply? Thank you.

I’m looking for some advice regarding the usage of temporary exception entitlements in Mac App Store apps. Specifically the Apple Event Temporary Exception to communicate with other third party applications (not first-party macOS system apps): The Best Practices for Submitting Scriptable and AppleScript Apps to the Mac App Store section is a bit vague (how to 'request' a temporary entitlement?) and I couldn't find it mentioned in the Review Guidelines. Before designing, implementing and testing functionality based on the Apple Event Temporary Exception I’d like to know if these entitlements would: A. Always be rejected on the Mac App Store B. Only accepted in highly specific use cases C. Accepted if there is a clear use case and sufficient argumentation For this particular use case I’d like to send Apple Events to Adobe Illustrator and QuarkXPress. The application helps the user with some design tasks in their documents. The app requests the currently open documents and accesses document content to process used design elements. This is optional functionality that the user must explicitly enable in the app. I’m aware that the com.apple.security.scripting-targets entitlement is preferred. (Side question: are these always allowed or can they also be rejected for third party app scripting?) However, many third party applications don’t offer any scripting access groups in their definition, including Adobe Illustrator and QuarkXPress in this case. So before spending a lot of time implementing this feature I’d like to have some indication whether it is unlikely that sending Apple Events to third party apps will be allowed on the Mac App Store. Thanks for any insights!

The new version of our app uses Advanced Commerce API via in-app purchase. The app itself was approved but the in-app purchase associated with the app version is still Waiting for Review. Is there anything else we can do? Any way to expedite the review of the in-app purchase itself?

Hi, This is my first time releasing an app to the store and it's been stuck in a "Waiting to review" state for about 5 days now. From what I gathered, most apps should be reviewed within a 48 hour period. I was just curious if there's something blocking it being sent to the In Review state. Thanks for any help you can provide.

Hi all, I have a build in "Waiting for Beta App Review" that has been stuck for more than three days, well beyond the typical 24-48 hour window. Context: • Internal-use app distributed via TestFlight only (no App Store release). • Uploaded approximately April 18, 2026. • No ITMS warnings, no rejection notice, no request for additional information. • A newer build was uploaded today (April 21, 2026). It processed correctly and is also now awaiting Beta App Review behind the older one. • I noticed another forum thread referencing FB22543589 / Case ID 102872835864, reporting TestFlight builds being flagged as Expired/unavailable overnight between April 20 and April 21, 2026. I would like to rule out whether my submission was affected by that incident. Questions: Has anyone else experienced Beta App Review delays during the week of April 20, 2026? Beyond filing a Feedback Assistant report, is there a recommended escalation path for stuck beta reviews? If my pending build was affected by the April 20-21 TestFlight incident, does re-uploading resolve it, or does the new build simply re-enter the same queue with the same delay? I have also submitted a support request via the Contact Us form, but wanted to check with the community in case others are seeing the same pattern this week. Thanks,

Hello, I recently submitted an update for my app, and I would really appreciate it if you could review it when possible. The latest version includes important fixes and improvements. Please let me know if anything else is needed from my side. Thank you for your time and support.

Hello, I'm looking for guidance on a submission that appears to be awaiting re-review following my response to a "2.1 Information Needed" message. App: Markets: Global Trading 24/7 App ID: 6756673679 Version: 1.0.6 Timeline (all times ET): Apr 17, 10:45 AM: Submission entered "Waiting for Review" Apr 17, 9:25 PM: Moved to "In Review" Apr 17, 10:14 PM: Received "2.1 Information Needed" message regarding the OTP demo account flow Apr 17, 10:45 PM: Replied in Resolution Center clarifying the OTP behavior Apr 20, 9:10PM: Still awaiting response, and in "Waiting for Review" status The App Review FAQ notes that messages in Resolution Center are generally responded to within 24 hours. My reply has now been pending for approximately 3 full days, so I wanted to check in here in case it would be helpful to surface this. Our prior two updates to our published app were approved quickly, and the 2.1 message concerned the demo account OTP flow, which I responded to in detail in Resolution Center. If anyone from App Review is able to take a look, I would very much appreciate it. Happy to provide any additional information that would help. Thank you, Chuck Bradford Dexari Inc.

Hey my app subscriptions are currently in review whilst my app has been approved 2 times, i need this to be approved to start marketing it.

Hello, My app "Tall - App de rencontre" (App ID: 6761081326) has been rejected 4 times under Guideline 4.3(b) Design Spam. The App Review Board also upheld the rejection (Appeal Ticket APL411770). I fully understand the dating category is saturated. However, my app has unique mechanical features that do not exist on any other dating app on the App Store: MANDATORY HEIGHT GATE: During registration, women below 1.75m and men below 1.80m are blocked and CANNOT complete registration. This is hard-coded into the onboarding. It is not an optional filter. Users who do not meet the height criteria simply cannot use the app. DOOR-FRAME HEIGHT VERIFICATION: Users must submit a full-body photo standing barefoot under a standard door frame to verify their height. Unverified users see all other profiles blurred. This trust-and-safety mechanism is entirely unique. "THE BAKERY": A curated, time-limited daily drop of compatible profiles replacing infinite swipe. This is an anti-swipe paradigm designed to prioritize quality over quantity. I also have an existing community of over 1,000 people across multiple WhatsApp groups TALL FRANCE, 10K Instagram followers, and 44K TikTok followers — all specifically for tall people looking to connect. This proves real demand for this niche. I also noticed that the app "Score Dating" is currently live on the App Store in the Lifestyle category. Score blocks users who do not have a credit score of 675 or above. My app uses the same concept — a mandatory gate based on a specific criteria (height instead of credit score). If Score is accepted, I believe Tall should be evaluated with the same standard. I have responded to every rejection with detailed explanations and visual evidence, but received the same copy-paste response each time. I have a Meet with Apple consultation scheduled to discuss this further. Has anyone successfully overcome a 4.3(b) rejection for a niche app with genuinely unique features? Any guidance from Apple or the community would be greatly appreciated. Thank you, Frankie Babet

My apps are stucked in „Waiting for revlew” for 6-7 days. What is going on? It’s not only my problem, a lot of users have the same problem, there are many forums with that issue. It’s pretty unbelievable for me, that in 2026 we have to wait about week to approve or reject an app. Ridiculous. Take the example of Google Play…. Regards.

My app is waiting for review for more than 48 hrs since Wednesday at 5:57 PM. It has been rejected, and errors were fixed with an updated new build. Is this normal?