I am unable to link my new non-consumable In-App Purchase (idea_think_pro) to my draft update page (iOS 2.0.0).The product is fully configured with required screenshots and metadata, and displays the blue "Add for Review" button. However, clicking it shows the hard validation block: "Your first non-consumable in-app purchase must be submitted with a new app version."Simultaneously, the "In-App Purchases and Subscriptions" section is completely missing from my iOS 2.0.0 version page, even when no app build is attached. I have cleared all active submissions and browser caches. Please manually link Product ID idea_think_pro to App Version 2.0.0 on your database or reset my version layout cache.

I click in App Store Connect to view my app but there is a dns error. Tried Brave and Safari but have the same result. I just did update my Mac to Tahoe 26.4 . This site can’t be reached olympus-int.itunes.apple.com’s DNS address could not be found. Diagnosing the problem. DNS_PROBE_POSSIBLE

An unexpected error was encountered when submitting for review. If the issue persists please contact us I can no longer submit iOS app for review. Always show this error. I am using Safari latest version - 16.4 MacOS Version - Ventura 13.3.1 Xcode - 14.2 Appreciate any leads. Thank You!

Trying to add subscriptions to a new app (Had a few versions already approved). Keep getting this message with no way to select the app version in the draft box that pops up. "Unable to Submit for Review Your first subscription group must be submitted with a new app version. New subscription groups must be submitted with an auto-renewable subscription from within that group." I have reached out to apple who haven't responded at all yet.

Well, here we go again. The subscription items are rejected because I have not submitted a binary. (Except I have, of course.) The binary is rejected because I have not submitted the IAP subscription items. (Except I have, of course.) Neither lets me submit the other again alongside it. Brilliant system.

Dear Apple Support, Our company owns the trademark of AVATR. Due to regional regulations and local cloud service suppliers, we authorize overseas distributors to use separate developer accounts to launch our AVATR app. Previously multiple accounts could use the same name, but now the system says the name is taken. We need your help to confirm: Is there a new rule restricting identical app names across different developer accounts? Please share relevant policy updates. Can we file a trademark claim to get permission to use AVATR on multiple authorized accounts? What documents do we need to submit for the claim? We can provide trademark certificates, authorization letters and links of our live AVATR apps for verification. Thank you.

Im trying to add my build for review yet there is no upload option listed. does anyone have any suggestions or experience with this if so what did you do to res this proble?

Hi everyone, Has anyone had an app version approved while the subscriptions submitted alongside it were left behind in review? I submitted a new version of my app together with two replacement auto-renewable subscriptions. The app itself was approved yesterday, but both subscriptions still show Waiting for Review. Both subscriptions are fully configured, connected through RevenueCat and work correctly in TestFlight. However, because they have not been approved for production, the live app cannot load the plans and users cannot start a trial or subscribe. This follows a previous issue where my original monthly and annual subscriptions became stuck In Review for several months. Those original products are still stuck, so I now have: Two original subscriptions stuck In Review Two replacement subscriptions stuck Waiting for Review An approved live app with no working subscription products I have contacted Apple Developer Support multiple times, requested escalation and submitted a Feedback Assistant report, but I have not received a resolution. Is it normal for Apple to approve the app version without reviewing the subscriptions included in the same submission? Has anyone found a way to get the subscriptions manually routed to the In-App Purchase review team? This has blocked all subscription revenue for my live app, so I would really appreciate any advice.

Hi all, We're seeing an odd search behavior on the iOS App Store app. When users search for "Prontus" (the exact, correctly-spelled name of our published app), the App Store auto-corrects it to "Patronus" and shows unrelated apps in the results, with only a small "Search for Prontus instead?" link to reach our actual listing. App affected: Prontus - https://apps.apple.com/br/app/prontus/id6760715818 Region observed: Brazil (App Store, pt-BR), iOS App Store app, iPhone Steps to reproduce: Open the App Store app on iOS. Tap the Search tab. Type "Prontus" (no typos). The App Store shows "Mostrando resultados para patronus" and unrelated apps instead of ours. Users have to notice and tap the small "Ao inves disso, buscar Prontus?" link to reach our app. Interestingly, this does not happen on the App Store web listing (apps.apple.com) - searching "Prontus" there correctly returns our app as the first result. So it seems specific to the App Store app's search/autocorrect behavior on iOS. Since "Prontus" is spelled correctly and is a live, unique name in the catalog, I'd expect search to surface it directly rather than auto-correct to an unrelated, more popular term ("Patronus"). This is hurting our discoverability. I've also filed this through Feedback Assistant (FB24071198) and Contact Us (case 20000123768847). Has anyone else run into App Store search auto-correcting a correctly-spelled app name to something unrelated? Any known fix or workaround would be very welcome. Thanks!

