Hello Apple Developer Community and App Review Team, Please help! Our app is "In Review" status for 4 days on a resubmission. We have requested an expedited review on 30 December because we had a launch with 20k users. My Apple ID: 6745441830 SKU: panduoapp This delay has pushed our planned launch back by over a week, impacting more than 20,000 pre-registered users who are waiting to access the app's core features (AI interactions, community, etc.). My developer had never seen this before and he got a new app submitted yesterday and got approved within 3 hours. Is this level of "In Review" time common right now during the post-holiday period? We've seen quick reviews on other similar apps recently, so wondering if this might be stuck or require a nudge. Any advice on next steps (beyond Resolution Center inquiry) or similar experiences? We've double-checked build attachment, IAP config, paywall links, and reviewer notes (including demo access). Thank you!

Hello everyone, I am facing a recurring issue with my app review and looking for advice. The Situation: I originally submitted a build last week and it sat in "Waiting for Review" for 7 days with no movement. Assuming it was a glitch, I removed that build and resubmitted this past Saturday (Jan 3). It is now Tuesday, and the new build is also stuck in "Waiting for Review" (no reviewer has picked it up yet). This is an update to an existing app. We have checked the Resolution Center and our email, but there are no messages or requests for more information from the App Review team. Has anyone else experienced similar delays recently? If an Apple staff member sees this, could you please check if there is an issue with the queue for this specific build? Thank you!

Our app have been waiting for a review for a whole day. We need this as soon as possible since it has a huge effect on our users' expereice. https://apps.apple.com/us/app/ziina-pay-get-paid-instantly/id1507246381

Hello, "This issue is blocking App store approval" I have tried pushing my application to Appstore. However it has been rejected on the following ground: _"As we discussed, the app uses or references the following non-public or deprecated APIs: Frameworks/CommonLibrary.framework/CommonLibrary Symbols: • _SecCertificateIsValid The use of non-public or deprecated APIs is not permitted, as they can lead to a poor user experience should these APIs change and are otherwise not supported on Apple platforms."_ I have scanned the app using "strings" tool & "otool -ov" tool. But they have come out clean. No Non-public or deprecated APIs detected. Please advise which tool can be used to scan the CL to locate where the deprecated API or non-public API lies and also how to rectify the same. Thanks Saikat Bakshi.

Hi everyone, I'm having a frustrating issue with in-app purchases on 2 of my apps, and despite following all the steps correctly, they're getting rejected during App Store review because the products screen doesn't load for reviewers. I could really use some help figuring out what I'm missing. What I've Done (Following Apple's Documentation) Created products in App Store Connect: Added each in-app purchase individually with correct Product IDs These IDs match exactly the ones in my .storekit file Filled out all required information: translations, pricing, descriptions Everything was filled correctly Submitted products for review: Each product went through the separate review process All products were approved individually Linked the approved products to my app build App submission: Uploaded new build with in-app purchases implemented Products are properly configured in the app code Used StoreKit for testing (products load correctly in sandbox) The Problem Even after all products are approved and linked to the build, reviewers are reporting that the products screen shows nothing - the products array appears to be empty for them. Since this is my first time submitting apps to the App Store, I feel like I'm missing some crucial step in the process. Apple's documentation seems scattered and not clear enough about the complete workflow. Questions: Do I need to do something special after products are approved but before submitting the app? Are there any additional configurations needed in App Store Connect? Is there a definitive step-by-step guide for the complete in-app purchase submission process? Does anyone have experience with this issue or know of clear documentation that explains the complete in-app purchase workflow from creation to app approval? Any help or pointers to proper documentation would be greatly appreciated!

Hi, I am in need of your help with publishing my game. I got the following explanation for the negative review of my app/game. Issue Description One or more purpose strings in the app do not sufficiently explain the use of protected resources. Purpose strings must clearly and completely describe the app's use of data and, in most cases, provide an example of how the data will be used. Next Steps Update the local network information purpose string to explain how the app will use the requested information and provide a specific example of how the data will be used. See the attached screenshot. Resources Purpose strings must clearly describe how an app uses the ability, data, or resource. The following are hypothetical examples of unclear purpose strings that would not pass review: "App would like to access your Contacts" "App needs microphone access" See examples of helpful, informative purpose strings. The problem is that they say my app asks to allow my app to find devices on local networks. And that this needs more explanation in the purpose strings. Totally valid to ask, but the problem is my app doesn't need local access to devices, and there shouldn't be code that asks this?? FYI the game is build with Unity. Would love some help on how to turn this off so that my app can get published.

