Hi, I designed and created 2 apps to help protect 2 dying languages. One is Sonny Goes to School for the Osage Nation in US and the other is Maskosis Goes To School for Samson Cree Nation in Alberta Canada. The concept is similar and the animations are similar. We use the same characters that we drawn for the first project (Maskosis) and reuse them for the 2nd project (Sonny). We now need to update the apps so they can be used on newer devices. However the app review team kept rejected the updates saying we are spaming the app store. They advice us to "submit a unique app with distinct content and functionality." To recreate all the animations would be very very expensive. I do not know how to proceed, does anyone have any ideas? I attached part of their reply below. No matter how I explain myself, they just kept replying back saying I am spam... "Guideline 4.3(a) - Design - Spam Issue Description We noticed the app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review the app concept and submit a unique app with distinct content and functionality. "

Hi everyone, I am facing an unusual and prolonged delay with the App Store review process for my app, "ismth水木" (Bundle ID: net.ismth). It has been stuck in the "Waiting for Review" status for 60+ days since my last submission on March 22, 2026. Here is the quick timeline: Feb 20, 2026: First submission. Mar 21, 2026: First rejection received (resolved the issues immediately). Mar 22, 2026: Resubmitted with adjustments. Current Status: Still "Waiting for Review" (has not even changed to "In Review"). I have contacted Developer Support multiple times (Case ID: 102836154889), but I keep receiving the same automated template responses stating that they need more time, with no specific details. Since the vast majority of reviews take less than 48 hours, a 60-day delay without even entering the review stage is highly unusual. I am deeply committed to complying with Apple’s guidelines, but the lack of transparent communication makes it impossible to know if my account is being audited or if there is a technical misunderstanding. Has anyone else experienced a similar "Waiting for Review" bottleneck recently? Any advice on how to escalate this, or any insight from Apple Staff here would be greatly appreciated. Thank you!

Hi, My app ID: 6762301629 has been stuck in "Waiting for Review" since 17 May. We are worried there might be a system glitch or a hidden blocker holding up the process. Just wondering if there is anything we need to do on our end. Any help or a quick check from the App Review team would be greatly appreciated. Thank you!

Hi Team, My app ICY SIM (App ID: 6761278922) has been stuck in "Waiting for Review" for over 4 weeks with no movement, no feedback, and no communication. What I've done: Submitted multiple expedited review requests and resubmissions (I now understand this can reset queue position, so I've stopped doing that) Filed a support ticket 3 days ago (Case ID: 102895038326) — still no response I completely understand the team handles a high volume of requests. However, 4 weeks with zero communication — not even an acknowledgment of the support ticket — is concerning. What I'd like to know: Is there a system glitch, account flag, or hidden blocker preventing my submission from entering review? Can someone confirm my app is actually in the queue and not stuck due to a technical issue? A queue position or estimated timeline would go a long way Any visibility from the App Review team or anyone who has experienced a similar situation would be greatly appreciated. Thank you.

I'm submitting a new version of my app, and after click "submit for Review", it show that: A few more items are needed in order to submit for review The items listed below are required for submission:There are still screenshot uploads in progress. I didn't met this problem before. Is that mean I haven't upload all the screenshot required or it's still uploading the screenshots to App Store Connect's server? Cause before there is a "save" button after you drag images to the screenshots area, now you don't. And I think I have uploaded all the screenshots needed and I waited a day to try submit again, still the same. What should I do?

