Hi everyone, I’m currently stuck with a blocking issue in App Store Connect and would really appreciate any guidance or insight. Issue: My app version (iOS App 1.0) is missing the “In-App Purchases and Subscriptions” section entirely. Because of this, I cannot attach my subscriptions to the version, which is preventing me from submitting the app for review. Additionally, I also do not have the option to create a new version, so I can’t work around the issue by moving to 1.0.1. What happened before this: I uploaded a build (Build 24) Submitted the app for review Then removed the submission After that, the IAP section disappeared completely Since then, I cannot attach subscriptions or create a new version Current state: Subscriptions are created and show “Waiting for Review” New Build is attached to Version 1.0 All metadata and screenshots are complete “In-App Purchases and Subscriptions” section is missing “Add Version” option is not available What I’ve tried: Removing and re-adding the build Waiting for UI refresh/processing Contacting Apple Developer Support (case has been escalated for 6 days with no response) Impact: This is currently blocking my app launch because I would be rejected since the subscriptions are not linked, as I cannot submit my first subscription with the app. Questions: Has anyone experienced a missing IAP section after removing a submission? Is there any way to force reset the app version state from the developer side? Is this a known App Store Connect issue? Any help or suggestions would be greatly appreciated. Thanks in advance.

Hello, I have a blocking issue in App Store Connect. I need to submit my In-App Purchase together with the app (first-time approval), but: The option to attach In-App Purchases is missing I cannot create a new app version I cannot properly edit the current version This creates a deadlock and prevents me from submitting the app correctly. This does not seem like a configuration issue, but a problem in App Store Connect. Has anyone experienced this or knows how to resolve it? Thank you.

My external TestFlight build for Reverie: Climbing Journal (iOS, build 1.0.0 (7)) was submitted for review on Thursday 2nd July at approximately 00:10 BST. It has now been 5 days with no movement — still showing "Waiting for Review." I have raised 4 support tickets including an expedited review request (case ID 102932291414) and have received no response to any of them. There is no option to get a call back or call and speak to an actual person. A separate app on the same developer account (Get Set) was submitted for external TestFlight review several days later and was approved within 24 hours, so this appears to be specific to this submission rather than a general account issue. I have testers waiting and this is causing significant disruption. Is there anything I can do to progress this, or can anyone from Apple advise on what's happening?

Our application (Apple ID: 6762377822) has been stuck in the Waiting for Review status for more than 5 days. We submitted an expedited review request, but have not yet received a response. We are currently under significant time pressure. We sincerely hope the expedited review request can help facilitate the process and move the review forward as soon as possible. Thank you for your attention and assistance.

Hi everyone, I’m facing an issue with the App Store review / support process and would really appreciate some guidance from others who may have experienced something similar. I have contacted Apple Developer Support multiple times regarding my app, but unfortunately I have not received any meaningful response so far. At this point, I am unsure how to move forward or how to get proper feedback to resolve the issue. The lack of response is making it difficult to proceed with my app submission and address any potential problems on Apple’s side. Has anyone encountered a similar situation? How did you successfully escalate the issue? Is there a specific way to get a response from the review team or developer support? Any advice on how to move forward would be highly appreciated. Thank you in advance!

Hello, my app id 6756081224 Waiting for Review 10 day ago Help me please

Hello, My app update has been stuck in the review process for much longer than expected. Here's my current situation: The app update I submitted has been in "Waiting for Review" for longer than the usual 48 hour timeframe, with no progress. I submitted an expedited review request after the 48 hours of submitting but have received no response as of yet. Has anyone else encountered this issue? And what should I do? Thank you.

My app has been stuck in “Waiting for Review” since June 23, 2026. It has now been 10 days without moving to “In Review.” I have already contacted App Review through App Review Status, but I have not received an update yet. I also checked App Store Connect and do not see any missing metadata, Resolution Center messages, App Privacy issues, Age Rating issues, Export Compliance issues, or missing Review Notes. Is anyone else currently experiencing unusually long “Waiting for Review” times? Also, is there anything else I should check on my side before contacting App Review again?

