Hello Apple App Store Team, I hope you’re doing well. I recently submitted an App Store feature nomination for my app and wanted to kindly ask if there is any update available regarding its review or consideration. Nomination ID: d617fde8-d5a9-4535-8984-17f4b246b301 https://apps.apple.com/us/app/metime-self-care-for-women/id6762885738 I completely understand that featuring decisions are editorial and not guaranteed. I just wanted to confirm whether the nomination has been received successfully and if there is anything else you need from my side to support the review. Thank you for your time and consideration.

I set up all the App Store details, including support info and other required information, but I’m having an issue when adding a build and trying to save. The Save button turns red, and I’m not sure why. It’s not showing what I’m missing in the setup.

Hello Support Team member - I hope you are having a good day. My app has been approved and I manually released it 8 hours ago. Currently users do not see the subscriptions available on the paywall, and the subscriptions do not show up under in-app purchases in the app store. When I look at my subscriptions in AppStoreConnect - they say "Missing Metadata". When I look inside the subscriptions - one of the two has a localization that is showing a status of "Prepare for Submission". The other subscription does not have a localization - and there is nothing within the subscription that has a yellow warning alert. How can I resolve this? Thank you much!

I am unable to submit any app for review. Every attempt to add a build to an App Store version results in a 409 error, both through the App Store Connect website and directly through the App Store Connect REST API. Affected accounts: Account 1: My personal Apple Developer account Account 2: A company-owned Apple Developer account where I have Admin access Both accounts are completely separate — different legal entities, different enrollments — but exhibit the exact same behavior simultaneously. API errors observed When calling PATCH /v1/appStoreVersions/{id}/relationships/build: 409 ENTITY_ERROR.RELATIONSHIP.INVALID "The specified pre-release build could not be added." When calling POST /v1/appStoreVersions to create a new version: 409 ENTITY_ERROR.RELATIONSHIP.INVALID "You cannot create a new version of the App in the current state." What I have verified All builds are processingState: VALID and not expired usesNonExemptEncryption: false is set on all builds No build is already attached to another version Build version string matches the App Store version (1.1.0) App bundle ID matches the build bundle ID Localization, review contact details, and keywords are all filled in Banking info in Agreements, Tax, and Banking was recently updated on both accounts Issue persists on both the website and via the REST API, ruling out a browser/cache issue Question Has anyone seen 409 errors affecting two completely separate developer accounts simultaneously? Could there be a platform-level issue with App Store Connect that is not reflected on the System Status page? I opened a support ticket 1 week ago but I only got a reply today and it's just asking for more details.

Our app (id 1611398578) has been stuck "In Review" in App Store Connect for 15 days, after being approved quickly by App Review. We contacted Apple Support multiple times through email and phone, but we did not receive any response. Today we tried re-submitting a new version hoping it will trigger a system reset and fix the issue. The submission for iOS was approved very fast by App Review, but it is again stuck "In Review". PLEASE APPLE HELP US GET THIS ISSUE RESOLVED!

Hello, after updating to Xcode 26.4.1, our app is rejected on App Store Connect because of the following error: ITMS-90429: Invalid Swift Support - The files libswiftCompatibilitySpan.dylib aren’t at the expected location /Payload/AlbusAir.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it. We did not change anything to the code, we didn't update any dependency. As far as I'm aware, we don't use Spans in Swift. I even tried copying the dylib myself in the app in a Xcode build phase and it still doesn't work. Can someone help? Thanks !

