I’ve been trying to get this app through App Review for more than two months now. It was rejected a few times before. I changed what Apple asked me to change and submitted it again each time. The current version has now been sitting in Waiting for Review for quite a while and nothing is happening. I’m actually not very familiar with the App Store review process, so I’m not sure how long Waiting for Review is supposed to take. Do I just leave it there and wait? Or should I submit it again? I’m also wondering if I need to create a new submission / new ID at this point. I don’t want to keep changing things if that just sends me back to the beginning of the queue. The whole thing has already been going on for more than two months, so I’m a bit lost on what I’m supposed to do now. Has anyone run into this before?

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.

Hello, I renewed my Apple Developer Program membership on July 29, 2026. The payment was successfully processed, I received the invoice and renewal confirmation, and the Apple Developer website shows that my membership is active. For approximately one week, App Store Connect has continued to display this error: Developer Program Membership Expired Your membership has expired, and your apps have been removed from the App Store until you renew your membership. To renew, a user with the Account Holder role must sign in and renew the membership on the Apple Developer website. Because of this incorrect status, I cannot submit apps, and App Store Connect states that my existing apps have been removed from the App Store. I have contacted Apple Developer Support multiple times. I received two responses, but neither addressed the App Store Connect membership-status issue. The renewal itself is already complete; the problem appears to be a synchronization issue between the Apple Developer portal and App Store Connect. Has anyone experienced this situation? How long did synchronization take, and was there a specific support team or escalation path that resolved it? Any advice would be appreciated.

Our app cannot be found by its own name on the France App Store, because search silently rewrites the query. App: Kaiho: Arrêter de fumer / Kaiho: Quit Smoking Coach Apple ID: 6760356299 Feedback Assistant: FB24267557 WHAT HAPPENS Searching "Kaiho" on the France storefront returns kaiju monster games. The page reads "Affichage des résultats pour « kaiju »" ("Showing results for kaiju") with a "Rechercher « Kaiho » à la place ?" link underneath. Our app is not in the results at all. The first item served is a paid ad for an unrelated app, then KAIJU N° 8 THE GAME. THIS IS NOT A RANKING QUESTION The app is correctly indexed on that same storefront: searching "kaiho arreter de fumer" returns it as the #1 result. The substitution happens before ranking the term itself is replaced. TWO APPLE SYSTEMS DISAGREE While typing, the App Store's own autocomplete proposes "kaiho: arrêter de fumer" as its first suggestion, and offers "kaiho in Developers". After submitting, the results engine rewrites the term to "kaiju". The suggestion service and the results engine hold contradictory views of the same query. REPRODUCIBLE ACROSS STOREFRONTS The search response exposes the substitution explicitly. MZSearch with term=kaiho returns "spellCorrection": "kaiju" on X-Apple-Store-Front 143442 (France), and "kahoot" on 143459 (Switzerland), 143443 (Germany) and 143450 (Italy). Storefronts 143441 (US), 143446 (Belgium), 143455 (Canada) and 143454 (Spain) return no spell correction and do return the app. Measured 2026-08-11. WHY IT MATTERS "Kaiho" is our French trademark (No. 5255039, INPI, classes 9, 41, 42) and the only term under which we ask people to look for us. France is our home market and the source of nearly all our iOS installs. Anyone told to "search for Kaiho on the App Store" lands on monster games instead. I have filed FB24267557 and opened a Developer Support case under Distribution > App Store search and visibility. QUESTION FOR THE COMMUNITY Has anyone managed to get Apple to drop a spell correction on their own brand name? I have seen the same pattern reported for "Myseum" being corrected to "Museum" (thread #780657) with no resolution posted. If you got it fixed, what actually moved it? Feedback Assistant, a support case, Search Ads volume on the exact term, or simply time?

Membership began 1 month ago. I opened 9 tickets. No response received to date from the Support Team. "Before uploading a build of your app to App Store Connect, first create an app record in your App Store Connect account." https://developer.apple.com/help/app-store-connect/create-an-app-record/add-a-new-app