Hello everyone. I hope the Apple team sees my message. I submitted my app for review on June 15th. It's been in the "Waiting for Review" status since then. The app doesn't have any complex structures. No authorization (except for GameCenter), no encryption, etc. It's written in Swift, the native language, and is iOS-exclusive. I've contacted support three times, submitted a request for expedited review, and responded to the emails that arrived confirming my request, but there's been no response, even though the messages indicated a response within 24-48 hours. Apps are successfully submitted to the testing environment. I feel like I'm being ignored. Please help, I'm really looking forward to the App Store release due to the planned events. If anyone has had a similar situation, please share what helped and how long it took for your app to be reviewed, so I can understand how much longer I need to wait.

I have been rejected twice under Guideline 2.1(b) because my In-App Purchase subscriptions are not submitted for review. I cannot figure out how to attach them to my submission. Here is my situation: I have 6 auto-renewable subscriptions fully configured in App Store Connect under "Barrel Pro Subscriptions" — all have screenshots, pricing, descriptions, and review notes My app is iOS only, built with React Native/Expo My current version is 1.1, Build 10 (1.1.0) The problem: The "In-App Purchases and Subscriptions" section does not appear anywhere on my version page. I have scrolled to the very bottom and it is not there. I cannot find any way to attach my subscriptions to my submission before clicking "Submit for Review." The blue info box on the Subscriptions page says: "Your first subscription must be submitted with a new app version. Select it from the app's In-App Purchases and Subscriptions section on the version page." But that section does not exist on my version page. What I have tried: Cancelling the rejected submission and starting fresh Creating a new version (1.1) manually Uploading a new build (Build 10) Checking both "In-App Purchases" and "Subscriptions" sections in the sidebar Has Apple removed this section from the version page? How do I attach my subscriptions to my submission in 2026? Any help is greatly appreciated. Thank you.

I'm hoping someone here has navigated something similar or can point me to the right channel. My Apple Developer Program membership was terminated, with the notice citing Section 3.2(f) of the ADP Agreement and referring to indications of fraudulent conduct. No specific reason was given. As far as I can tell, the only significant change to my account beforehand was updating my country/region after I relocated. I did this openly through Developer Support: I disclosed the change, Apple asked me to verify my new address, I uploaded a government-accepted document, and a Developer Support agent confirmed Apple had reviewed it and updated my account so I could renew. So the location details on my account are accurate and were verified by Apple itself - which is why the "misrepresentation" framing is confusing to me. Two questions: What is the correct channel to formally appeal or request a review of an account termination? The "file a complaint under a Platform Regulation" link is not available in my region, and the general contact forms do not seem built for this. Has anyone here gone through a 3.2(f) termination and had it reviewed or reversed? What actually worked - phone support, a specific form, persistence? I'm trying to resolve this factually and in good faith. Any guidance is appreciated.

How long the paid apps agreement takes ? im not sure what's going on, I have all active my bank account etc, I added well all the products etc, but still says processing, I ask for help, and no one hasn't answer anything yet, I look on YouTube I didn't find anything, I ask Ai and just says I need to fking wait !! im so tired of waiting desperate also bc I worked so much on this and is crazy that noe apple is taking so much time not sure if this is real or what's going on!!

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.

