I am developing a utility application for macOS. In the next version, I would like to access data files from multiple third-party web browsers. However, requiring users to manually select and grant access to each browser’s folder individually would be inconvenient from a usability perspective. Therefore, I am considering requesting Full Disk Access for my app. Is it realistic to expect App Store review approval when requesting Full Disk Access? Under what conditions or use cases is such permission typically accepted by Apple? I would greatly appreciate any advice or experiences you can share.

Hello, I have an app with a few essential asset packs currently totaling to ~8GB. I've noticed that when trying to install the app fresh from TestFlight, there is a significant delay between tapping install and the app appearing on the device in the loading state. The delay is long enough where it's hard to tell what's happening, or if the installation has failed. This also appears to be an issue in App Review, as I've had my app rejected twice due to the app not loading on the reviewers device. The reason they gave is UIRequiredDeviceCapabilities is blocking the installation, but UIRequiredDeviceCapabilities is empty. Note: I'm not looking for App Store review help, simply sharing the extent of the issue. Thank you

Mobile app marketing feels even more challenging in 2026, with once-reliable tactics like paid installs, influencer promotions, and push notifications losing impact while organic growth and user retention continue to slow. I am curious what is truly working for developers in 2026, whether stronger ASO, community-led engagement, web-to-app funnels, or long-term retention strategies are outperforming traditional paid acquisition.

Hello everyone, I’m looking for guidance regarding a prolonged App Store review delay. I submitted my app for review more than 12 days ago, and its status has remained “Waiting for Review” with no updates. I have also tried contacting Apple through App Store Connect and the Contact Us option, but I haven’t received any response so far. This app does not include any unusual features, private APIs, or sensitive content, and previous versions (or similar apps) were reviewed much faster. The long delay is blocking a planned release and affecting our timeline. Could anyone please advise: If this review duration is normal lately? Whether there is a recommended escalation path beyond App Store Connect messages? If there are any known review backlogs or issues I should be aware of? Any insights or suggestions from developers who’ve faced a similar situation would be greatly appreciated. Thank you for your time and help.

ASO is by far one of the most frustrating parts of being an indie iOS dev. Despite trying keywords, descriptions, screenshots, and icons, results are unpredictable and competing with big-budget apps feels impossible. Has anyone found a way to make it work?

I'm looking to learn from others in the community. Please share any effective tips, hacks, or approaches you've used to boost app visibility and downloads through App Store SEO. Insights on keywords, descriptions, or metadata optimization are especially welcome.

Brand new to app development and marketing and preparing to launch my app on both the App Store and Google Play Store soon I understand ASO is a strong approach for organic growth and would appreciate any tools services or practical advice on how to do ASO efficiently and effectively

On January 1, 2026, we received a notice regarding the potential removal of our app with a 30-day resolution deadline. We treated this matter with immediate urgency and submitted an appeal on the same day. However, two weeks have passed without any feedback or clarification. As we have not yet received specific details regarding the violation, we are unable to identify the exact cause or take the necessary corrective actions. With only two weeks remaining in the compliance window, it is critical for us to understand the issue promptly to resolve it before the deadline. Could you please provide an update on the status of our appeal? We are fully committed to complying with App Store policies. If there are any additional materials required or proactive steps we should take while waiting, please let us know.

Hi everyone, We’re looking for advice regarding an App Store review rejection and would really appreciate insights from developers with similar experience. Our app is a retro game emulator platform. It provides emulator functionality only (e.g. NES / GB / GBA emulation) and does NOT include, bundle, or download any game ROMs. Key points about our app design: ❌ No ROMs are bundled or distributed ❌ No in-app ROM downloads ✅ Users can only import their own ROM files that they legally own (e.g. personal backups) ✅ No copyrighted game names, box art, screenshots, or branding are used ✅ The app is positioned as a general-purpose emulator tool, similar to a media player that plays user-provided files However, during review we received the following rejection: The app appears to contain copyrighted video game files. Apps and their content should not infringe upon the rights of another party… We’re confused about what might have triggered this decision and would appreciate guidance on: On what basis Apple may conclude that the app “contains” copyrighted game files? Could this be related to: App screenshots or preview videos? Default demo flows or UI text? The emulator functionality itself? What changes are typically required to pass review, such as: Adding stronger legal disclaimers Requiring user confirmation that imported ROMs are legally owned Removing any potentially misleading UI wording Explicitly clarifying ROM ownership responsibility We’ve noticed that similar emulator apps already exist on the App Store, so we’re trying to understand: Whether there is a clear compliance path What modifications have worked for other developers in similar cases Thanks a lot in advance for any advice or shared experience 🙏 Happy to provide more details if needed.