inapp purchase product has been in review for more than 24 hours, although we have another product that was submited for review after the first one and it has been approved already

New developer here. Does removing your app from review(to change the build or any other reason), and resubmitting it, reset you to the back of the line? I‘ve done this multiple times, and I have users asking me when the updates are coming.

2026 confirmed that ASO has evolved beyond keywords into a full funnel system where creatives, conversion rate, app quality, retention, and ads drive visibility. Organic growth now comes mainly from Explore and Browse, with algorithms rewarding strong visuals and product health over simple metadata changes.

As an indie iOS dev, ASO often feels frustrating and unpredictable. Any proven tips, or is it just a grind we all face.

Requesting you all any recommendations for iOS ASO tools covering keyword research, metadata optimisation, competitor tracking, and A/B testing.

Hi everyone, my name is Donovan, I am sharing here the official response I received from Apple following my appeal with App Review Board (image attached). For context, I am an independent developer and a student, working alone. This application was originally created as a student project, with a very simple goal: to improve my skills in mobile application development and to understand the entire creation cycle, from the initial idea to a genuinely usable application. What was meant to be an exercise gradually became a real product. Over time, many people tested the project, used it, provided positive feedback, and encouraged me to take it all the way. That is why I decided to continue it, structure it properly, and finalize it with the level of seriousness expected from a public-facing application. Today, the application is a dating and social connection app, entirely free, with no blocking paid features, funded only by light and optional advertising. It follows the rules, works correctly, and offers features that Apple itself acknowledged as useful and informative. And yet, after review, the message is clear: it is not the quality that is being questioned, but the category. Because it is a dating app, a category considered saturated, two years of independent, self-funded work, carried out seriously and in compliance with the rules, can simply be dismissed. What is being judged here is not the work itself. It is the right to enter. The “unique and very high-quality experience” being required appears to be a threshold reserved for those who are already established, visible, or funded. For a serious student project carried by a single developer, the door remains closed, cleanly, politely, definitively. For those who still wish to see what the application looks like, I have attached a few images illustrating the interface and the main features. Unfortunately, this will likely be the only way to discover it on iOS. Under these conditions, the conclusion is pragmatic. Rather than continuing to defend the very existence of an honest and free project, it becomes more coherent to invest my energy where it is genuinely accepted. On its side, Android validated the project without difficulty. It still allows an independent developer to propose an idea, let it evolve, and bring it to completion without requiring prior success just to earn the right to try. It is therefore very likely that these two years of development will never make it to the App Store. Not out of frustration. Out of clarity. I am publishing this message not to provoke, but to inform other independent developers: Apple is a remarkable platform, provided you are already established on it. And this is a reality worth knowing before turning a student project into a life project. Screenshots:

We are planning to migrate our application from an iOS In‑App Purchase (IAP) subscription flow to an external web purchase flow. The intended user journey is: The user taps a “Subscribe” button in the app. The user is redirected to a web-based checkout to complete the purchase. The user returns to the app, and subscription access is unlocked based on entitlement verification from our backend. Our app is currently listed in the Education category. Before we begin this refactor, we would like confirmation on the following: Entitlements / permissions Do we need to request any specific Apple entitlements or approvals to implement this external purchase flow (e.g., external link or alternative payment related permissions)? Compliance / review requirements Are there any specific App Review compliance checks, disclosures, or review process requirements we must satisfy when moving from IAP to an external purchase flow? If relevant, are there constraints based on app category (Education) or product type (subscription)?

I understand that private APIs are not permitted under Apple’s App Review Guidelines. However, our application requires I²C communication, and we are currently considering the following APIs: IOAVServiceReadI2C IOAVServiceWriteI2C IOI2CSendRequest Could you please confirm: Is there any provision to use these APIs in a Mac App Store–approved application? Are there public alternatives available for achieving I²C communication on macOS? Thank you for your guidance.