Dear App Review Team, I am writing to escalate our app review, which has now been unresolved for 71 days. App ID: 6705133649 Original submission: 1 June 2026 Current date: 11 August 2026 The specific concern is not only the total duration, but the response time on each individual round. Every time we address a raised issue and resubmit, we wait an extended period for any reply at all: • One resubmission took 12 days to receive a response • Another took 45 days Each reply, when it finally arrived, raised a single new issue rather than a complete list — so we resolve it, resubmit, and the wait begins again. Every one of our previous submissions to this same app was reviewed within 24 to 48 hours. We would genuinely like to understand what has changed. A shift from 48 hours to 45 days on the same app, same account, and same category of build is not something we can explain from our side, and no communication we have received has explained it either. We are requesting: Escalation to a senior member of the App Review team An explanation for why review times on this app have moved from 24–48 hours to 12–45 days per round A consolidated list of every outstanding concern, so we can address all of them in a single resubmission rather than one per cycle Confirmation of whether any account-level hold or flag applies to us An estimated timeline for resolution We have complied fully and promptly with every request made so far and will continue to do so. We can provide demo credentials, a screen recording of the complete user flow, or a call with our engineering team at any time convenient to you. This delay is materially affecting our users and our business, and we would be grateful for your urgent attention. Thank you,

Hello Apple, I'm hoping someone can clarify the expected behaviour here, as I'm not sure whether I've missed a step. Timeline for my first submission (iOS 1.0, new organisation account): 21 July — reviewed 22 July — App Review opened a Guideline 2.1 information request, asking the standard set of questions about third-party analytics, third-party advertising, data sharing and any other data collection 23 July — I replied in the App Store Connect message thread with complete answers to all four questions Since then — status has remained In Review, with no further response That's now 18 days. The submission page shows all 19 items as In Review with no warnings, there are no unread messages in the thread, and the version page has no incomplete metadata flags. My questions: When you reply to a 2.1 information request, does the submission automatically return to the review queue, or does replying alone sometimes leave it in a state where it isn't picked back up? Is a reply in the App Store Connect message thread sufficient, or should the response also be entered in the App Review Notes field on the version? Is there anything that would cause a reply to be recorded but not surfaced to the reviewer? I'd rather understand the mechanism than resubmit blindly and lose my place in the queue. Submission ID: 4cd83c15-8977-4545-a1c4-d4e666d769fc App: 6762837701 (com.travellingintime.TravellingInTime) Thanks.

Hello everyone, I have already released four apps, and I am currently experiencing an issue where the review process appears to be stuck while trying to release my fifth app. The app was rejected several times due to In-App Purchase related issues, and the most recent rejection was on July 15. I submitted the app for review again on July 16, but there was no progress. On July 24, I canceled the existing review submission and submitted it again with the updated version. However, as of today, August 10, the review still has not progressed. I have also contacted Apple Developer Support twice, but I have not received any response at all. Could the review be stuck because I canceled the previously rejected submission and submitted a corrected version again? In addition, I developed another new app and submitted it for review on August 4, but that submission also has not progressed. Could anyone advise me on how I can move the review process forward? Thank you.

how do i get it back? I am the developer of it and for several years it was on the App Store I is my copy and has vast amount of information in it that i value

Hello, I currently have two apps submitted for App Store review, and both have remained in “Waiting for Review” for an unusually long time without moving to “In Review.” In the past, my submissions have generally moved through the review process much faster, so having two separate apps waiting at the same time for this long seems unusual. There are no messages from App Review, no requests for additional information, and as far as I can see, there are no actions required from my side in App Store Connect. Both submissions simply remain in “Waiting for Review.” I’ve also noticed several recent posts from other developers reporting similar delays, so I’m wondering whether there is currently a larger backlog affecting App Review. Has anyone else experienced unusually long review times over the past few days? Is there anything we should do when an app remains in “Waiting for Review” for an extended period, or is it better to simply leave the submissions untouched and wait for the review queue to move? I understand that review times can vary and that the App Review team handles a large number of submissions. I’m mainly concerned that the two submissions may have become stuck in the queue. Any information from Apple or experiences from other developers would be appreciated. Thank you.

