Hello I’m 17 and just made my first app to test everything was working. I went to another phone of mine and downloaded the app and paid for a subscription. It’s been about 11 hours and the subscription still hasn’t showed on my App Store Connect trends. Is this normal or should I take the app down and sort this issue?

Hello, I am working on app clips and I wish to know how is the code packaged when the build gets uploaded to App Store Connect? Is there any documentation around this or can you help me with what happens while generating the binary? I added 7 files to app clip target. Some are of 1 KB and others are of 2KB when I look for it's size on my MacBook. However when I upload a build to App Store Connect with these 7 files, I am noticing the size of App Clip increasing by almost 1MB. These files are code files i.e. .swift files and not assets. How is it possible to that the App Clip size grows by an MB for these 7 files? Even if I consider them to be 2KB each, shouldn't the app clip size increase just by 14 or so KB's?

Hi, I'm working on an app that currently support iOS 16+ I'm considering to raise the deployment target to iOS 26 For users on devices with version lower than iOS 26, I know they can continue to use the app they have already installed and can even redownload it via the last-compatible versions support. The question is simple - once the version with deployment target iOS 26 is released, is there any way to update the last compatible version of iOS 16+ in case a critical bug or security vulnerability has to be fixed? For example lets say that the current version is 1.2.2 (iOS 16+) new version 2.0.0 (iOS 26+) is released users with iOS 26 can install 2.0.0 existing users with iOS 16-18 can continue to use and reinstall 1.2.2 in the meanwhile, the app evolves and reaches 2.1.5 6 moths later, a critical bug or security vulnerability on 1.2.2 has to be fixed, so 1.2.3 version, based on 1.2.2 codebase with the necessary fixes has to be deployed to old users. How to update existing users with iOS 16-18 from 1.2.2 to 1.2.3? Is there any mechanism to achieve this? Does AppStoreConnect or AppStoreConnectAPI allow such thing?

Hello! we're currently in the process of trademarking a company name for an application we're building here in the US. As this has occurred, an app built for UK users has been published with the exact same name. As we understand our trademark wont be enforcable in the UK from the US, we are disappointed as it seems we can no longer use that exact name for our application. How similar can names be in the app store? for example if their app was FunFriend, could mine be "FunFriend - US"? or "FunFriends"?

Hello, We want to upload an app for our customers that uses our company's authentication system which will enforce 2factor (2fa) soon. The App review section in App Store Connect accepts only username and password. What is the desired way to interact with the review process now? Will Apple themselves register an account to use with 2fa? Or how could we provide access to the token? Can someone help? Regards

Hi, My developer payment was marked as "Paid" on June 5, 2025 in App Store Connect. As of June 16, the funds have still not arrived in my bank account. Apple only provides a Transaction ID (324756355), but no EFT or SWIFT reference number. My bank confirmed there is no record of any incoming or returned payment. Other developers have received their June 5 payments already. Mine seems to be either not sent or stuck. Apple support keeps telling me to wait 30 days, but without proof of actual transfer, this isn’t acceptable. Has anyone experienced this kind of delay before? Thanks.

This is my first app subscription submission. I submitted it a week ago today and the status for the sub still says "Waiting for Review". I assume there's nothing for me to do at this point other than wait for Apple's approval. How long do these things normally take?

Hello everyone, I’m reaching out to seek advice and support regarding a confusing issue I’m experiencing with my app’s review process. App ID: 6744330283 Here’s the situation: Versions 1.0 and 1.1 of my app were approved and successfully published on the App Store. However, updates 1.2 and 2.0 have both been rejected for Guideline 4.3 – Spam. The rejection happens extremely fast – less than 10 seconds after the app goes “In Review”, it gets rejected. There is no indication that the reviewer even launched the app. This is very frustrating because: The app has real user reviews, In-App Purchases, and active paying users. My app is 100% original – it is not a copy or template-based app. Even worse, the review process for versions 1.2 and 2.0 took over 7 days before even starting, and then they were rejected instantly, again without being opened. I’m happy to cooperate and improve my app further, but I feel like this may be a misunderstanding or a mistaken flag by an automated process. Has anyone experienced something similar? Is there any way to get a more thorough manual review or speak directly with the review team? Thanks in advance for any guidance or shared experience.