Hello everyone, I'm facing a very frustrating situation with App Review for my indie app, CoffeePomodoro, and I'm hoping someone here or an Apple engineer can help shed some light on how to escalate and resolve this. My recent update (Version 1.3.1, Submission ID: 59763b52-7c14-4b27-a2cf-2799d2bafe35) was rejected under Guideline 3.1.1 - In-App Purchase. The rejection message states: "We found that the app includes a feature to restore previously purchased In-App Purchase products by entering the user's Apple Account and password. However, In-App Purchases cannot be restored in this manner." The Reality: There is absolutely zero custom UI, form, or TextField in my app that asks for an Apple ID or password. When a user taps "Restore Purchases", the app simply calls Purchases.shared.restorePurchases() via the RevenueCat SDK, which directly wraps Apple's native SKPaymentQueue.restoreCompletedTransactions(). The credential prompt the reviewer saw is the native iOS system-level authentication dialog that appears automatically in the sandbox/TestFlight environment. This usually happens if the device or simulator being used for the review doesn't have an active Sandbox Apple ID already logged in. I have explained this in the App Store Connect Resolution Center. I provided screen recordings showing it's the system dialog, and I attached code snippets proving the app only calls native APIs. Unfortunately, my explanations seem to be ignored, and I keep facing the same roadblock. It feels like the reviewers are mistaking their own OS's native prompt for a custom credential-harvesting screen. Meanwhile, my users are waiting for this update to resolve their subscription issues, and I am stuck in a rejection loop for using Apple's own native API exactly as intended. Has anyone else experienced this specific misunderstanding by the review team? How can I escalate this so someone actually reviews the screen recording and code snippets I provided? Thank you for your time.

I'm trying to get a promo code for my app, and get vectored off to DevConnect to checkout the updated "Apple Developer Program License Agreement". Trouble is is that it shows no "updated" flag, button or whatever it is that I should be able to click to accept it. Bug?

I haven't updated my app in months, but I discovered my app icon color recently changed entirely on its own, and it displays inconsistently in App Store, App Store Connect, and TestFlight. Everything works fine locally during development. It's all as expected in Icon Composer and Xcode. Typically, the icon shows a white symbol on a blue background. But now, online, the white symbol is a dark red color, and there seem to be additional Liquid Glass and shadow effects that I never chose. So, somewhere in Apple's backend processing of my .icon file, it's getting malformed and rasterized with different parameters than expected? And different cached versions are being displayed in different places? On web, it's showing the incorrect version. Same in App Store Connect and TestFlight. In App Store on iOS, the incorrect version is shown in search results, but the correct version is shown on the product page. I've attached some screenshots. Store link: https://apps.apple.com/us/app/kitchenkit-grocery-organizer/id6754018760 Related threads: https://developer.apple.com/forums/thread/812852 https://developer.apple.com/forums/thread/811770 https://developer.apple.com/forums/thread/823078

My app has been stuck in the “Waiting for Review” stage for the past 9 days, and I have not received any updates, feedback, or rejection notices. I have already contacted support multiple times regarding this issue, but unfortunately I have not received a response yet. I have spent a significant amount of time and resources building this app, including purchasing the required Apple Developer subscription and preparing everything according to the App Store guidelines. I kindly request you to please check my submission status or let me know if there is any issue causing the delay. Even a small update would be greatly appreciated. Case ID: 102893147964

Hi Team, My App : LuvLust: Couples Game & Quiz (App ID: 6747910861) has been stuck in "Waiting for Review" for 3-4 weeks with no movement, no feedback, and no communication. What I've tried: Multiple expedited review requests & resubmissions although I understand now that's not the best way as it resets my position. I understand there are lot of requests but a queue number or some form of communication would help. Just want to know if there is a system glitch, account flag, or hidden blocker preventing my submission from entering review. Any help from the App Review team would be greatly appreciated. Thank you.

Hi Apple, I hope you are doing well. I am posting here regarding my app, Subscription & Expense Manager (App ID: 6759901202), which has been stuck in the “Waiting for Review” state since March 4, 2026 at 2:45 PM. It has now been an extremely long time without any update, review progress, or communication from the App Review team, and I am becoming increasingly concerned about this unusual delay. I completely understand that review times may vary depending on workload and internal processes, but this duration seems far beyond normal review timelines. Our team has invested substantial time, effort, and resources into developing this application, and the continued delay is significantly affecting our launch plans and business timeline. We have carefully followed all App Store Review Guidelines and ensured that every required detail, asset, permission, and compliance item was properly submitted. At the moment: There are no rejection messages No metadata issues are shown No additional information requests are pending The app simply remains stuck in “Waiting for Review” We have also already contacted Apple regarding this matter but unfortunately have not yet received a response. I would sincerely appreciate it if someone from Apple or the developer community could guide me on: Whether this kind of delay is currently common If there is any way to escalate the issue Whether there may be an unseen issue causing the review to not start We are fully prepared to provide any additional information or make immediate changes if required from our side. This app is very important to us, and we are genuinely worried because of the extended delay after putting so much hard work into the project. Any help, advice, or update would be greatly appreciated. Thank you. HR Apps