Hi everyone, I'm looking for advice from people who have done this before. Situation: I have an app under Developer account A. It has only been distributed via TestFlight (internal + external, including Beta App Review approval). It has NEVER been released on the public App Store. I want to move this app to my Developer account B before the public launch. Since App Transfer requires a prior App Store release, that option is off the table. My plan is simply to create a new Bundle ID and a new app record on account B, and resubmit from scratch. My questions: Bundle ID / app name conflicts Has anyone experienced issues reusing an app name that was previously used on another account (even if never publicly released)? Does the name stay "reserved" somehow? Beta App Review history — Does Apple's review system flag a resubmission from a different account if the binary is essentially the same app? Any risk of extra scrutiny or rejection because "this app already exists" somewhere in their system? TestFlight testers — I assume external testers will need to reinstall from a new TestFlight link. Is there any way to migrate them, or is it a clean slate? Cleanup on account A — Should I fully delete the app + Bundle ID on account A before creating the new one on account B, or does it not matter since the Bundle ID will be different anyway? Anything else I'm missing? — Hidden gotchas, signing issues, push notification certs, provisioning profiles, anything that bit you when doing something similar. Thanks in advance for any insight.

20 days passed since I released the app. According to Trends it has 30+ installs and 10 In-App purchases. When will I finally get analytics? Can't wait to see it, because I'm actively promoting my app and I wish to know the marketing performance. All that I see now in App Store Connect is this message: Other apps have no signs of this issue, I assume that the analytics is missing because the app is new. The question is "when"? :)

I cant upload a new binary, because it was already in review for my old subscription that was rejected. It just stayed in review. I don't have an " In app purchase", but have a subscription with a 3 day trial. It seems like if I dont add an "In app Purchase" then it never goes to review and never loads a binary. I made up one to force it, so I could select the one Im using a "subscription with a 3 days trial " that I needed (that seemed to work) and now I cant get it out for the new binary. Anyhow, Im fairly new at this, but enjoy it. sorry if its a remedial question in advance (yes my paid agreements are active and good) thank you for the help;)

My app is: 6757429647, Most of reviews went successfully within 2 days but this one its waiting for review for almost 6 days, what might be the issue? I'm waiting for a reply from Apple team

Started 4 weeks ago, can't submit new apps even now. Waiting for "we are looking into it." with no follow up. Thank you,

hi i have created an app that has been approved by apple but to be approved in europe (eu) something else is required. i have been waiting now for 8 weeks, does anyone know why it is taking so long or how long it usually takes?

I have a new app which has been submitted for review, and has been rejected.. The tester unable to see subscription settings.. He/she has not looked very far, they are in the app settings tab, and that was noted in the app submission. The likely issue is that this is an iPhone app, and specifically not for iPad.. Yet the reviewer used an iPad to test! This is the third consecutive rejection for administrative issues which have nothing to do with the app itself, and which, if the reviewers were to look properly, are not actually issues at all. This feels as though the reviewers are trying to get through as many reviews as possible in the shortest time possible, and not taking the time to examine an app submission properly. They are undermining months of hard work with a 30 second scan.

I am trying to enroll for the Apple App Store as an individual & sole proprietor. After reviewing and agreeing to the conditions, I clicked "Continue," but the page displays the following error message: "We are unable to process your request." Could you please help me resolve this issue? Thank you for your support. Best regards,

Hello, I am currently testing In-App Purchase subscriptions and encountered an issue where one of my products is not being returned. I have configured four subscription products: Annual 6 Months 3 Months Monthly All products were created and set to be available on the same date in App Store Connect. However, when fetching products using StoreKit, only three products (Annual, 3 Months, Monthly) are returned. The 6 Months subscription is missing and does not appear in the response. I have confirmed the following: All product identifiers are correct and match the code All products are in "Ready for Sale" status Agreements, tax, and banking information are completed The issue occurs consistently in the sandbox environment Could you please help me understand why only the 6 Months subscription is not being returned? Thank you.

When I click in Distribute button after selecting App Store Connect, I'm receiving the following error message: App Record Creation failed due to an invalid attribute. Request failed with error code "ENTITY_ERROR.ATTRIBUTE.REQUIRED", and reason "The provided entity is missing a required attribute You must provide a value for the attribute 'companyName' with this request" How can I fix this "companyName" atribute, since the organization name field is already filled correctly in my account information? Thanks!