There’s still debate on what drives App Store rankings, but some confirmed factors include app name, subtitle, keyword field, downloads, ratings, and in-app events. Likely influences are stability, retention, conversion rate, and user behavior. Search relies most on metadata, Top Charts focus on download velocity, and Featured spots are editorially chosen. Elements like promo text, long description, and release notes don’t impact rankings.

I’m trying to clarify keyword usage in App Store Optimization. Apple’s docs suggest you can use phrases like “Near Me” instead of separating words with commas (“Near,Me”). Does assigning phrases directly improve ranking compared to letting Apple combine single keywords?

Hello, I am new application developer that has been developing several applications in the productivity and finance sections concurrently for about 1 year. One of my applications is nearly ready to be submitted to the App Store. I have received a lot of discouragement from people who have submitted apps in regards to putting submitting as a paid app, however due to all of the upfront and ongoing investment I've made, I do not wish to release my application for free initially. (I am learning how to best integrate storekit and in-app purchases and subscriptions, but I'm not ready to implement that yet) QUESTION: When releasing an app as a paid app and then converting to a FREE app with subscription later on, is there anything I need to be aware of technically or in regards to guidelines so I don't shoot myself in the foot when changing pricing? Any advice is greatly appreciated. Thank you.

I want to publish my game next year in the Apple App Store but I want to choose the time period manually. Can I upload my game for app review without releasing it automatically afterwards? Where exactly can I choose in App Store Connect if my game is published automatically or manually after the app review process? Currently I only use TestFlight.

I'm an algo engineer-turned-entrepreneur. About two months ago, I signed up for the Apple Developer Program. Last month, I launched an AI avatar video calling app called Twome (pronounced "Two-me") on the App Store. But just a few days after launch, I used EAS Update (a React Native tool for hot updates) to push a quick bug fix, and soon after, I got hit with a "Pending Termination Notice." They said I violated the Apple Developer Agreement—my app got pulled, and my developer account was flagged for removal. (The App Review message was pretty vague: "App submissions from your account have engaged in concept or feature switch schemes to evade the review process." I'm guessing that's what triggered it.) I was totally shocked. I'd done my homework beforehand and seen tons of devs saying hot updates for bug fixes were fine. No choice but to appeal, so I filed one right away on the App Review Board. Then came the real nightmare: 28 whole days later, I finally got a response—and they upheld the rejection. The reasoning was even fuzzier this time; it felt like a copy-paste template. No specific evidence like before (at least the first notice had some details). Maybe they realized our update didn't actually change any features? Anyway, I'm trying another appeal now, but who knows when it'll come back. The waiting is brutal. We did a full internal audit and pinpointed just two things that might've raised red flags with App Review: Post-launch, we tested an unreleased "rate us" feature and posted a review using our developer account. We figured the App Store would know it was from the app owner and auto-remove it from public view. It was our only review, and we didn't think it'd count as misleading since Apple handles that stuff. The bug fix hot update I mentioned. Beyond that, our post-mortem showed zero other issues. All metadata, product descriptions, and screenshots are 100% compliant—no misleading claims, no dark patterns pushing payments, nothing. Before launch, friends were hyped, saying it'd blow up—it's the world's first realistic AI digital human real-time video calling app for everyday social/entertainment use, aimed at regular folks. But now we're tied up in knots with this appeal mess, desperate to get back on the Store ASAP. It's insane that appeals take a full month to get a response—especially when we didn't blatantly violate anything, or at worst, tripped over something unintentionally. We've already been down for over a month without even knowing the exact issue. Feels way too harsh. Posting here to ask: Has anyone dealt with something similar? Is a 28-day wait (or more) normal for appeals? Any ways to expedite the process? Any practical advice would be hugely appreciated!

Hello, My app (App ID: 1616628950) is currently in the Waiting for Review state after resubmission. The app was resubmitted on December 24 following a previous rejection related to in-app purchase labeling. The issue has been addressed, and the updated build was submitted accordingly. Normally, our app updates enter review within 1–2 days, so this delay seems slightly unusual. I understand that review times may vary, especially during the holiday period, but I wanted to check in here in case the submission might be stuck or require additional information from our side. There were no major functional or policy-related changes in this update aside from addressing the previously noted issue. Thank you very much for your time and assistance.