Hey, Our app has been “Waiting for Review” for almost 7 days now. Case ID: 102895656971 If anyone from Apple reads this, please help.

Hey All, Having a terrible time trying to submit subscriptions to the App Store. Any help or guidance would be much appreciated. Setup Auto-renewable subscriptions (Monthly + Annual) and one non-consumable (Lifetime), all attached to first binary submission RevenueCat for IAP infrastructure What happened First submission (v2.26): all three IAPs attached cleanly to the binary submission via the "In-App Purchases and Subscriptions" section on the version page. Apple's review came back with feedback on the paywall display (Guideline 3.1.2c - auto-renewable subscription prices not visible). The reviewer's screenshot showed Lifetime rendering correctly with a price, but the two subscription rows blank. I was missing a localization setting, which I then fixed. The localization went into Waiting for Review, then back to Rejected again within hours - App Store Connect's UI explains this: items attached to a rejected app version submission cannot independently progress through review. I then cancelled the v2.26 submission, which freed the localization to be re-submitted standalone. That stuck. I built a new binary (v2.27) and uploaded to App Store Connect. When I opened the v2.27 version page, the "In-App Purchases and Subscriptions" section that Apple's documentation describes (and which appeared on v2.26) was no longer present. I couldn't find any UI way to attach the subscriptions to this version's submission. The subscriptions and localization remained in Waiting for Review from earlier, and the Draft Submission panel for v2.27 only listed the binary. I submitted the binary alone in the hope that Apple's backend would bundle the in-queue subs with this version's review (since they all reference v2.27). Apple's reviewer reported the same display behaviour I see in my own testing - Annual/Monthly blank, Lifetime shown - and rejected on Guideline 2.1(b). What I've tried Resaving + resubmitting the group and per-subscription localizations Replying via Resolution Center with detailed context Updated App Review notes explaining the dependency between the subs and the binary Re-recorded the paywall screen recording on the current build Confirmed Paid Apps Agreement is Active and Tax / Banking are complete Completed a previously-incomplete "Sharing Economy Reporting Regime" compliance row that was in Missing Info (doesn't apply to my app, but flagged complete to rule it out) Sandbox testing on the iOS simulator with a sandbox tester signed in via Developer → Sandbox Apple Account: Lifetime renders its price, Monthly/Annual remain blank (same as Apple's review environment) Verified all product configuration in App Store Connect - pricing across territories, intro offers, localized display names + descriptions, review screenshots are all present Verified the RevenueCat offering correctly references the product IDs and the "pro" entitlement is properly linked Questions Is there a way to surface the "In-App Purchases and Subscriptions" attachment section on a new version after the first version was rejected? Something I'm missing in the configuration? For subscriptions sitting in Waiting for Review that are tied to a now rejected version, is there a way to attach them to a new version submission so they're reviewed together? If recreate with new IDs is the only path, is there any way to preserve the original product IDs for the subscription identifiers eventually, or are they permanently consumed? Thanks all, Cheers r

Hi Team, I have an application (6762230721) that has been in review for about 7 days now. Wondering if there is anything I need to do. Thanks, Patrick

Hey everyone, Starting to get a bit anxious here. Our app has been stuck in “In Review” for an unusually long time, and we haven’t received any updates or communication from Apple yet. Usually reviews are much faster for us, so this delay has us worried that something may be wrong or stuck in the process. We have an important release planned, and the uncertainty is honestly stressful. Has anyone else experienced unusually long review times recently? Did your app eventually go through, or did you have to contact Apple? Would really appreciate hearing others’ experiences. Thanks 🙏

Hi Apple App Review Team. My app (ID: 6761986315) has been waiting for review since 14 April 2026. Any assistance would be greatly appreciated.