Hello everyone, I’m looking for some advice or shared experiences regarding an app rejection under App Store Review Guideline 4.3(b) – Design – Spam. Our app was rejected and, after an appeal to the App Review Board, Apple maintained that the app “duplicates the content and functionality of similar apps in a saturated category.” We strongly disagree with this classification and are struggling to understand how Guideline 4.3(b) has been applied in our case. The app was developed as an original product: Custom-designed content (including original cards and interactions) A unique visual style and UI A distinct interaction flow focused on encouraging social interaction between users This was not a template-based or reskinned app, nor is it part of a series of similar submissions. We fully respect the App Store Review Guidelines and are open to making adjustments to better align with them. However, what we find difficult is the lack of specific, actionable feedback. We have not received clear guidance on which exact elements are considered duplicative or what changes would meaningfully address the concern. Some of the questions we are hoping the community can help with: In your experience, what typically triggers a 4.3(b) rejection in cases like this? Are there specific mechanics, terminology, or presentation choices that reviewers often interpret as problematic? Have others successfully resolved a 4.3(b) rejection without completely abandoning their app concept? We have already invested significant time and resources into this project, and being advised to create an entirely new app is not financially feasible for us. We are genuinely trying to understand how to proceed in a way that is constructive and compliant. Any insights, experiences, or advice would be greatly appreciated. Thank you in advance. — Lars

This is my first iOS app release and I’m a bit confused. The initial version was reviewed in under 12 hours (rejected), and the corrected version was approved just as quickly. But my Product Page Optimization with only screenshots has been stuck in “Waiting for Review” for four days. Do these get reviewed only with new versions, or should I just wait it out?

My app is being rejected again and again because the reviewer keeps saying that there is a bug with the app, the get OTP button did not work. They are using Ipad Air. Now the issue is that I have tested my app again and again on every device possible and I am able to login perfectly every time. I am using firebase phone authentication to login. I don't know what to do ?

I have two apps stuck in "Waiting for Review" status: App 1: Submitted Dec 20, 2024 (still waiting) App 2: Submitted Jan 12, 2025 (still waiting) I've requested expedited reviews but haven't heard back. I know the holidays can cause delays, but it's been over 3 weeks for the first app. Has anyone else experienced similar delays? If anyone from Apple's review team sees this, could you check on these submissions? Happy to provide more details if needed. Thanks guys

I’m attempting to resubmit my app after a few unsuccessful review submissions (first time dealing with this process). Previously, when I resubmitted (the last two times), the “In-App Purchases and Subscriptions” section was available on the version page, and I could select the appropriate IAPs and subscriptions prior to submitting for review. However, on the resubmission attempt, this section is no longer visible anywhere on the version page! I’ve tried several troubleshooting steps, but it still won’t appear. Current status: All IAPs/subscriptions: Waiting for Review App version status: 1.0 Prepare for Submission It has been suggested that I "deleting all my subscriptions and [do] them over again..."; however, this workaround is completely unacceptable! While it may work for unreleased apps, it would be catastrophic for production apps. If this UI bug occurred during a subsequent update, deleting IAPs would permanently invalidate the original product IDs—which cannot be reused. This would break all existing customer purchases! Does anyone know how to get around this?????

Hi Forum I am working on an ios app with a companion watchos app. The watchos app was made in 2018, it uses watchkit and has a watchkit app target and a watchkit app extension target. When I started working on it, the app was already published and running. More importantly, the watch app was installing on the users watch automatically, when the app was installed on their phones. I came in and made some changes, updated some things and added some smaller features. After uploading to testflight and testing the app there, we sent it for review and updated the app. This updated app, introduced the issue that when users now downloaded the app, the watch app seems to be missing. For me, downloading this new version on either testflight or app store works fine, but whenever my boss or a new user does it, the watch app is missing. I have tried to go back to the older version of the app I started with, but this doesn't seem to change anything. My coworker tried to do do the same thing, uploading the old version, but with a new version number and everything works like normal. He suggested the reason was that he uses xcode 16, while I use xcode 26 and the updated xcode has some slightly different settings, which can mess it up. Does anybody know about this or have the same problem? And is it correct that it can be the way settings are handled in xcode 26 compared to 16?