Hi everyone, I want to confirm whether iPad screenshots are mandatory when submitting an app to the App Store. nshots required only when the app supports iPad, or must every iPhone app also provide them? Also, if the app can technically run on iPad but is not specifically designed for it, should I upload iPad screenshots or disable iPad support before submission? Any clarification from developers who have recently submitted an app would be helpful.

I have a newly enrolled individual Apple Developer Program account (Team ID 798MLWU9L7) and I cannot upload my first build to App Store Connect. Every attempt fails with: Error 90034 — "Missing or invalid signature. The bundle 'com.gestaolocadoras2k.app' at bundle path 'Payload/....app' is not signed using an Apple submission certificate." I have already verified and ruled out everything on my side: The build is signed with a valid "Apple Distribution" certificate (a regular one, NOT a "Distribution Managed" cert). Entitlements show get-task-allow = false and beta-reports-active = true. I use a manually created App Store provisioning profile bound to that Apple Distribution certificate. WWDR intermediate certificates (G3 and G6) are present and valid in my keychain. I recreated the distribution certificate and the provisioning profile from scratch. It fails identically through BOTH Xcode Organizer AND Transporter (same error, Validation failed 409 in Transporter). My Developer Program membership is Active (renews July 2027). The "Free Apps" agreement is Active in App Store Connect; there are no pending agreements and no pending License Agreement banner. Apple System Status shows all relevant services operational (no outage). The account is ~6 days old and I have waited several days. Since the signature is valid and two independent tools reject it the same way, this looks like a backend account-activation issue rather than a signing problem. Could an Apple engineer please check my account? Team ID: 798MLWU9L7 Bundle ID: com.gestaolocadoras2k.app App Store Connect app ID: 6794145294 Thanks in advance.

Last week I've submitted a new update for review doing the standard procedure for iOS, Mac and Vision. When submitting them both the Mac and Vision App switched to Waiting for Review state but the iOS one got stuck in Ready for Review state. I've tried a few times canceling the submission and submitting again and it always gets stuck in the "Ready for Review" state. Under the App Review section shows as Waiting for Review but on the general page shows Ready for Review. I've tried using the App Store Connect the API and the same thing happens. Any suggestions how to fix this?

Hello, I'm the developer of FOS Social (Apple ID: 6755471015), a creator-membership marketplace currently in TestFlight. I've submitted the Advanced Commerce API access request form twice and have not received any response, confirmation, or status update. My most recent submission has Request ID: UVQ7FUZVV3. Our use case: FOS Social is a social platform where viewers subscribe to individual content creators through independent auto-renewable monthly subscriptions across three tiers ($10 / $17 / $29). A single viewer must be able to hold concurrent active subscriptions to multiple creators at the same tier — for example, subscribed to Creator A at Gold and Creator B at Gold simultaneously. This matches Apple's stated eligibility model for the Advanced Commerce API: "exceptionally large catalogs of subscription content — apps that include frequently added content from multiple creators, where each creator's offering is merchandised as a single auto-renewable subscription." Why standard StoreKit doesn't work for us: We currently reuse one product ID per tier across all creators (e.g. com.fosssocial.creator.gold.monthly). When a viewer already subscribed to one creator at Gold tries to subscribe to a second creator at Gold, StoreKit returns "already subscribed" and treats it as a renewal rather than a new independent subscription. Pre-creating a separate subscription group per creator in App Store Connect is not feasible since our creator base is dynamic and growing. My questions: Is there any way to check the status of an Advanced Commerce API access request, or a typical response timeframe we should expect? Is there anything that commonly causes these requests to go unanswered (e.g. submission not made by the Account Holder, app still in TestFlight, missing information)? Is there a recommended escalation path when the request form has been submitted multiple times with no reply? I've also opened a support case (Case ID: 102934491974) but wanted to ask here as well in case anyone from the community or Apple has guidance. Thank you!

Why will screen captures from the iPhone simulator not upload to the App Store Connect? Why does Apple make ANYTHING Apple so flipping hard? Why do I need screen shots for a business only app?

