I’ve been building iOS apps since 2011 and have worked on hundreds along the way. Recently, I started a series on App Store Optimization (ASO) to share tips, strategies, and lessons learned. In this first post, I dive into how responding to customer reviews can directly influence ASO performance and App Store ranking - covering timing, response style, and best practices to turn negative reviews into positive ones.

Hi everyone, we are currently facing an issue with one of our apps regarding the new icon requirements in iOS 26. • We created the app icon using Apple’s Icon Composer. • On the device, everything works perfectly: the app icon is shown on the home screen, and it can also be customized with the new iOS 26 features (colors, transparency, etc.). • However, in TestFlight the app icon is not displayed at all (in the TestFlight app on the device). • In App Store Connect, the icon is also not shown in the overview for the app. Interestingly, within the list of TestFlight builds in App Store Connect the icon is visible. What we have tried so far: • Created an archive and manually uploaded it to App Store Connect → no icon in TestFlight. • Took the working Icon Composer asset from another app target where everything works correctly, deleted the old one in this project, and copied the working asset into the problematic target. → Same behavior: visible on the device, but still missing in TestFlight and App Store Connect overview. In contrast, in another app (using the same workflow and also Icon Composer), everything works perfectly: the icon shows up on the device, in TestFlight, and in App Store Connect. Has anyone experienced a similar situation? Is there something specific that needs to be set in App Store Connect (e.g. Marketing Icon / Branding section), or could this be related to the new iOS 26 icon handling? Any help or hints would be greatly appreciated. Thanks in advance!

To make an iOS app available on Apple Silicon Macs, we need to enable the availability option under Pricing and Availability in App Store Connect. But unfortunately, macOS 26 is not still available as a choice there and I don't want to make the app available on earlier macOS versions. Does anyone have any solutions? Would adding the LSMinimumSystemVersion key to Info.plist work?

Hi everyone, I’m trying to submit my first release with In-App Purchases, but I can’t keep the IAP attached to the submission. Status: Not published yet (first release) Version: 5.0.0 (multiple builds: (7), (8), etc.) What happens I upload a new build and select it for version 5.0.0. I go to Add for Review and select my newly created IAP (auto-renewable subscriptions). I submit the version. When I re-open the submission details, the IAP section is empty (they no longer appear as “Included in this submission”). The result is a double failure: App rejection (Guideline 2.1 – “IAP not found in the submitted binary”). Each IAP is also rejected for lack of a binary in its review context. It looks like the IAP and the build keep getting detached from each other after I submit. Since this is my first version, I’ve tried changing builds and even editing version metadata, but it still feels like I’m just “editing the first version” rather than creating a fresh link between this binary and these IAP. What I already tried Creating the IAP and selecting them during Add for Review. Ensuring the IAP have complete metadata/localizations and pricing. Re-submitting using a new build number (5.0.0 (8), etc.). Checking Monetization → In-App Purchases and Subscriptions; products exist, but after submit they stop appearing under the submission. (When testing the opposite path) Removing IAP entirely for a non-IAP release — but Review still referenced IAP “linked” on their side. Questions What is the exact, canonical sequence to link a new build to newly created IAP so they remain listed under “Included in this submission” after I hit Submit? For first-time IAP, do I need to press Submit for Review on each IAP product before selecting them in the app submission? Or is selecting them during Add for Review enough? Which product statuses are required so that IAP do not drop off the submission? (Ready to Submit vs Waiting for Review, etc.) Can changing the build (or editing version metadata) after attaching IAP cause them to be silently removed from the submission? Since this app is not yet published, is it advisable to create a new app version (e.g., 5.0.1) to “reset” the linkage, or should a new build under 5.0.0 be sufficient? Any guidance or a step-by-step checklist to keep IAP attached to the submission would be greatly appreciated. Thanks! — Victor

Even the best apps struggle to get noticed—over 5 million apps compete in stores, and most never hit 1,000 downloads. Visibility, not quality, is the real challenge. App Store Optimization (ASO) is the key to breaking through. Optimizing your app’s title, keywords, visuals, and description, combined with ongoing testing and competitor analysis, can drastically improve discoverability and downloads in 2025.