Pending Termination Notice Under Section 3.2(f) – Seeking Guidance Regarding Developer Identity Verification Hello, Case ID: 20000132641773 I am seeking guidance regarding a Pending Termination Notice that I recently received under Section 3.2(f) and App Review Guideline 5.6.2 (Developer Identity). I fully respect Apple's policies and have always tried to operate within the App Store guidelines. However, I am struggling to understand the identity-related concerns mentioned in the notice. My Situation I enrolled in the Apple Developer Program as an Individual developer. I completed the standard enrollment process and paid the membership fee. My developer account was approved and activated by Apple. During enrollment, I was not asked to upload a passport, National ID Card, driver's license, or any other identity verification documents. The account has been active for several years. I have multiple published applications and have invested significant resources into their development and growth. My Main Concern The notice states that Apple believes fraudulent or false identity information may have been provided. However: I have never intentionally misrepresented my identity. The name on the account belongs to me. I am fully willing to complete any identity verification process. I can immediately provide my Passport, National ID Card, Driver's License, proof of address, or any other documents Apple may require. Significant Business Impact The termination notice has affected all applications associated with my account. As a result: App transfers are disabled. Earnings payments are paused. Existing applications are impacted. Ongoing user acquisition and marketing campaigns have been disrupted. I have invested heavily in growing these applications, including substantial advertising spend through Meta Ads and other marketing channels. I can provide supporting evidence of advertising activity, installs, traffic, and user acquisition if requested. Questions Has anyone successfully resolved a similar Developer Identity (5.6.2) issue through additional verification? Has Apple allowed developers to submit identity documents after receiving a Pending Termination Notice? Is there any recommended approach when the developer is fully willing to verify their identity but was never previously asked to submit identity documents? I have already submitted an appeal and expressed my willingness to provide any form of identity verification required by Apple. Any guidance from Apple staff or developers who have experienced a similar situation would be greatly appreciated. Thank you.

Hello! After uploading a promotional image for an IAP, it appears broken in App Store Connect. We tested it with another app and encountered the same issue immediately after uploading. Could you please advise what might be causing this and how to fix it?

Hello, I am trying to submit my In-App Purchase subscriptions for review, but App Store Connect is preventing the submission. I have already created: A subscription group ("Piscineiros Pro") Two auto-renewable subscriptions All required metadata and review screenshots When I open the draft submission, I receive the following message: "Unable to Submit for Review. To submit your items for review, add an app version for the selected platform." However, my app version (iOS 4.8.3) already exists in App Store Connect and was previously submitted for review. I would like to understand: Do I need to create a new app version and upload a new binary before I can submit these subscriptions for review? Is it possible to associate the existing subscriptions with the currently rejected app version? What specific steps are required to submit these In-App Purchase products together with my app review? Thank you for your assistance. Best regards, Luiz Maueski

Hello Apple Developer Community, I'm reaching out regarding an urgent matter that requires immediate attention from the App Review team. SITUATION: Our production mutual TLS (mTLS) security certificate expires on August 15, 2026 — only 11 days away. We have submitted version 4.3.1 of our iOS app (Mibanco) which includes the mandatory certificate renewal implementation. WHAT WE'VE DONE: ✅ Implemented dual-certificate coexistence for safe rotation ✅ Tested v4.3.0 thoroughly in TestFlight production ✅ Validated mTLS authentication without errors ✅ Confirmed backward compatibility with legacy systems ✅ Zero user-facing impact OUR REQUEST: We need HIGH PRIORITY review and approval of v4.3.1 before August 15, 2026. This is a critical security infrastructure renewal, not a feature release. Submission ID: b148b754-1abe-451e-b4ac-ad285abbc6da Thank you for your urgent attention to this time-sensitive security matter. Best regards, Alberto Adrian Quineche Poma Engineer Mibanco