I inadvertently used the build number for the version number. How can I remove these versions/builds so that i can get back to my normal versioning scheme? I am now stuck using a version number of 110 instead of a build number of 110.

Hi there, we have an issue with subscription renewal process. The price of the subscription is 169USD/year. But we see that some of the users renew at 129USD while other renew at normal 169USD price. What is the reason these users renew at lower price? Best regards, Mykhailo Tys

Have we hard anything at all about this documentation being updated? I'm a first-time developer, I'm struggling with the relatively opaque approvals process, and all the articles they point me to are completely untethered from what App Store Connect actually looks like. Had the same issues a couple months ago when I was first playing with TestFlight, it's like all the documentation is referencing an older version of App Store Connect. Is there a cadence to when they update this stuff, or just... ?

Hello, I have alternative icons on my app (this is the production build) yet I don't see the button to select an icon for a product page Treatment Do you know where the problem could come from ?

Hey everyone, We recently submitted our new dating app, Rove Dating, and it’s been rejected under Guideline 4.3(b) — “Design: Spam.” I’d really appreciate your insights, especially from anyone who’s faced something similar or has experience getting nuanced apps approved in a saturated category. Before building Rove, we spoke to dozens of users of existing dating platforms. We consistently heard the same thing: people are deeply dissatisfied with current apps. They’re overwhelmed, burned out by swiping, and frustrated by endless choices and low-quality interactions. It became clear that the problem isn’t that there are “too many” dating apps — it’s that most aren’t adapting to how people actually want to date in 2025. We designed Rove to address those pain points head-on, with a totally different approach to matching, message limits, and emotional safety. We believe our app meaningfully improves the dating experience — but we’re having trouble getting that across in the review process. Below is the explanation we’ve been submitting, which we feel strongly communicates how Rove is different. If anyone has tips, feedback, or even just a second set of eyes on how we’re presenting this, I’d be grateful! –– Response to Guideline 4.3(b) – Design – Spam We respectfully disagree with the assessment that Rove Dating duplicates existing apps. Rove is not a clone of existing dating apps — it introduces original interaction mechanics and novel safety features designed to address the growing frustration users feel toward current dating platforms. ⸻ What Makes Rove Dating Unique Rove Dating is a highly curated experience that intentionally limits user engagement to foster more meaningful, emotionally safe interactions: Key Differentiators: • No Swiping or Infinite Browsing: Users see a small, rotating selection instead of endless feeds. • Limited Conversations: Each user can have only 3 active conversations at a time. • “Shoot Your Shot” Mechanism: • Men can initiate contact with a limited set of women. • If a woman declines, the man can try with someone else — if not, he must wait. • Women can only receive inbound messages, helping prevent message fatigue. This constraint-based system: • Reduces inbox overload (especially for women). • Encourages higher-quality, intentional messages. • Mimics real-life social dynamics — where opportunities are limited and meaningful. ⸻ Innovative Safety System: MPAA-Style Behavior Ratings Rove also introduces a first-of-its-kind safety feature inspired by the MPAA film rating system: • Male users are assigned a community-informed behavioral safety rating (e.g., G, PG, R) based on in-app messaging analysis. • Women can quickly assess a match’s tone, trustworthiness, and vibe before engaging. • This system encourages respectful behavior and promotes a safer, more transparent dating environment. This type of behavioral transparency does not exist in any other dating app currently on the App Store. ⸻ Conclusion Rove is not another swipe-based clone. It is a thoughtfully reimagined dating platform built around scarcity, respect, and intentionality. Its mechanics — from conversation caps to safety scores — are fundamentally different from other offerings in the App Store’s dating category. We hope you’ll reconsider Rove on the merits of its original features, purpose-driven design, and unique safety innovations.