Hello, We’re experiencing a blocking production issue with our new in-app subscriptions and would appreciate guidance. Our latest app version was approved and is live on the App Store, but the new subscriptions we submitted with it are still stuck in “Waiting for Review”. They’ve been in this state for about two months, and purchases in production fail with an error. I already sent an email, but I haven’t received any response. Yesterday,I uploaded a new version of our app and was approved. I had hoped that submitting another version might resolve the issue, but unfortunately the subscriptions are still not active. This is extremely frustrating since users cannot purchase or upgrade. Has anyone experienced this before? What should we do next to get these subscriptions approved? Thanks in advance.

The specific identifier (com.utel.prod) is not getting listed in app creation form in app store connect. I hereby attached my screenshot.

I have several subscription plans in the App Store that I no longer wish to offer to new users. In my app, these old subscriptions are hidden, but they remain active so existing subscribers can continue their plans and be charged as usual. However, some new users are still able to switch to these old subscription plans through the App Store. What is the best solution for this situation? I want to continue serving existing subscribers while preventing new users from subscribing to these legacy plans. Thank you.

I’ve observed several areas in iOS where user experience could be enhanced, such as keyboard flexibility, animation speed, biometric options, cache management, background uploads, navigation reliability, and automation features. Addressing these aspects would not only improve usability but also align iOS more closely with diverse user needs across regions and use cases. What enhancements would you consider most valuable?

Hi Please when we upload our App from Xcode to App Store Connect, we do receive upload message but when we go to App store Connect interface, there we see our app being in process but it gets disabled and never goes to next step, and we waited for more than 2 hours, also we haven't received any email when we upload the app and when we refresh the page, the build in processing gets disappeared.

My iOS app currently holds a 3.5★ rating with limited reviews, and I’d like to raise it by motivating happy users to share feedback. I’m looking for ethical ways to do this without being pushy. What are the best strategies and timing for review prompts to boost ratings while keeping users satisfied?

For ~8 weeks (10+ support replies) I’ve been unable to switch my app’s Primary Language from en-CA to en-US. App Store Connect shows: “Primary Locale couldn’t be saved because you must first provide all the required screenshots for each version in this language.” State: Default product page has complete iPhone + iPad screenshots for en-US and en-CA (live/approved). Issue began before any CPP existed; I have since removed all CPPs. Error persists, which suggests a stale/ghost CPP localization still being validated, or other issues. Questions: What does “for each version” precisely validate (live / in-prep / historical; default vs CPP)? Can deleted/never-approved CPPs still be validated, and how can they be purged? Anyone seen this after CPP removal—what fixed it? Happy to DM an Apple Staffer the case ID, a HAR of the failed save, and a short screen recording. Thanks! P.S. This has been open for ~8 weeks; I’m seeking an engineering-owned view to identify the specific unmet validator requirement or confirm a product issue. P.S.S. the App Catalog Report for my account is currently returning an empty file (Email) (requested via Apps → … → Reports). If others have seen this recently, is there a workaround - or should I file Feedback?

I’m launching my game on May 9 and have been going through Apple’s App Store course. It’s informative but also feels like a marketing push. For those who’ve tried App Store campaigns, did they actually drive results like views, conversions, or in-app purchases? Sharing your app/industry for context would be super helpful.

Hi, I'm developing a watchOS app, no parent iOS app, when I archive the app, and submit it to APP Store Connect, it returns an info.plist error that I didn't set micphone permission description, but I actually set it. Could anyone how to fix it? and how to submit only a watchOS APP? Any help will be appreciated! thanks！

