Few of my iOS app’s universal binary exceeds 200MB, while individual device-specific binaries remain under 200MB. I understand Apple recommends keeping app binaries below 200MB to allow downloads over mobile networks. I want to confirm whether the size of the universal binary impacts the ability of users to download or update the app (App Store build) over cellular networks, or if only the device-specific slice size is considered?

Went to update my MacOS app on the Connect site. After I clicked on + on the Distribution page, I thought it was weird that my artwork was missing, so I tried to re-add my prior artwork. This was blocked with the message "Please save new locales before uploading screenshots". I only have en-us as a locale, that hasn't changed. So now I can't update it.

Once, the App Store empowered indie creators - small teams could launch great apps and find users easily. But in 2025, that era feels long gone, with algorithms, big players, and pay-to-win discoverability reshaping everything. Is there still a real chance for indie iOS developers today, or has Apple’s evolving ecosystem made independent success nearly impossible?

Hi everyone, I’m encountering an issue with my in-app subscriptions setup. When I test using the StoreKit configuration file in Xcode, everything works correctly — the subscriptions are fetched and I can simulate purchases without any issues. However, when I switch to the Sandbox or Production environment, my app fails to fetch the available products from Apple’s servers. The call to fetchProducts (from the expo-iap library) returns an empty array. Here’s some context about my setup: Framework: React Native (Expo Bare Workflow) Library: expo-iap Products: Auto-renewable subscriptions StoreKit Configuration: Synced with App Store Connect Status: Subscription Plans are approved in App Store Connect I’ve verified the following: The product identifiers in code match exactly with those in App Store Connect. The app is signed with the correct bundle ID. I’m testing with a Sandbox account (logged in via Settings -> Developer -> Sandbox Tester Account). Despite this, the response from Apple’s servers still contains an empty array. Has anyone experienced something similar with expo-iap or in general when moving from StoreKit configuration to Sandbox/Production? Any suggestions on what else I could check or common pitfalls I might be missing? Thanks in advance!

Hello, Our Xcode Cloud builds are successfully archiving but fail every time during the "Export archive for app-store distribution" step. The issue appears to be a persistent authentication failure with App Store Connect that we are unable to resolve. Primary Error: The build logs show a critical authentication failure. IDEDistribution.critical.log shows: App Store Connect request for store configuration failed for account Session Proxy Provider... Unable to authenticate with App Store Connect. DVTITunesSoftwareService.log specifies the error is DVTITunesSoftwareServiceFoundation.DVTServicesSessionProviderCredentialITunesAuthenticationContextError.proxy. The build process eventually terminates during the IDEDistributionSymbolsStep with an Rsync failed error, which we believe is a symptom of the earlier authentication failure. Troubleshooting Already Performed: We have already taken the following steps without success: Verified the account used for the integration has "Account Holder" and "Admin" roles. Confirmed that Xcode Cloud's automatic signing is working correctly and is able to create new provisioning profiles. Thoroughly checked the App Store Connect web UI under Users and Access > Integrations > Xcode Cloud for a way to reset the connection, but no such option exists. Removed and re-added the Apple ID in the Xcode application's settings (Xcode > Settings > Accounts) on a local Mac. Our hypothesis is that the integrated authentication session between Xcode Cloud and App Store Connect is invalid or stale, and there is no user-facing way to reset it. Has anyone else encountered this "Session Proxy Provider" authentication error with Xcode Cloud? Is there a known solution or a different method to force a re-authentication of the service connection? Any guidance from Apple engineers or other developers would be greatly appreciated. (Developer Support Case: 102717975870)

I recently turned on the enhanced security options for my macOS app in Xcode 26.0.1 by adding the Enhanced Security capability in the Signing and Capabilities tab. Then, Xcode adds the following key-value sets (with some other key-values) to my app's entitlements file. <key>com.apple.security.hardened-process.enhanced-security-version</key> <integer>1</integer> <key>com.apple.security.hardened-process.platform-restrictions</key> <integer>2</integer> These values appear following the documentation about the enhanced security feature (Enabling enhanced security for your app) and the app works without any issues. However, when I submitted a new version to the Mac App Store, my submission was rejected, and I received the following message from the App Review team via the App Store Connect. Guideline 2.4.5(i) - Performance Your app incorrectly implements sandboxing, or it contains one or more entitlements with invalid values. Please review the included entitlements and sandboxing documentation and resolve this issue before resubmitting a new binary. Entitlement "com.apple.security.hardened-process.enhanced-security-version" value must be boolean and true. Entitlement "com.apple.security.hardened-process.platform-restrictions" value must be boolean and true. When I changed those values directly in the entitlements file based on this message, the app appears to still work. However, these settings are against the description in the documentation I mentioned above and against the settings Xcode inserted after changing the GUI setting view. So, my question is, which settings are actually correct to enable the Enhanced Security and the Additional Runtime Platform Restrictions?

Hey everyone, I’ve noticed a big drop in my keyword rankings lately, and it seems linked to Apple’s recent ASO update that’s been trending on Twitter. Has anyone figured out what changed? It looks like app titles may now have less impact on rankings.

I'm trying to submit a support request to get an issue resolved in my organization's account, but both the phone call-back and email support forms are giving errors whenever I try to submit an issue. The phone form just says "There was a problem processing your request.", and the email form says "This email address isn’t valid. To update your email address, visit account.apple.com.". But the email address is hard-coded to my account email, and it's the main email for my company which I have been successfully using for months!! How am I supposed to get in touch to get this blocking issue fixed when all contact methods require your to go through this broken form? I suspect the original issue I was contact support about also has to do with this, since it's titled "Email Verification".

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

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.

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’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 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?

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.

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！

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.

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?

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?

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.

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?