I'm encountering an issue when trying to use alternate app icons in a Product Page Optimization A/B test on the App Store. Here's what I've done so far: I added my alternate icons to the ASSETCATALOG_COMPILER_ALTERNATE_APPICON_NAMES build setting. I set ASSETCATALOG_COMPILER_INCLUDE_ALL_APPICON_ASSETS to YES. All icons are correctly configured in the asset catalog, and I can switch them programmatically in the app using setAlternateIconName(_:completionHandler:) with no issues. However, when I go to App Store Connect and try to create a new product page variant, I don’t see any option to select an alternate app icon for A/B testing. It only allows me to change screenshots and preview videos. Am I missing a step, or is there any additional configuration required to allow icon testing in Product Page Optimization?

Hi, I'm integrating in-app subscriptions using StoreKit 2 in my iOS app, and I've run into an issue where I'm unable to fetch any subscription products via: let products = try await Product.products(for: productIDs) This consistently returns an empty result (products.count == 0) when running on a real device using a sandbox account. Here's some relevant context of my current setup: This is the first version of the app adding in-app purchase subscriptions. In-App Purchase products are configured in App Store Connect, and marked as "Ready to Submit". The products are attached to the app version, and fully saved. A sandbox account is logged in on the test device. StoreKit Configuration local debug works fine — I can simulate purchases locally from Xcode. However, in the real sandbox environment, any attempt to fetch products returns no results. In App Store Connect > Agreements, Tax, and Banking, I currently see: Paid Application Agreement: Status = "Waiting for User Info" Banking Info: “In Progress” Tax Info: Not yet submitted ❓❓❓ My key question is: Does the "Paid Applications Agreement" need to be fully active (including bank + tax info complete) before in-app purchase products can be fetched in the sandbox environment? If so, it seems that this may be blocking my ability to: Test real subscription flows with sandbox accounts Pass App Store Review (since products cannot be loaded) Any clarification would be greatly appreciated! Thanks in advance.

I’m setting up a Product Page Optimization test, but there’s no App Icon tab to pick a different icon for each treatment. I ran a test like this a few months ago and had the App Icon tab, so I’m not sure why it’s missing now. All alternate icons work in my app (can switch between them) and are listed in the Catalog Compiler - Options › Alternate App Icon Sets build setting. Apple engineers: What are the requirements for the App Icon tab to display when creating a test? Everyone else: Could someone with an app with alternate icons start to create a Product Page Optimization test and tell me if you see the App Icon tab? I'd appreciate knowing if others are seeing this. 🙏 Here’s a screenshot from Apple’s Product Optimization Test doc showing the tab I’m missing:

I've looked everywhere in my App Store Connect dashboard and cannot find the section where I can do product page optimization for my app. I looked at some tutorials and in the forums but I don't see from my view in the dashboard to be able to follow the guide of finding this. Do I need to ask Apple to enable it for my app?

Apple just introduced a new Challenges feature in Game Center (WWDC 2025). I have Game Center enabled for my app and have working leaderboards (and achievements). Now I want to implement challenges (connected to my leaderboards). But the Game Center Challenges not showing in App Store Connect or Xcode 16.4 I have a working GameCenterResources file in Xcode and it allows me to add Achievement, Leaderboard, Leaderboard Set, but no Challenges. I'm based out of Europe. Any ideas?

In https://appstoreconnect.apple.com/business I only see the Free Apps Agreement which I already accepted, but the Paid Apps Agreement is not there. I am the account holder and already signed the new Apple Developer Program License Agreement, so those are not the reasons for this issue. I need to find and accept the Paid Apps Agreement because I have a subscription app on testflight which I want to publish to app store soon. Thanks in advance!

Our team is migrating from Apple Server Notifications V1 to V2. We have two primary questions regarding notification delivery during this transition: Is it possible to configure Apple to send V1 notifications to an existing V1 endpoint URL and V2 notifications to a separate V2 endpoint URL concurrently? If concurrent delivery to distinct URLs is not supported, what is the expected behavior for outstanding/pending V1 notifications when the notification endpoint URL is updated to the V2 URL? Are V1 notifications re-sent to the new V2 URL, or are they dropped?