Hi everyone, I’m currently working on a project based on the Telegram iOS open-source code. My goal is to build an unofficial Telegram client with Telegram’s permission (they have publicly allowed third-party clients under their open-source license). My app includes unique new features and UI improvements that are not present in the official Telegram app. Essentially, it’s Telegram plus additional features — built from the official source, but extended significantly. However, when I try to submit my app to the App Store, Apple rejects the build under Guideline 4.3(a) - Design - Spam with this message: “We still noticed your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps.” I completely understand Apple’s intent to prevent low-effort clones or spam apps. However, in my case, this is a legitimate open-source-based project with new and unique functionality. I’ve spent a lot of time designing new features and improving user experience — this is not just a rebrand. Has anyone else experienced this issue when submitting an app based on an open-source client (like Telegram)? Is there any recommended approach to help Apple differentiate my app as a distinct and valuable product? Any advice or guidance would be greatly appreciated! 🙏 — Additional Context: The app is based on Telegram’s open-source iOS client. The app includes new features and UI changes. It’s submitted under a different name, icon, and bundle ID. I’m happy to comply with any additional clarification Apple might need. Thanks in advance to anyone who can share insight or experiences with this kind of rejection.

I have 2 app store connect apps: "" ".beta" This is necessary for our usecase as we are building an iOS blockchain wallet, for a chain that updates itself every ~3 months adding new features/changing. We need the communities input, and can't have them uninstalling/re-installing the production app constantly, having to re-import private keys, etc. So we use 1 app store connect app for production releases, and another for public facing long running beta, where we experiment with new features before pulling them into production. Allowing users to have both installed at the same time Last week my CI (without any changes to scripts, project, profiles, etc), started failing for the production build with the error: [altool.105176BE0] Validation failed (409) This bundle is invalid. The bundle identifier cannot be changed from the current value, '<bundle-id>.beta'. If you want to change your bundle identifier, you will need to create a new application in App Store Connect. (ID: ae60bab4-0c01-4b2e-9ea9-91a73adccc14) Nowhere in any of the .app, .ipa, info.plist, provisioning profiles, etc, is it referencing ".beta", everything is referencing "" I tried building it manually locally, same error. I took the local output that failed with xcrun altool, and instead dropped it into Transporter, and it uploaded successfully to the production app Is it possible that xcrun altool is using an app store connect API that changed sometime in the last few weeks? Maybe the search/sort ordering logic has changed?

I’ve invested heavily in developing my app, but marketing and ASO remain challenging. Despite experimenting with different keywords and tools, my rankings haven’t improved much. Is this just a matter of time?

I have been trying to update an app of which the code base hasn't changed in two years. It still builds fine and runs fine, on simulator and device, but... when uploading it to Testflight I get the error "The app contains one or more corrupted binaries. Rebuild the app and resubmit.". I have been rebuilding like a maniac, trying to look at what could be wrong with the binary, I let ChatGPT misguide me on the log files, I think I have tried everything... but to no avail. Any ideas how I could find out what goes wrong?

I requested an expedited review, and the app was approved within a few hours. However, the in-app purchase subscription plan is still under review. Is there anything I can do to speed up the approval process for the in-app purchase, or do I just have to wait? Thanks.

My message - URGENT - ESCALATE - App Store Connect UI Broken for 10+ Days I have already had to remove a subscription and do a new one as the option for a new in-app purchase was not appearing (I tired to explain that but no one is listening) I still cannot proceed with my app submission. New critical issues: My app version is frozen now. I have tried on a new browser, deleting caches but nothing is working. Every build is costing me money. I email and no response from Monday. Cannot change build from 11 to 12 in app version - no way of deleting last build - no red circle appears. In-App Purchases section is completely unresponsive - cannot attach subscription I have build 12 ready in TestFlight. I have subscription impulse404_premium_monthly_v2 ready to submit. But App Store Connect UI is broken and preventing me from attaching either. This is now costing me significant money in delays. Please escalate this immediately. MY RESPONSE FROM APPLE - Hello, Thank you for making the requested changes. However, we are unable to proceed with our review as this app’s status is currently “Prepare for Submission.” You will need to submit a new build for review. More information about submitting builds can be found in App Store Connect Developer Help. We look forward to reviewing your resubmitted app. Best regards, App Review