I am seeking guidance after experiencing what appears to be an inconsistent and unresponsive review process. My app was rejected under Guideline 4.3(b) (Spam - saturated category) and Guideline 2.1 (App Completeness - IAP not found in binary). I would like to highlight several concerns: Regarding 2.1 - IAP Issue: The rejection states that In-App Purchase products "could not be found in the submitted binary." However, a previous reviewer successfully accessed and screenshotted the exact purchase screen in an earlier review cycle. The IAP is clearly implemented and functional. This inconsistency suggests the current reviewer may not have thoroughly tested the app. Regarding 4.3(b) - Spam: I have submitted detailed appeal notes explaining the unique, differentiating features of my app that are not found in any competing applications in this category. These include: Integration with real-time external data sources (not static content) Cultural and regional elements unique to my market AI-powered contextual features beyond template-based functionality A distinctive companion feature focused on reflective dialogue rather than predictions Despite providing this documentation, I receive identical templated rejection responses with no acknowledgment of the specific points raised in my appeals. My Questions: How can I ensure that reviewers actually read and consider the detailed notes provided in appeals? If a previous reviewer could access the IAP screen, why would the current reviewer claim it doesn't exist? Apple actively features apps in this category in editorial collections. What specific criteria differentiates "approved" apps from those rejected as spam? I have invested significant development time and resources into creating something genuinely innovative, not a clone. I respectfully request that my submission receive a thorough, hands-on evaluation rather than a surface-level category-based rejection. Any guidance from Apple staff or developers who have navigated similar situations would be greatly appreciated. Most Importantly: This experience is deeply discouraging and exhausting. This process does not feel developmental or constructive that it feels like a barrier designed to wear down independent developers. The inconsistency between platforms is striking: my app was approved on Google Play without any issues, and we were expecting simultaneous production releases. Instead, I am trapped in a rejection loop here while my competitor advantage erodes daily. How can it be that one platform recognizes the legitimacy of my work while the other dismisses it with templated responses? Simply providing vague assurances and surface-level category rejections helps no one, not developers, not users, not the ecosystem. Independent developers are the backbone of app marketplace diversity. When the review process becomes this opaque and unresponsive, it doesn't protect quality that it stifles innovation and consolidates the market in favor of established players who can afford to wait indefinitely. I am not asking for special treatment. I am asking for a fair, thorough, and consistent review.

I’m working on an iOS app and need help with ASO to find the best keywords for title, subtitle, description, and keyword field. Can anyone suggest free tools that show keyword volume, difficulty, and competitor keywords?

A 1.69% App Store conversion rate could be due to factors like unclear value proposition, unoptimized screenshots, or lack of strong reviews. Improving visuals, refining your app description, and gathering positive ratings can help boost installs.

User spending on mobile apps keeps rising, but competition is growing faster, making App Store Optimization a critical pillar of mobile growth by improving visibility, reducing cost per install, and driving stronger organic performance. This post highlights the most important ASO trends for 2026, including AI driven optimization, user intent focus, localization, creative testing, analytics, and privacy first strategies to help apps grow consistently on the App Store.

I am in the middle of trying to get an app approved for beta release and the back and forth with the App Store reviewers has been incredibly frustrating and concerning. On Tuesday, I created an app record for my app but quickly realized I made it under the wrong account- I'm working for a company that has a few brands under it's umbrella, and I was under the wrong account when I created the app record. Rather than wait several days to get Apple's approval to transfer app ownership, I decided to delete that app record and create a new one under the proper account. Worst mistake of my life. Now, Apple is insisting that the new app record is spam despite my clarification that I own the other app record and that it was deleted before the new one was created. I have no choice but to believe that somebody else is using our branding and asset somewhere in the App Store that I can't see. Does anybody know how I can resolve this? It should have never taken me the whole week to make an app available on test flight and my stakeholders are not pleased, and I have no clear path towards resolution that will allow me to use the proper branding with the proper company account. App review refuse to offer any solutions, I am stuck with a brand name that I can't use because it's associated with an app I already deleted.