Hello, I'm experiencing a serious issue with my Apple Developer account. Every app I submit stays in "Waiting for Review" for more than a month. This is not happening with just one app—it affects every app I submit. Here are the details: Every submission remains in Waiting for Review for over a month. The status never changes to In Review. I have already contacted Apple Developer Support. I also submitted an Expedited Review request, but the apps are still waiting. The apps fully comply with the App Store Review Guidelines and are complete and functional. At this point, I'm trying to understand whether there could be an issue with my developer account or if there is another reason causing all of my submissions to remain stuck in the queue. Has anyone experienced the same issue recently? If an Apple engineer sees this post, I would greatly appreciate any guidance or if my account could be checked. Thank you.

Hello, I am building a developer tool and for that I need to figure out which min deployment targets users technically may still specify in their Xcode projects. This page https://developer.apple.com/support/xcode indirectly says that both Xcode 26 and Xcode 27 allow setting IPHONEOS_DEPLOYMENT_TARGET only to iOS 15.0 and newer. Also https://developer.apple.com/news/upcoming-requirements/ now says that starting April 28 2026, the apps must be built with iOS SDK 26+, meaning only Xcode 26 and newer may be used for building the apps that go to the AppStore. However in fact in Xcode 26 I can specify older iOS deployment targets, as low as iOS 12. This post here https://developer.apple.com/forums/thread/805506?answerId=863871022#863871022 confirms that in fact it is possible to even submit the app to the AppStore with IPHONEOS_DEPLOYMENT_TARGET 12.0 There's also this post https://developer.apple.com/forums/thread/821370?answerId=882853022#882853022 that indirectly confirms that Apple still allows iOS 12.0 deployment target. Since Xcode 26 is still allowed to build apps for the AppStore even after Xcode 27.0 release, does that mean the developers may technically be able to keep specifying iOS 12, iOS 13, iOS 14 as deployment target when submitting their apps to the AppStore without having their apps rejected?

Hi all, I'm hoping someone has seen this before. My app's first submission was rejected, but I cannot find the rejection reason anywhere. What I see: The app-level status shows "Rejected". Under App Review, the submission itself still shows "In Review". There is no reviewer message / no Resolution Center message anywhere, and the in-app purchases are all marked as rejected too. The rejection email only says to visit the App Review page, but the link just opens the App Store Connect root (appstoreconnect.apple.com) with no details. What I already tried: App Store Connect on web (Safari/macOS and Firefox/Windows) and the App Store Connect iOS app — all three show the exact same state. Hard reload, private window, sign out / sign back in. Opened an App Review contact request asking for the specific reasons — no response until now. So the app is clearly rejected, but the submission status and the reviewer feedback never propagated on my end. It looks like a backend status/desync issue. Questions: Has anyone experienced this "rejected but stuck on In Review with no message" state? Where else can the rejection details appear, or is it purely a matter of waiting for the backend to sync? Roughly how long did it take to resolve for you? App: CountTally Submission ID: e9bf771c-a5a2-471f-9db4-7b7038d4ebf9 Thanks a lot for any pointers!

When I sign into App Store Connect, I am taken to this URL: https://appstoreconnect.apple.com/review_agree The page shows a gray activity spinner for a few seconds, then is blank. I have tried on multiple computers and multiple browsers, over the past few weeks, with the same result. I have lodged a developer support request, but it hasn’t been resolved yet. It’s been holding up our App Store submission for a couple of weeks now. Any ideas of things I could try, or has anyone else had this issue and had it resolved ?