Hi Apple Developer Community, I’m encountering an issue with complications (复杂功能) in my Apple Watch app after releasing it to the App Store. Here’s the scenario: During development and TestFlight testing, complications work correctly. Users can add the custom watch face from the iPhone and all complications display properly. After releasing to the App Store, when users try to add the same custom watch face from their iPhone, they see the error: “Complications Unavailable”​ (复杂功能不可用). However, if users add the watch face directly from their Apple Watch, complications load and work normally. Environment Details: watchOS: 26.3 iOS: 26.3.1 Xcode: 26.2 Distribution: App Store (release build) What I’ve tried so far: Verified that the complication data source is properly configured in the WatchKit extension. Confirmed that the app’s bundle ID and App Groups are consistent across debug and release configurations. Ensured that the complication entitlements and privacy permissions are declared in both iOS and watchOS targets. Tested with multiple devices and different Apple Watch models—the issue persists only when adding the watch face from the iPhone (App Store build). Key Question:​ Could this be related to how the iOS-Watch complication handshake is validated in App Store builds? Or is there a known issue with complication availability when the watch face is added via iPhone vs. directly on the watch? Any insights, debugging tips, or references to similar resolved issues would be greatly appreciated. Thank you!

I added an Apple In-App Event for the App Store on March 31, and it has now been more than 18 days. However, I am still not seeing any analytics data for the event in App Store Connect. I wanted to check if this delay is normal or if I might be missing something. Has anyone else experienced this issue? Are there any specific requirements, settings, or reporting delays I should be aware of for In-App Event analytics? Any guidance would be appreciated. Thanks in advance!

Hi all — this is genuinely urgent for us and I'd really appreciate any help. We've been fully blocked from shipping updates for almost two weeks, and Feedback Assistant has been completely silent. Posting here as a last resort to get the issue in front of someone who can route it. Our app (1.0.0 live on App Store, CN region) has a version record stuck in a broken backend state since April 9. Every recovery path fails at the Apple backend layer. Version record ID: 00ae0692-f94d-4632-a369-a9b230788330 Case: #102865399563 Symptoms via ASC web UI: Version shows "Prepare for Submission" Save fails with red error icon, no message shown DevTools Network shows: 409 ENTITY_ERROR.RELATIONSHIP.INVALID on /data/relationships/build "+" button to create next version is hidden while this record is in "Prepare for Submission" state Symptoms via ASC API (all paths tried, all 409): DELETE /v1/appStoreVersions/{id} → 409 STATE_ERROR "Only the first version of any platform can be deleted" PATCH /v1/appStoreVersions/{id}/relationships/build with 4 different valid builds (71 / 73 / 74 / 78) → 409 ENTITY_ERROR.RELATIONSHIP.INVALID on each PATCH with null (clear relationship) → 204 success PATCH to re-set relationship after clear → 409 again GET confirms versionString is still "1.0.3" in backend even though UI shows "1.0.4" after a rename attempt What we need: Either (a) Apple engineering resets this version record, or (b) official guidance that we can abandon it and create 1.0.5 (the "+" button is currently hidden, so this path is blocked from our side too). All builds (71, 73, 74, 78) are VALID in TestFlight. The blocker is purely the broken backend state on this version record — not our builds, not our code. Thank you so much to anyone who takes the time to read this or help route it. If any Apple engineer here can escalate Case #102865399563 to the right team, it would mean a lot — we've done everything we can from our side and are just stuck waiting. Any advice from fellow developers who've seen similar 409 issues would also be hugely appreciated. Thanks again 🙏

I'm trying to test using different icons in the product page optimization section, with each page using a different icon. However, even though I've added the icons to "Resources" and checked "Include all app icon resources" in "General," the icons still don't display when creating a test in the App Connect section after official review. How can I make this feature work correctly?