Responding to reviews helps ASO because it encourages better user sentiment, improves rating recovery, and builds trust for new users checking your app. Converting negative reviews into positive ones has a strong impact on ranking. Engaging consistently with users is one of the simplest ways to strengthen overall ASO performance.

My account has been active and in good standing for the past 2 years, and during this time I have never received any warnings or issues. Recently, after Apple reviewed my account, I received a notification about possible termination. After carefully reviewing the situation myself, I realized what may have caused this: I originally registered my Apple Developer account as an Individual Developer Account, However, the bank account used for App Store payments belongs to my registered company, At the time, I was not aware that the legal entity of the bank account must match the Apple Developer account registration. This was not done with any intention to misrepresent or misuse the platform. It was simply a misunderstanding of the account requirements. We have never deceived our users or the Apple Review Team in any way. For us as developers, providing an excellent user experience has always been our top priority, and we have always aimed to follow Apple’s review and compliance standards closely. We sincerely hope that, given our situation, the Apple Review Team could grant us an opportunity to correct these issues.

Hello I am trying to release an app, dealing with storing, delivering, and maintaining outdoor activity euqipememts. On web, I used widget provided by TOSS, which is a Korean banking application. Due to lack of time I have use lazy method User taps the “Pay” button ↓ Backend generates a payment URL (Toss Payments) ↓ Open the payment page in an external browser (Safari) ↓ User completes the payment in Safari ↓ Return to the app via deep link (borini://payment/success) ↓ Call the payment approval API ↓ Display the payment completion page I have hear such method is possible for our type of service which deals with real life goods. So I would love to know if it is actually possible or will I have to make a new payment method using apple provided payment method in order to pass APP Store Connect review before releasing application

I developed a mobile game which is a shooter/endless waves type of game. I submitted a few months ago and got rejected under guideline 4.3.0 -design spam. I went and redesigned the while thing, ADDED A COMPLETE MULTIPLAYER functionality where you can battle other real players. Submitted it again last Friday, week ago. Got the same rejection reason 4.3.0 - design spam. After explaining the features I added they wrote me back saying that the issue is resolved and then rejected due to some technical error I did when filling out the age rating settings. Fixed that and AGAIN they rejected under guideline 4.3.0 - design spam!! Even after attaching them a screenshot of the message that CLEARLY shows they resolved that issue, they keep on rejecting under 4.3.0 it’s like they are not even looking at the screenshot, or even looking in the message history. Does this make any sense to anyone? That 2 days ago they said 4.3.0 was resolved, then not? the app was developed entirely from scratch, no free assets, no templates, I have adobe files to prove it. please advise, I am loosing my mind.

Can multiple apps be published under the same organization that use the same logo and the same app name, but are intended for different regions? Each app will target a specific country or region, and the core functionality will be similar. I could not find any specific App Store Review Guideline stating whether it is allowed to have the same app name and branding for different regional versions. Is it necessary to differentiate the branding or name for each regional version to get approval during App Review?

Its been 4 days now and apparently it is unusual for it to take more than 48 hour? Any advice on who to contact to get this looked at?

Need Clarification on Pending Termination Notice for “Ethereum Cloud Miner Sim” App Hello Apple Developer Community, My developer account recently received a Pending Termination Notice, stating that my account may have been used for dishonest or fraudulent activity. I am very concerned and would like clear guidance on how to properly resolve this situation. My app is “Ethereum Cloud Miner Sim”, which is a simulation-only app, not real mining. To avoid misunderstanding, I clearly included: “Sim” in the app name A full disclaimer in the description No external payments, no misleading claims, no incentives, and no financial functionality Despite this, the app was removed and my account received the termination warning. I want to understand: What specific part of my app or metadata was interpreted as dishonest or fraudulent? How can I correct the issue so my account is not terminated? Is there any additional clarification or documentation I should provide? Does Apple consider simulation apps (non-functional mining simulations) as violating Guideline 5.6? My intention has always been to follow Apple's guidelines carefully, and I am ready to make any changes required. I kindly request direction from Apple or anyone in the community who has experienced a similar issue. Thank you for your time and guidance.

Hello everyone, I hope you are all doing well. I’m opening this discussion because we’ve encountered a repeated Guideline 4.3 rejection for an update, despite having previously addressed the same concern with the App Review team and reaching a resolution. Several weeks ago, we went through a detailed review process regarding Guideline 4.3. We provided full technical explanations, clarified our development structure, redesigned parts of the UI, and made all adjustments requested by the App Review team. That update was ultimately approved, and the app has been live on the App Store since then without any issues. However, our new submission—which includes only a critical bug fix—is now being rejected again for the same 4.3 reason. No changes have been made to the concept, design, or core functionality since the previously approved version. The update is not introducing new features or new UI; it simply resolves a performance bug affecting downloads and uploads, which users are already experiencing in the live version. We operate a single developer account, and our apps are entirely built in-house. Although we use open-source VPN cores (such as Xray-core and Clash), these frameworks are publicly available on GitHub and are commonly used by many developers. Our implementations, configurations, and UI are fully custom and not shared with any other apps. This was already reviewed and confirmed in our previous submission. We have already sent clear and detailed technical explanations through the Resolution Center—similar to what was accepted in our earlier approval—but unfortunately, it hasn’t resolved the issue this time. This situation is becoming difficult for us because: The current live version has a performance bug that users are already affected by. We are in the middle of ongoing campaigns, meaning delays can lead to financial impact. Negative user feedback due to this unresolved bug could permanently damage the app’s reputation. Since this exact concern was previously reviewed, discussed, and resolved with App Review, we are unsure why the same guideline is suddenly being applied to a simple bug-fix update. So I wanted to ask the community: Has anyone faced a similar situation where a previously resolved 4.3 issue resurfaced on later updates? Are there any specific details or approaches that helped clarify the situation for the review team? Is there anything additional we should highlight to prevent misunderstanding on automated or manual review? Any insights or shared experiences from other developers would be extremely valuable. Thank you in advance for your time and support.

Our app was just rejected by Apple because they say the subscription management sheet never loads. It just spins indefinitely. We're using StoreKit's manageSubscriptionsSheet view modifier to present the sheet, and it's always worked for us when testing in SandBox. Has anyone else had this problem? Given that it's Apple's own code that got us rejected, what's our path forward?

Consistent user signals are more important than metadata; they promote favourable reviews, strong retention, and frequent updates to improve ranking. To determine what actually converts on your App Store product page, combine these with A/B testing.

Our app (app1) was recently transferred from Team A to Team B. While reviewing the Apple login implementation, we discovered that "Sign in with Apple" had been incorrectly set up to use the Service ID and App ID of another app (app2) — specifically, it was using app2.service as the Service ID and app2 as the App ID. In other words, app1’s users were authenticated through app2’s credentials due to a misconfiguration on our part. Now that app1 has been transferred to Team B, we’re trying to preserve those users. However, app2 is still in Team A, and we cannot maintain Team A anymore — meaning app2 must also be transferred to Team B if we want to retain access to the user data. One idea we considered is submitting app2 for App Review (even though it's non-functional) just to fulfill the transfer requirements, and then transferring it to Team B solely to retain the Apple login setup. Is this approach acceptable? Are there any recommended ways to handle this kind of misconfiguration while preserving existing Sign in with Apple users?

Hi everyone, I submitted an appeal to the App Review Board over 14 days ago, but I still haven’t received any update or acknowledgment. I’m now at a standstill, as this delay is blocking my app release and preventing me from moving forward. Is there a typical timeframe for ARB responses? And is there any recommended way to follow up or get the appeal looked at? Any insight from others who’ve been through the process would be appreciated. Thanks.

Hello, everyone! I encountered problems during the application review process. My app has been in the "Waiting for Review" state for over one week, while usually the review process is completed within 12 hours. And currently, there is no update of any information, and it is unknown what kind of problem has hindered it. Has anyone else experienced such a delay recently? Any suggestions on how to speed up the process or upgrade issues with Apple would be greatly appreciated.

Hi! My app was rejected on Nov 4 due to 4.3 Design Spam. After communicating with the App Review team on Nov 4, the decision was still the same, so I submitted an appeal to the App Review Board that day. They mentioned there are apps that are providing the same functionalities but I have done my research on App Store and reached out to potential users in London to gauge the interest. I believe my app and its direction is unique. I still haven’t received any update and I totally understand that the appeals process can take some time. It's just that I am really passionate about getting this app into the public to get people on it and I have no idea on what is wrong and how I can help make it right. Does anyone know how long it usually takes to get a response from the App Review Board? Thank you for any help!

Hello everyone, quick question. I have an app with subscriptions that limit some functionality until you subscribe. The app detects if you have an active subscription and if you do not, when choosing a functionality that is behind the paywall, you get redirected to the upgrade screen where the subscriptions are located. The reviewer replied "We have started the review of your app, but we are not able to continue because we cannot locate the in-app purchases. To help us proceed with the review of your app, please reply to this message providing the steps for locating the in-app purchases in your app." I think the issue is that the app was tested before by the review team with a sandbox account, and now the app is not displaying that upgrade screen anymore because it detects that sandbox account as having an active subscription. And now the reviewer can't get to that screen anymore. Has anyone encountered this type of issue in the past? If you erase purchase history from that particular sandbox account, you log out and log back into the sandbox account it works, but I'm not sure if the reviewers do that.

Start by refining your metadata with keyword-rich titles, subtitles, and descriptions that match user intent. Use high-quality screenshots, app previews, and localized content to improve visibility. Focus on user engagement through regular updates, positive reviews, and consistent installs. Higher retention and active user signals naturally help your app climb the App Store rankings.

I can't pass rule 4.3b. I'm practicing horoscope. How do you think I should proceed? Is it possible to publish this application?

Dear App Review Team, Our app – Apple ID 6749515097 has been stuck in the “Waiting for Review” status for more than 1 month (since October 14, 2025). Normally, reviews begin within a few days, but in our case, it seems unusually delayed. Could you please investigate and help with this. Thank you very much for your time and assistance.

Hello, I first submitted my app on September 14, and it has been stuck in the “Waiting for Review” status for almost three months now. This is the first version of the app, and it has never been reviewed before. I’ve already contacted Apple via email, but I only received the standard response stating that everything is fine. Is there anything else I can do? Thanks!

Hello, Our app was rejected under App Store Review Guideline 1.4.1 for providing “medical-related data, health-related measurements, diagnoses or treatment advice without appropriate regulatory clearance.” However, the features in question are not intended for medical use, and we have already: Added clear disclaimers that the feature is wellness-only, Explicitly stated it is not clinically validated, Indicated that it is not intended for diagnoses or medical purposes, Avoid all medical wording in UI, Added references similar to other wellness apps (e.g., breathing, stress, HRV-style indicators), Updated Terms of Service and Privacy Policy accordingly. The app provides non-medical, wellness-oriented visual indicators, similar to many other wellness apps (breathing record, stress reference, basic heart rate ranges), but no medical interpretation, no diagnosis, and no treatment advice. Still, the review response continues to classify the features as “medical-related data” and asks for regulatory approval. My Questions I understand that Apple cannot comment on specific app review decisions, so I would like to ask for clarification on the general interpretation of Guideline 1.4.1: Under what conditions does a wellness feature become classified as “medical” under 1.4.1? Examples: If the UI shows only relative ranges (e.g., “slow / average / fast”), If we avoid numeric medical measurements, If we avoid clinical wording, If the feature is based on general wellness indicators (like stress trends, breathing rhythm, etc.) Are disclaimers + non-clinical UI enough to classify the content as wellness? We added disclaimers in the UI that match Apple’s guidelines: “This feature provides wellness-only information and is not intended for medical use.” Yet it still appears to be treated as medical. Is there any additional requirement for wellness-only apps to avoid being considered medical devices? For example: Specific wording we must avoid? Required UI changes? Required documentation in App Review Information? Differences between “wellness”, “health”, and “medical” in the context of 1.4.1? If similar apps on the App Store provide wellness-style visualizations (stress, breathing, HRV trends), what distinguishes them from medical use? We would like to understand how to align with the Human Interface Guidelines and App Review Guidelines correctly. Goal The goal is not to bypass regulations but to correctly classify our features as wellness-only. If there is any general guidance for how to structure such features so that they clearly fall under the wellness category, that would be very helpful. Thank you in advance for any clarification or guidance.