Hoping to get some perspective from others who've dealt with this, since our written appeal, a follow-up with corrections, and a support ticket all led to the same templated response. Timeline: All apps on our account were removed and the account was placed in "Pending Termination" status, citing Section 3.2(f) — misleading auto-renewable subscription practices (purchase flows, "scareware" tactics, misleading metadata). We submitted a detailed written appeal explaining our subscription flows use standard StoreKit pricing with no urgency/countdown elements, and requested the specific app, build, or screen the finding was based on. We proactively re-reviewed our purchase flows anyway, found and corrected a couple of elements that could be seen as borderline (a reference-price/strikethrough on one offer screen, a slightly harder-to-dismiss win-back screen), submitted a corrected build, and detailed the fixes in a follow-up to App Review. Final answer: same boilerplate language, no specifics on which app/build/screen triggered it, account formally terminated, directed to the Re-instate a Terminated Developer Program Membership form and/or a P2B Regulation complaint (we're EU-based). Questions for anyone who's been through this: Did providing more detail/corrections in your appeal ever get you a more specific response, or is the templated language just what everyone gets regardless? For those who used the Re-instatement form after a full termination (not just "pending") — did it ever work, and roughly how long did it take? Appreciate any real experience — trying to figure out whether to keep pushing on the reinstatement path or focus our energy on other platforms.

I submitted my Solana memecoin trading app to the App Store and I was returned with they reply "- If you intend to distribute the app in the United States, provide a copy of your Money Services Business (MSB) registration. Additionally, confirm that you will restrict the app's availability to the states listed on your MSB registration." When I looked into it, it seems the MSB registration would mean a money transmitter license along with it. These are insanely expensive, and I know for a fact that other crypto apps did not all go through this for every state. I use a third party API for all transactions and keys are stored on the users devices, so I don't even understand the requirement for a transmitter license if the app never even handles money. I have been on hold with apple phone support for 2 hours (seems it doesn't work) when I replied with the App Store Connect with my questioning they just resent the same message which frustrated me. Can anyone offer some guidance here?

Summary After setting a single auto-renewable subscription product (not the app) to "Developer Removed from Sale" in App Store Connect, the next scheduled renewal for an existing active subscriber failed with DID_FAIL_TO_RENEW v2 and expirationIntent = 5 ("expired for some other reason"). I expected expirationIntent = 4 ("product wasn't available for purchase at the time of renewal"), since the product was, in fact, not available for purchase. I would like to confirm whether 5 is the documented/expected value for this scenario, and how to deterministically distinguish "developer removed product from sale" from other renewal failures using the notification payload. Reproduction / observed sequence Day 15: Changed product annual_promo (auto-renewable subscription) status from "Approved" to "Developer Removed from Sale" in App Store Connect. The app itself remained Approved and on sale. Other subscription products in the same group remained Approved. Day 16: An existing active subscriber on that product had a scheduled automatic renewal date. Result: Renewal did not occur. We received a DID_FAIL_TO_RENEW v2 notification. Payload (relevant fields): JWSRenewalInfoDecodedPayload.expirationIntent = 5 JWSRenewalInfoDecodedPayload.autoRenewStatus = 0 Questions Is expirationIntent = 5 the correct/expected value when a renewal fails because the developer removed the product from sale? Or should it have been 4 ("product wasn't available for purchase at the time of renewal")? If 5 is intentional, what is the engineering rationale for not using 4 in this scenario? Given that expirationIntent = 5 is documented as a catch-all ("some other reason"), which other fields in the DID_FAIL_TO_RENEW payload (e.g., subtype, autoRenewStatus, gracePeriodExpiresDate, signedTransactionInfo) should we inspect to deterministically classify the failure cause and isolate "developer removed product from sale" from billing failure / customer cancel / price-increase not accepted / etc.? Context I'm aware of the docs page In-App Purchase statuses and Set availability for an auto-renewable subscription, but they describe the status semantics, not the resulting notification payload. Product has been reverted to "Approved" to avoid further impact on subscribers while this is clarified. Thanks in advance.

Hi everyone, I’m looking for advice on the best escalation path for an App Store Connect tax issue that is blocking our Paid Apps / In-App Purchase setup for a live app. Timeline: Jun 18, 2026: Opened a Finance Support case for tax information submissions. Since then: No update from Apple Finance. Current impact: Paid Apps / IAP cannot be completed, and users are already trying to purchase the Pro upgrade. I have also submitted a new Finance contact request under Tax information submissions. Has anyone dealt with a similar App Store Connect tax issue where Finance Support went quiet? Is there any escalation path beyond the Finance contact form and replying to the original iTSPayments email? Any guidance from Apple staff or developers who have been through this would be appreciated.

When submiting my W-8BEN (US Tax Forms) my citizenship is automatically set to Australia. This is incorrect as my citizenship is in Germany, but the issue is that I can not change the citizenship section because it greyed out and I can not select it. Can someone please provide me with advice as to how I can change my citizenship.Thank you

My trader status has been "in review" for over a month now. It feels like it's stuck. Apple support doesn't answer emails and I cannot schedule a call with them, because the supposed form to do so doesn't exist. I cannot find it. Anywhere.