I'm trying to submit my app version together with two auto-renewable subscriptions (both in the same subscription group), and one of the two subscriptions will not submit, while the other submits with no issue. Setup One subscription group ("Crucibull Pro") with two subscriptions: Annual — $49.99/year — submits fine Weekly — $1.99/week — fails to submit Both are being submitted together with a new app build in a single review submission. The errors I get (they vary, none are field-specific) "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." "Sorry, something went wrong. Try your request again." "An unexpected error was encountered when submitting for review. If the issue persists please contact us." Critically, there is no red/field-level error anywhere on the Weekly subscription's page — its status is "Prepare for Submission" and every field is filled. What I've tried (nothing has worked) Verified every field on Weekly: reference name, product ID, 1-week duration, availability (all countries), price ($1.99 with a valid start date), localization (display name + description), tax category, and an App Review screenshot. Compared Weekly side-by-side with Annual (which submits fine) and matched every field. Changed Weekly's Tax Category to "Match to parent app" to match Annual. Removed and re-added the items to the submission (per the error message's advice) multiple times. Configured the subscription group ranking/levels. Deleted the original Weekly subscription and recreated it from scratch with a new Product ID — same result. Confirmed App Store Connect is stable (System Status all green) and still errors. Tried fresh submissions, different browser/incognito, and re-uploading the screenshot. Current state The Annual sub and the app build are ready and submit fine. The Weekly sub is fully configured, identical to Annual, freshly recreated, on a stable platform — and still throws generic submission errors with no indication of what's actually wrong. Question Has anyone seen an auto-renewable subscription that's fully configured (and identical to a working one in the same group) fail to submit with only generic errors and no field-level detail? Is there a known backend/propagation issue, or a hidden requirement I'm missing? Any way to see the actual validation failure? Thanks in advance.

I have an app update that is completely ready for submission. This update incorporates a subscription for new functionality. I'm unable to submit as the subscription is stuck in the "Prepare for submission" state instead of going to "Ready to submit" and I'm unable to include it with my app. After doing some research, I found that the banking information on my developer account is broken. I tried to update and fix this information. However, I get an error saying that it is unable to find "Bank of America". I suspect this is causing everything else to be stuck in the "Prepare for submission" state. Does anyone know how to work around this issue or can someone at Apple give me an ETA as to when things will be fixed. This issue is delaying my release. - Ken

Account-level TestFlight failure after app transfer. All apps (including brand-new, non-transferred app) fail with "The requested app is not available or doesn't exist" (Team JYHS43K259) Since receiving several apps via App Transfer, no app on my team can be installed through TestFlight. Every install attempt fails with: "Could not install [App Name]. The requested app is not available or doesn't exist." Critically, this affects not only the transferred apps but also a brand-new app created directly on this account with no transfer history. This indicates an account-level distribution problem rather than an app-record issue. Account details Account holder: BULENT TEKBAS Team ID: JYHS43K259 Account type: Individual Support case: 102936985904 — open for 5+ business days with no substantive response Affected apps Uyku Sesleri — Bundle ID: com.octo8.uykusesleri — Apple ID: 6759616379 — transferred to this account on June 13, 2026 Bekçilik Sınavı 2026 — Bundle ID: com.alhn7.bekciliksinavi2026 — Apple ID: 6756800265 — transferred July 1, 2026 VitaminD — Bundle ID: com.octo8.vitamind — Apple ID: 6768099487 — transferred July 9, 2026 Arete — Bundle ID: com.octo8.arete — created natively on this account, never transferred, currently TestFlight-only All four apps exhibit the identical install failure. Symptoms Builds upload, process, and reach "Testing" status normally Builds are visible in the TestFlight app with an Install button Tapping Install immediately fails with "The requested app is not available or doesn't exist" Reproduced on iPhone 16 Pro running iOS 26 and iOS 27 Internal testing, external testing, and public links all fail identically Already verified / attempted Paid and Free Applications Agreements: Active; banking and tax information complete Pricing and Availability: available in all territories; no app is Removed from Sale Created new versions in "Prepare for Submission" state App Privacy details published; export compliance resolved on all builds Trader status / DSA declaration completed Deleted and reinstalled TestFlight; signed out of Media & Purchases; restarted device; signed back in; accepted freshly generated invitations Removed all testers and re-invited them; generated new public links Uploaded multiple new builds with incremented build numbers — all process successfully, all fail to install Why this appears to be account-level Arete (com.octo8.arete) is a new app with a new bundle ID, created, signed, and uploaded entirely under Team JYHS43K259, with no connection to any previous team. It fails identically to the three transferred apps. The only common factor across all four apps is the team itself. Request Could someone from Apple please check whether Team JYHS43K259 is in a held or degraded distribution state following the recent app transfers? Case 102936985904 has been unanswered for over five business days, and this is blocking updates to live apps with active subscribers. I can provide sysdiagnose logs, build IDs, or any additional information immediately.

I'm trying to submit my app version together with two auto-renewable subscriptions (both in the same subscription group), and one of the two subscriptions will not submit, while the other submits with no issue. Setup One subscription group ("Crucibull Pro") with two subscriptions: Annual — $49.99/year — submits fine Weekly — $1.99/week — fails to submit Both are being submitted together with a new app build in a single review submission. The errors I get (they vary, none are field-specific) "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." "Sorry, something went wrong. Try your request again." "An unexpected error was encountered when submitting for review. If the issue persists please contact us." Critically, there is no red/field-level error anywhere on the Weekly subscription's page — its status is "Prepare for Submission" and every field is filled. What I've tried (nothing has worked) Verified every field on Weekly: reference name, product ID, 1-week duration, availability (all countries), price ($1.99 with a valid start date), localization (display name + description), tax category, and an App Review screenshot. Compared Weekly side-by-side with Annual (which submits fine) and matched every field. Changed Weekly's Tax Category to "Match to parent app" to match Annual. Removed and re-added the items to the submission (per the error message's advice) multiple times. Configured the subscription group ranking/levels. Deleted the original Weekly subscription and recreated it from scratch with a new Product ID — same result. Confirmed App Store Connect is stable (System Status all green) and still errors. Tried fresh submissions, different browser/incognito, and re-uploading the screenshot. Current state The Annual sub and the app build are ready and submit fine. The Weekly sub is fully configured, identical to Annual, freshly recreated, on a stable platform — and still throws generic submission errors with no indication of what's actually wrong. Question Has anyone seen an auto-renewable subscription that's fully configured (and identical to a working one in the same group) fail to submit with only generic errors and no field-level detail? Is there a known backend/propagation issue, or a hidden requirement I'm missing? Any way to see the actual validation failure? Thanks in advance.

Hi all, Like others my app submission has been stuck in “waiting for review” for weeks. I know initial app reviews take longer than updates, but this has been delayed far too long and makes me concerned about repeating the process in the future. I submitted this app for review back on Feb 10. It was initially rejected for a minor issue, which I resolved and resubmitted the same day. After that, the build remained in “Waiting for Review” for about two weeks with no further communication. At that point I canceled the submission and resubmitted the build, thinking it may have been stuck in the queue (I now know not to do this next time). Unfortunately the new submission has also been waiting for review for another 9 days now with no messages or updates. I’ve contacted app review support as well (case ID- 102826632729). I understand review times can vary, but delays like this make it difficult for developers to plan launches or push updates when the review process is the only path to distributing apps. As paying members of the Apple Developer Program, we rely heavily on this pipeline functioning reliably. Hoping this post will reach someone from Apple who can help move the process along. If any other devs have suggestions/tips that have worked for them, please share so others in this position can become unblocked. Thanks in advance.

I submitted an updated version of my app for review on May 18, 2026, and its status has remained "Waiting for Review" ever since. It has now been more than two weeks without any progress or communication from Apple. To resolve the issue, I have: Submitted multiple support tickets through Apple Developer Support. Received the standard message that I would receive a response within 48 hours. Waited more than 15 days, but have not received any reply to any of my tickets. Attempted to contact Developer Support by phone during U.S. business hours, but after waiting on hold for more than two hours, I was unable to reach anyone. This delay is affecting my ability to release important updates to my users, and I am running out of options. Has anyone experienced a similar situation recently? Is there any other channel or escalation process that I can use to get assistance or have my submission reviewed? Any guidance would be greatly appreciated. Thank you.

It doesn't seem to be able to launch. It says "This version of Xcode is not compatible with this version of macOS." So, does that mean that users who have updated to macOS 27 cannot submit apps to the App Store? Do I have to wait until Xcode 27 starts accepting submissions? Environment: macOS 27.0 / Xcode 26.6 RC

Hi App Review team, I'm posting here as a last resort after7 weeks with no movement and 4 unanswered support requests. I'm about to lose my launch window next week and I need someone at Apple to look at this. The situation: App: BMH Themes — App ID 6763770421 — Bundle ID com.bringmedinahome.bmhthemes Version 1.0 (Build 24): reviewed and APPROVED, currently "Ready for Distribution". In-app purchases: 904 are APPROVED, but 1,134 have been stuck in "Waiting for Review" for 7 weeks. The 1,134 stuck items are the exact same type as the 904 already approved — so this is clearly not a content issue. None of the 1,134 show any rejection or "Developer Action Needed" message. Nothing is pending on my side. I have submitted 4 support requests over the past weeks. None received a substantive response. Why this is urgent: My company is now legally registered, my VAT number is being issued, my business bank account is active, and my full marketing campaign is finalized for a launch next week. I cannot launch with 1,134 of my products frozen — releasing a half-empty catalog would waste the entire launch. These stuck in-app purchases are the ONLY remaining blocker. My request: Could someone please check whether these 1,134 in-app purchases are correctly queued, confirm whether there is an internal processing issue, and escalate to the App Review / in-app purchase team? The app is already approved — only these items are stuck. Thank you very much for any help.

Over the last 24 hours, App Store Connect has been performing very slowly, sometimes showing Bad Gateway and sometimes only loading tab views without any content. I use the word "flakiness" because it's happening intermittently. It took over an hour for Xcode Cloud builds to be triggered yesterday, and during that time it was not possible to start builds manually because the github refs weren't refreshing. Today I was unable to load the Users & Access > Integrations > Webhooks page. Since, I've logged out and back in, and now I cannot load any of my apps even though my development team correctly shows with my account info in the top right. Is anyone else experiencing these symptoms? I see nothing on the System Status page other than an outage with Apple Podcasts Connect.

Hello Apple Support Team, My app's new In-App Purchase appears to be stuck in the review process, and I'd like to check whether there might be an issue with the submission. App Information App Name: Foxify AI - Make Your Own Song Apple ID: 6761515837 Item for Review: New Consumable In-App Purchase Timeline Submitted: July 3, 2026, at 6:28 PM As of today (July 8), the In-App Purchase has remained in "Waiting for Review" for 6 days. Context: We submitted a new app build together with this new In-App Purchase so the Apple Review team could test the updated purchase flow and the new consumable IAP. The app build has already been approved and is currently Pending Developer Release, but the new In-App Purchase is still showing Waiting for Review. Since the IAP has not been approved yet, we are unable to release the new version as planned, and our launch date is approaching. Normally, our In-App Purchases are reviewed within 1–2 days, so this delay seems unusual. Could you please help check whether there is any issue with this submission and, if possible, assist with reviewing it as soon as possible? Any guidance or assistance would be greatly appreciated. Thank you for your support.

Hello, My app Jewel Coloring+ Sort Beads IQ+ (App ID: 6785241915) appears to be stuck in the App Review process, and I would like to check whether there may be an issue with this submission. The current version was originally planned for release on June 30, 2026. However, today is July 7, 2026, and the app is still in "Waiting for Review." Current status: Waiting for Review No messages in Resolution Center No requests for additional information We have also submitted multiple Support inquiries but have not received any response so far. This version is particularly important to our team, as it is tied to a planned release schedule and user acquisition activities that had already been prepared in advance. Given the unusually long delay, we are unsure whether the submission is proceeding normally or if there may be an issue requiring attention. If an Apple staff member could help check the status of this submission, it would be greatly appreciated. Thank you for your time and assistance.

Hello, Our GAKO Business update has been repeatedly delayed in “Waiting for Review,” despite multiple contacts with Apple Developer Support and an approved expedited review request. App: GAKO Business Version: 1.3.1 Current submission date: July 3, 2026 Current status: Waiting for Review Expedited review: Approved This issue has been ongoing across multiple submissions for approximately one month. We have contacted Apple Developer Support several times and followed up repeatedly under the same support case. However, the current submission has still not entered review. The update contains critical production fixes affecting existing App Store users. GAKO Business is used by real businesses to manage appointments, employees, schedules, services, and customer records. The currently published version contains issues affecting essential business workflows, while the corrected version remains unavailable. Apple has confirmed that the application was placed in the expedited review queue. However, it remains in “Waiting for Review.” We are not asking Apple to bypass the App Review Guidelines. We would like Apple to verify whether the submission is affected by an internal routing issue, technical hold, or another submission-level problem. Has anyone experienced the same situation where expedited review was approved, but the application remained in “Waiting for Review”? If Apple staff sees this post, we would greatly appreciate assistance in checking the submission. Thank you.

Does the annually updated requirement that apps uploaded to App Store Connect must be built with the latest SDK (i.e. Xcode version) only apply to the main executable or to embedded binaries (e.g. frameworks) also?

Guideline 1.4.3 rejection for a cigar journal app — multiple apps with identical functionality are live on the App Store Hi all, My first submission (a cigar humidor/tasting journal app) was just rejected under Guideline 1.4.3 (Safety – Physical Harm) for "content or features related to the use of tobacco... products." The rejection states the app's concept is "not appropriate because it is focused on these products or activities." The issue: my app doesn't sell tobacco, doesn't facilitate purchasing it, and doesn't encourage consumption any more than a whiskey-tasting log encourages drinking. It's a personal tracking/journal tool — users log cigars they already own, rate them, track humidor inventory, etc. There is no e-commerce, no social sharing of consumption, no promotional content. There are currently multiple apps live on the App Store with functionally identical (in some cases nearly indistinguishable) feature sets: My Humidor – Cigar Journal — https://apps.apple.com/us/app/my-humidor-cigar-journal/id6639582700 Humidor Journal Pro — https://apps.apple.com/us/app/humidor-journal-pro/id6751737114 Ember: AI Cigar Companion — https://apps.apple.com/us/app/ember-ai-cigar-companion/id6761503587 Whiskey and Cigar Pairing — https://apps.apple.com/us/app/whiskey-and-cigar-pairing/id6762530184 Cigarbase: AI Cigar & Humidor — https://apps.apple.com/us/app/cigarbase-ai-cigar-humidor/id6761301449 Leaf Enthusiasts — https://apps.apple.com/us/app/-/id6757314729 Cigar Journal & Tracker: Puro — https://apps.apple.com/us/app/cigar-journal-tracker-puro/id6760948482 ASHD – Cigar Social — https://apps.apple.com/ca/app/ashd-cigar-social/id6759581213 All of these are humidor/cigar journaling or social apps built around cataloging and tracking tobacco products — the exact category my app was rejected for. Several even use AI companion/recommendation features, which is a superset of what my app does. Full rejection text for reference: Guideline 1.4.3 - Safety - Physical Harm Issue Description: The app includes content or features related to the use of tobacco, nicotine-related, or vaping products, including but not limited to cigarettes, pipes, hookahs, or e-cigarettes. Apps with content or features related to consuming tobacco are considered to encourage the consumption of tobacco. Since these products pose a risk of physical harm to users, it is not appropriate to encourage their use. Next Steps: Your app's current concept is not appropriate because it is focused on these products or activities. It would be appropriate to revise the app or submit a new app that is not focused on these products or activities. My questions for the community: Has anyone successfully appealed a 1.4.3 rejection for a tobacco tracking/journal app (as opposed to a marketplace or vaping-hardware app) by citing comparable live apps? Is there a meaningful distinction reviewers are drawing between "journal/inventory" apps and something else, and if so, what specific wording or framing helped get it approved? Is the right move to reply in App Store Connect citing these examples, or file a separate appeal with the App Review Board? Any input from developers who've navigated this — especially in adjacent categories like whiskey, wine, or other regulated-but-legal-consumable tracking apps — would be hugely appreciated. This is my first submission, so I want to handle the response the right way rather than burning an appeal on the wrong approach. Thanks in advance.

Hi, I'm having a problem because my app stuck in "waiting for review" status since Friday (June 26th). Today is the fifth day we've been waiting for Apple to review the app. We had an app lunch scheduled for today and are stuck with no information. We contacted Apple via the standard contact form and requested expedited app review, but unfortunately, nothing has changed; we haven't received a response to our messages. The app is still "waiting for review." What should I do? Is there another way to contact Apple to expedite the review, or at least get information about the review date? App Name: Genie Vault App ID: 678469924

I want to delete an app from App Store Connect, but I've been unable to do so. App Information: App Name: Need to be removed-MI Apple ID: 6742525904 Current Status: Prepare for Submission I have already followed Apple's official guidelines for removing the app: https://developer.apple.com/help/app-store-connect/create-an-app-record/remove-an-app/ The following operations have been completed: App information has been reset; All in-app purchases have been deleted/cleared; All subscriptions and subscription groups have been deleted/cleared; The app has been removed from all sales regions; App Review Submission has been removed; The submission record in the App Review page now shows as Removed; Logged out and re-logged into App Store Connect; Browser cache and history have been cleared; Attempted to repeat the process using Safari for Mac and different network environments. Currently, when deleting the app, a prompt still appears: “This app is unable to be removed right now. This app cannot be removed. Learn more about removing apps. This app has in-app purchases that are in review. Please try again once these in-app purchases are no longer being reviewed.” The previous error message also included: “Some items related to this app are currently in review. To remove this app, you must first cancel the submission.” However, after removing the App Review Submission, this section has disappeared, and only the prompt related to "in-app purchases that are in review" remains. Currently on the App Store Connect front-end page: The In-App Purchases page is empty; The Subscriptions page contains no subscription items or subscription groups; App Review submission history has been removed; The app is currently in the Prepare for Submission state; No IAPs, subscriptions, or submissions currently under review can be found. Previously, the Subscriptions page displayed a notice: “One or more of the subscriptions listed below requires your attention.” However, the page does not display any subscription items or subscription groups. I'd like to ask if anyone has encountered a similar situation: the front-end page no longer shows any IAP or subscription items, yet when deleting the app, it still prompts that in-app purchases are under review? Is this situation due to residual IAP/Subscription review statuses left behind by Apple's backend, requiring contact with Apple Developer Support for cleanup? Or is there another hidden entry in App Store Connect that can be used to remove these lingering items?