We build and operate a management platform for fitness studios — bookings, memberships, payments, class schedules. We're planning the mobile side now and want to get the App Store model right before we build the release pipeline rather than after. What we have One codebase, which we write and maintain. It ships in two configurations from the same source: A marketplace app — every studio on the platform, searchable, with a picker. One binary, one listing, our brand. A per-studio configuration of that same app — identical functionality, with that studio's name, logo and colour palette, pointed at that studio's data. Studios ask for the second because they want their own presence in the store. Each one is a real business: real class schedules, real bookings, real payments taken by that studio, real members using it weekly. What I'm unsure about 4.2.6 Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app's content. I can read that two ways and I'd rather ask than guess: (a) It targets app-builder products, where the customer assembles an app themselves from a toolkit and the vendor's product is app generation. We aren't that — customers never touch a build tool, and the app is our own software that we develop, update and support. (b) It applies to any per-client build regardless, in which case each studio needs its own Apple Developer account and submits with us added to their team. Questions Which reading is right for a SaaS product where the vendor writes and operates the app, and the client supplies business data rather than an app? If per-studio builds can be published under our own developer account, is there anything specific you'd want to see in the submission or the App Review notes to make that clear? Separately from 4.2.6 — what makes per-client apps sufficiently distinct under 4.3? This is the part I'm least sure about, because it reads as a judgement about the pattern across many apps rather than about any one of them, and I'd rather design real differentiation in now than discover the line at app number fifty. Is "same functionality, different business, own branding, own data" enough, or is more expected? Does the aggregated / picker option in 4.2.6 change the answer if we ship it alongside? We're building the marketplace app regardless, so both would exist. Happy to give more detail on the product. I'd rather build the right pipeline once than appeal a rejection later.

Hello Apple Developer Community, I'm reaching out regarding an urgent matter that requires immediate attention from the App Review team. SITUATION: Our production mutual TLS (mTLS) security certificate expires on August 15, 2026 — only 11 days away. We have submitted version 4.3.1 of our iOS app (Mibanco) which includes the mandatory certificate renewal implementation. WHAT WE'VE DONE: ✅ Implemented dual-certificate coexistence for safe rotation ✅ Tested v4.3.1 thoroughly in TestFlight production ✅ Validated mTLS authentication without errors ✅ Confirmed backward compatibility with legacy systems ✅ Zero user-facing impact OUR REQUEST: We need HIGH PRIORITY review and approval of v4.3.1 before August 15, 2026. This is a critical security infrastructure renewal, not a feature release. Submission ID: b148b754-1abe-451e-b4ac-ad285abbc6da Thank you for your urgent attention to this time-sensitive security matter. Best regards, Alberto Adrian Quineche Poma Engineer Mibanco

Hi, Our macOS app has been in Waiting for Review since Jul 24, 2026 with no status change. Platform: macOS Version: 1.0 (1) App Apple ID: 6794145764 Submission ID: 5d04a433-b67d-4801-8578-b1ccc3f22d34 Support case: 20000126982226 We also requested an expedited review and contacted support more than once; no reply so far. Our earlier iOS submission was reviewed within a few days. This macOS one hasn’t moved at all. Is anyone else seeing long macOS “Waiting for Review” times right now? Any advice on getting this unstuck, or can someone from App Review take a look? Thanks.

Hello all! Have open source iOS application. Is it possible to use In-App purchasing (subscription or any other) for donations? Will it be against any kind of Apple rules? The application have no paid content. Just only donations needed. Will it be passing publications checking? This question isn't about using crowd funding or any other kind of platforms. This question about Apple rules exactly.

Hello, our team is currently in the process of adapting our app for UIScene lifecycle and Liquid Glass. When building with Xcode 26 and iOS 27 Simulator, we see the following message in the console: "UIScene life cycle is now required when building with the latest SDKs. Apps that don't adopt will fail to launch." If we build the app with Xcode 27 without scenes implemented, it crashes on launch as expected. To plan our development roadmap, we would like to clarify the following: 1. Behavior of Xcode 26 builds: Can builds created with Xcode 26 (without UIScene support) still be submitted to the App Store, and will they continue to launch without crashing for users updating to future iOS versions? 2. Xcode 26 submission deadline: Until what exact date will Apple continue accepting App Store submissions built with Xcode 26? Thank you for your guidance!

Hi, I submitted Mendo (iOS, version 0.1.0) for App Review on Thursday at 12:39 AM. It’s still Waiting for Review. I had earlier submissions of the same version that I removed myself because I needed to make updates. The current submission is the one I want reviewed. I understood App Review usually takes around 48 hours, but it’s been longer than that for me. Is this delay normal right now, or is there something I should check on my end? Otherwise can I at least get some sort of acknowledgement of some sort to the tickets I've created: - case ID is 20000125052237 case ID is 20000126237735 Thanks.