As a game studio with real business commitments, we depend on a predictable App Review process. Every month, we publish updates, run user acquisition campaigns, and test new ideas; that’s how our business operates. It’s not optional. We have obligations to our partners, our marketing budgets are committed in advance, and our entire monthly rhythm depends on getting builds out on schedule. Right now, Apple’s App Review is making that impossible. For the past 30 days, we’ve been stuck in a rejection loop on a single submission. Here’s what the cycle looks like: • Apple rejects our build with vague, generic feedback that doesn’t actually identify what’s wrong. • We investigate every possible scenario that could conceivably match their description, fix what we believe is the issue, and resubmit, usually within three hours. • Then we wait. And wait. Each review of the resubmission takes more than ten days. Read that again: we respond in 3 hours, they respond in 2 weeks. This isn’t a one-off. It’s been three full cycles now, and we still don’t have clarity on what they actually want changed. The rejection notes are so shallow that we’re forced to guess; patch a plausible cause, ship it, and hope. It honestly feels like reviews are being triaged by AI models that aren’t ready for the job yet: surface-level pattern matching, no real engagement with the build, no specifics we can act on. Meanwhile, the cost is real: • UA campaigns we’ve already committed budget to are bleeding out. • Partner deliverables are slipping. • Our team’s monthly release rhythm — the engine of how we operate as a business — is broken. • We’re paying engineers to play guessing games with a reviewer who won’t tell us what’s wrong. We’ve escalated everywhere we can. Contact forms, appeals, developer support, every channel Apple offers. Nothing has moved. We love the platform. We want to keep shipping great games on iOS. But Apple needs to understand that App Review isn’t just a gatekeeping checkbox, it’s a load-bearing piece of every developer’s business operation. When a single rejection cycle eats 10+ days and the feedback isn’t actionable, you’re not protecting users. You’re breaking the businesses building for your platform. Two things need to change, urgently: 1. Restore meaningful, specific rejection feedback. Tell us exactly what’s wrong, with reproduction steps. If a human reviewer can’t be specific, an AI definitely shouldn’t be making the call. 2. Prioritize resubmissions on an in-flight review. A 10-day turnaround on a fix to a rejection you issued, three hours earlier, is indefensible. These should jump the queue, not start at the back. If anyone at Apple is reading this: we’re trying to work with you. Please help us help you. Want me to tighten it, make it angrier, soften it, or pull out the bullet lists so it reads as straight prose for the forum?

Hello, I am experiencing an App Store Connect issue where my In-App Purchases are not attaching to the app review submission. Current situation: The IAP products are fully configured. Status is currently "Waiting for Review". Product IDs match the app code correctly. Sandbox testing works correctly. However, the app version page does not display the "In-App Purchases and Subscriptions" section at all. App Review repeatedly responds that they cannot locate the IAPs during review. It appears the IAP submission linkage between the binary and App Store Connect may be corrupted or missing. App: Phantom Spy I would appreciate any guidance or escalation assistance. Thank you.

I had everything working with Revenue Cat. Then my app got rejected for not loading subscriptions, which was odd because a previous built was rejected for wording on that same paywall. I checked, and realised I suddenly can't fetch products in testFlight either. I can only see products in Xcode using the store kit configuration file. I've found many issues like this online and everybody point to the same solutions (that seem to work for most), but here's what I tried so far: Checked that all my agreements in App Store Connect are active Checked that ids match between Xcode / revenue cat / App Store connect Store kit config file is syncing with App Store Connect correctly I removed revenue cat and used the store kit api directly to fetch products. The array of products is empty in all environments that don't have access to store kit config file. Checked status of all subscriptions (all waiting for review -- as they were when the paywall worked) Nothing seems to work... Any suggestions? Many thanks

I was using the iOS 15 beta on my iPhone 12 Pro Max, long story short after upgrading to the full release of iOS 15, my iPhone will not prompt to use faceid for App Store or iTunes Store purchases. I’ve tried signing in and out of iCloud, disabling and renabling Face ID but no luck. I see others have had this issue since the general release of iOS 15 but no comment has been made by apple support. Any advice on a solution?