Hello everyone, I would really appreciate some advice regarding an App Review rejection under Guideline 1.2 because I’m unsure what the best next step is. The review notes included the following statement: “Since this app’s primary functionality is not permitted on the App Store, it would be appropriate to submit a new app with functionality that follows the App Review Guidelines. Resubmitting the app will result in the same or additional App Review Guideline violations.” This wording makes me unsure whether I should submit a new build with the changes I have made or continue discussing the issue through the Resolution Center. The app was rejected because App Review considered its primary purpose to be random or anonymous chat. However, I believe there may have been a misunderstanding about how the application actually works. The application is not a private messaging app, nor is it designed to let people freely chat with strangers. The concept is closer to a discussion that takes place on a user’s profile, similar to two people having a conversation in the comments section of a social media platform. Other authorized users can read those conversations and react to individual messages, so the conversation itself becomes the content rather than functioning as a traditional direct message. Users are never anonymous. Every account has a persistent identity, including a username, profile picture, verified email address, and profile information. The application also includes reporting, blocking, restricting, and moderation features. Communication is intentionally very limited. Users cannot simply message another user whenever they want. Even after all other requirements are met, a user can send only one initial message. The recipient then has 24 hours to decide whether to reply. If the recipient chooses not to reply, the conversation never begins, the thread is automatically moved to the archive after 24 hours, and the sender cannot continue contacting that user. They cannot send another initial message or repeatedly attempt to start a conversation. A conversation can only continue if the recipient voluntarily chooses to reply. Originally, every account was private by default, although users could choose to make their profile public. During App Review, I temporarily made the review accounts public because I wanted the reviewer to be able to explore the application more easily without needing multiple test accounts. Looking back, I now believe this may have unintentionally made the application appear much closer to a stranger chat experience than it was actually designed to be. Another detail that may not have been visible during review is that the reviewer reached the message composition screen but did not actually submit a message. (I saw it on screenshots they attached) If they had submitted it, they would have seen that the initial message does not immediately become an active conversation. Instead, it first enters a pending state where the recipient decides whether to accept it by replying. Without the recipient’s voluntary participation, no conversation is created. After receiving the rejection, I decided to redesign this part of the application to make the communication model even more restrictive. I completely removed the ability for users to have public profiles. Every account is now permanently private. Before any interaction is possible, a user must first send a follow request, and the recipient must explicitly accept that request. Without an accepted follow request, it is impossible to send the initial message. I also removed the discovery feature that could resemble random user discovery and replaced it with standard user recommendation cards similar to those used by many social networking applications. In addition, I implemented follow request rate limiting so users cannot rapidly send large numbers of follow requests. As a result, users can now interact only after mutual consent has already been established through an accepted follow request, and even then, communication is still limited to a single initial message that requires the recipient’s voluntary reply before any conversation can exist. My question is this: Given these changes, would you recommend submitting a new build for review despite the statement that “Resubmitting the app will result in the same or additional App Review Guideline violations,” or would it be better to continue discussing the issue through the Resolution Center first? (Some why they don't reply me at all) If anyone has dealt with a similar Guideline 1.2 situation, I would sincerely appreciate your advice on how you would proceed. Thank you very much for your time

How can Apple deny my appeal and not approve my app for tobacco when multiple apps like these are on the store?

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.

Hello, I recently received a Pending Account Termination Notice for my Apple Developer Program account. The notice refers to section 3.2(f) of the Apple Developer Program License Agreement and says the account may have been involved in dishonest or fraudulent activity, including possible concept or feature switching after review. I have already submitted an appeal to the App Review Board. The difficult part is that the notice does not mention a specific app, bundle ID, version, or behavior. I have multiple apps under the account, so I am trying to identify what may have caused the issue. During my review, I found one possible area: one app uses different API server endpoints depending on the user’s IP region or network location. This was only done to improve connection speed and reliability. For example, overseas users may connect to an overseas server because access to Mainland China servers can be slow or unstable. The app is not intended to show different features, menus, content, or user flows across those servers. The server routing only changes the API endpoint for performance reasons. It is not used to detect App Review users or hide any functionality. I also have several other apps under the same developer account. These apps were previously reviewed and approved through the normal App Review process, and I did not intentionally implement any mechanism to mislead App Review, hide features, or change the app concept after approval. Because the notice applies at the account level but does not identify a specific app, bundle ID, version, or behavior, I am having difficulty understanding what exactly triggered this enforcement action. I am willing to review and correct any issue, but I need to understand whether the concern is related to regional server routing, a specific app implementation, App Store metadata, server-side configuration, or something else. My questions are: Can regional API routing based on IP or network location be misunderstood as dynamic content or feature switching after review? What kind of documentation or evidence is most helpful to provide in an appeal to show that different server endpoints provide the same app experience? Should I provide side-by-side API responses, backend configuration screenshots, and screen recordings from different regions? If the termination notice does not identify a specific app, is there any way to request clarification about the app, bundle ID, version, or behavior that caused the concern? Is there any recommended way to document multiple apps in an appeal when the notice is account-level rather than app-specific? I understand that nobody here can make a decision on my account. I am only looking for general advice on how to clearly explain this type of server routing, how to review multiple apps under the account, and what evidence is usually useful. Thank you.

Hi everyone, I want to start by saying that I genuinely appreciate the work Apple’s reviewers, support teams, engineers, and testers do. The volume and variety of apps they have to evaluate must be enormous, and I understand why Apple has to be careful about protecting users and the App Store from deceptive or unsafe apps. I’m posting because I’m looking for guidance from anyone who has navigated a Pending Account Termination appeal. This is for my first iOS app submission. The app is a location-based social planning app for adults to create and join nearby plans. It is a real product, not a template/spam app, and I have been trying to make review as straightforward as possible. Timeline: Submitted / Ready for Review: June 10, 2026 In Review: June 15, 2026 I also had a TestFlight external testing review delayed for about a week I submitted support requests and an expedited review request, but did not receive any responses 19 days after submission, I received a Pending Account Termination notice alleging dishonest or fraudulent activity under the Developer Program License Agreement I have submitted an appeal to the App Review Board. The web page confirmed receipt, but I did not receive a separate email or appeal case ID. I also opened a Developer Support case just to confirm the appeal is in the queue. I want to be very clear: the app is honest and there was no intent to evade App Review. Because the app depends on nearby user-generated plans, I had created demo/test data and a review account so reviewers would not see an empty app in a location with no users. After TestFlight external testing was approved and before sharing the public link with real testers, I removed the synthetic test/demo data so production would contain real user activity only. I have already taken corrective steps: Removed automatic review/demo reseeding behavior from the backend Removed synthetic demo users and content related to them from production Current production data is real user data only I understand Apple has to protect users and the App Store from deceptive apps, spam, and fraud, and I appreciate how difficult that job must be at scale. I’m trying to handle this carefully and respectfully. For anyone who has been through a Pending Account Termination appeal: Is it normal not to receive an appeal case ID by email? How long did the App Review Board take to respond? Is there any appropriate way to provide clarifying information after submitting the appeal, or should I wait for Apple to reply? Thank you for any guidance.

Hello, Our app, Cloudkeep Rivals, was rejected under Guideline 4.3(a) - Design - Spam. The App Review message says that the app appears to share a similar binary, metadata, and/or concept with apps previously submitted by a terminated Apple Developer Program account. The reviewed version was 1.0 (202606172035), with review date June 25, 2026, and Submission ID a03a3146-51b2-4440-967b-2326018fb06b. We are trying to understand what exactly triggered this rejection. We have asked App Review several times whether the issue is related to the build/binary, metadata, the game concept, similar heroes/characters, or a possible association with a terminated account. Unfortunately, the replies we receive appear to be mostly the same copy-pasted message, without any specific clarification about which part of the app is considered problematic or what exactly we need to change. We also tried to use the Contact Us / support channels, but we have not received a meaningful response to our support messages or emails. We have now been waiting for about one month without a clear answer. Has anyone experienced a similar Guideline 4.3(a) rejection and managed to resolve it? Is there any effective way to get a more specific explanation from App Review or reach the correct escalation path? We are not trying to flood support or dispute blindly. We simply want to understand the exact issue so we can either fix the problematic part or provide the correct explanation/evidence. Thank you.

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