Hi! We have a critical in-app launch coming soon and already missed one due to longer than expected review process. I even requested an expedited review last Saturday, but it's still "Waiting for review". We also have a patch version waiting that we would send to review right after the current one is approved. Or should we reject the current submission and submit the patched version (and request expedited review) or would that just drop us back to the end of the line? Help appreciated, thank you. 🙏

We submitted our apps on May 19, 2025, in order to make them available to our new customers. To date, we have heard nothing from the AppStore Connect team. We tried to delete the submission of one of our apps and try again the process on May 23, but this too was unsuccessful. The availability of these apps on the store is vital to the operation of our company, since our customers are eagerly awaiting their use, which is a drag on our sales. It's frustrating not to have a faster service, especially as we pay an annual fee, without having more information on potential slowdowns such as during the Christmas period. Any help or visibility would be appreciated Wishing you a good day and good luck to my fellow developers if you're in the same situation. Best regards,

Hi everyone, I’m having a recurring issue with App Review under Guideline 3.2.1(viii). Our app provides loan services, and we’re using a custom domain on our app's Product Page (e.g. support URL, marketing URL). To comply with the requirement that the domain must be clearly under our control and associated with Apple Accounts, we’ve: Verified the domain (e.g. exampleloanservice.com) via the apple-app-site-association file. Added an Admin user to our App Store Connect team with an email like admin[at]exampleloanservice.com. All URLs listed in the App Store metadata (support, marketing, privacy policy) use that same domain. The Account Holder is still using a personal email like companyname[at]gmail.com. Despite this, the app is still being rejected with the same message: "domains used on the Product Page must be under your control or ownership" My questions are: Is having an Admin user with the correct domain email enough? Or does the Account Holder email also need to be on the same domain to pass review? Would really appreciate insights from anyone who’s faced this and solved it. Thanks!

Hello We submitted our app for the first time about a week ago. Then there was the usual back-and-forth between Review and us, things we did not think of when submitting the app. One of those things was that our subscriptions were not being submitted together with the app. So we did that and submitted it again, and both the app and the subscriptions went into status "Waiting for Review". Then the app was rejected again for some other reason that had nothing to do with the subscriptions. But the subscriptions stayed at status "Waiting for Review" - and in that status, they cannot be added again to review. So we thought, maybe the subscriptions are still in review, so we do not need to add them again explicitly. But now the app gets rejected because we didn't include the subscriptions in the submission. I submitted the app again and added a comment about the situation. Now both the app and the subscriptions are in "Waiting for Review". What can we do? Any way to get the subscriptions back to "Ready for Review", so they can be added again? Thanks Jonas

Hello all, this is my first post in Apple's Developer Forums, so please let me know if I'm not providing enough or the correct information. I am a web developer and am trying to put a new version one of my team's applications (built in react native) up to be able to use Test Flight and begin testing on physical devices. I recently upgraded my MacOS to Sequoia 15.5, and have the latest Xcode 16.3. I have been able to build the react native application and run it on a simulator on my device. I have also set up the cert, provisioning profile and bundle identifier. The step I am lost at is that whenever I archive, and attempt to distribute app or even validate app, I get the following errors. Validation failed Missing required icon file. The bundle does not contain an app icon for iPhone / iPod Touch of exactly '120x120' pixels, in .png format for iOS versions >= 10.0. To support older versions of iOS, the icon may be required in the bundle outside of an asset catalog. Make sure the Info.plist file includes appropriate entries referencing the file. See https://developer.apple.com/documentation/bundleresources/information_property_list/user_interface (ID: 1bd64325-339e-44a5-8c60-70a476ebd395) Validation failed Missing Info.plist value. A value for the Info.plist key 'CFBundleIconName' is missing in the bundle 'bundlename'. Apps built with iOS 11 or later SDK must supply app icons in an asset catalog and must also provide a value for this Info.plist key. For more information see http://help.apple.com/xcode/mac/current/#/dev10510b1f7. (ID: 61a5c97f-9f49-4f97-a305-d4cf09bc3ce5) This happens no matter what I do. However, I have checked over and over again, and my info.plist file DOES have the appropriate key: CFBundleIconName AppIcon My AppIcon images are located here: project-root/ios/project-name/Images.xcassets/AppIcon.appiconset I have the following Contents.json { "images" : [ { "size" : "20x20", "idiom" : "iphone", "filename" : "icon-20-2x.png", "scale" : "2x" }, { "size" : "20x20", "idiom" : "iphone", "filename" : "icon-20-3x.png", "scale" : "3x" }, { "size" : "29x29", "idiom" : "iphone", "filename" : "icon-29.png", "scale" : "1x" }, { "size" : "29x29", "idiom" : "iphone", "filename" : "icon-29-2x.png", "scale" : "2x" }, { "size" : "29x29", "idiom" : "iphone", "filename" : "icon-29-3x.png", "scale" : "3x" }, { "size" : "40x40", "idiom" : "iphone", "filename" : "icon-40-2x.png", "scale" : "2x" }, { "size" : "40x40", "idiom" : "iphone", "filename" : "icon-40-3x.png", "scale" : "3x" }, { "size" : "60x60", "idiom" : "iphone", "filename" : "icon-60-2x.png", "scale" : "2x" }, { "size" : "60x60", "idiom" : "iphone", "filename" : "icon-60-3x.png", "scale" : "3x" }, { "size" : "20x20", "idiom" : "ipad", "filename" : "icon-20.png", "scale" : "1x" }, { "size" : "20x20", "idiom" : "ipad", "filename" : "icon-20-2x.png", "scale" : "2x" }, { "size" : "29x29", "idiom" : "ipad", "filename" : "icon-29.png", "scale" : "1x" }, { "size" : "29x29", "idiom" : "ipad", "filename" : "icon-29-2x.png", "scale" : "2x" }, { "size" : "40x40", "idiom" : "ipad", "filename" : "icon-40.png", "scale" : "1x" }, { "size" : "40x40", "idiom" : "ipad", "filename" : "icon-40-2x.png", "scale" : "2x" }, { "size" : "76x76", "idiom" : "ipad", "filename" : "icon-76.png", "scale" : "1x" }, { "size" : "76x76", "idiom" : "ipad", "filename" : "icon-76-2x.png", "scale" : "2x" }, { "size" : "83.5x83.5", "idiom" : "ipad", "filename" : "icon-83.5-2x.png", "scale" : "2x" }, { "size" : "1024x1024", "idiom" : "ios-marketing", "filename" : "icon-1024.png", "scale" : "1x" } ], "info" : { "version" : 1, "author" : "xcode" } } Those files all exist in the folder (there is an @ symbol in the names of the files, but I replaced with a - here because the forum thought I was adding mailto: addresses.) When I look on Xcode at the images, it looks like all required sizes are there. The file for 40-3x and 60-2x are both exactly 120x120 pixels. I cannot for the life of me figure out what is missing and what is wrong. I have tried different iterations of this whole folder and Contents.json, I have generated them using the generators based off of the 1024 image. I am wondering if something could have happened after I updated to the latest MacOS and Xcode versions. Any help would be greatly appreciated

Validation failed (409) This bundle does not support one or more of the devices supported by the previous app version. Your app update must continue to support all devices previously supported. You declare supported devices in Xcode with the Targeted Device Family build setting. Refer to QA1623 for additional information: https://developer.apple.com/library/ios/#qa/qa1623/_index.html (ID: 6ff0a33d-de2f-4c45-8d08-27557be36bee)

Hello, At my company, we're trying to run an App Store A/B test on alternate app icons. However, the App Store is rejecting the binary when we upload it (see email below). We're hoping someone out there knows the solution to this issue. Background Currently, our app is built with one target from amongst several different schemes. These schemes are used for various versions, including developer debug builds, TestFlight builds, App Store builds, and others. Each scheme has its own distinct app icon specified in Xcode, as shown in the image below: In our project, we've added the alternate app icons for the two App Store treatments as recommended according to Apple's documentation (we named them "AppIcon-T1" and "AppIcon-T2"). These are located inside our "Images.xcassets" asset catalog. Each alternate app icon's properties are configured as: iOS: Single Size macOS: None watchOS: None Appearances: None Gamut: Any The Problem After making the changes above, creating an App Store build succeeds as usual. However, every time we submit an App Store build, we receive this email from Apple: Please correct the following issues and upload a new binary to App Store Connect. ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons~ipad.CFBundleAlternateIcons contains an entry “AppIcon-Enterprise” that references asset “AppIcon-Enterprise.” No such asset is present in the asset catalog. ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons~ipad.CFBundleAlternateIcons contains an entry “AppIcon-Debug” that references asset “AppIcon-Debug.” No such asset is present in the asset catalog. ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons~ipad.CFBundleAlternateIcons contains an entry “AppIcon-T2” that references asset “AppIcon-T2.” No such asset is present in the asset catalog. ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons~ipad.CFBundleAlternateIcons contains an entry “AppIcon-T1” that references asset “AppIcon-T1.” No such asset is present in the asset catalog. ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons.CFBundleAlternateIcons contains an entry “AppIcon-Enterprise” that references asset “AppIcon-Enterprise.” No such asset is present in the asset catalog. ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons.CFBundleAlternateIcons contains an entry “AppIcon-Debug” that references asset “AppIcon-Debug.” No such asset is present in the asset catalog. ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons.CFBundleAlternateIcons contains an entry “AppIcon-T2” that references asset “AppIcon-T2.” No such asset is present in the asset catalog. ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons.CFBundleAlternateIcons contains an entry “AppIcon-T1” that references asset “AppIcon-T1.” No such asset is present in the asset catalog. Troubleshooting According to those error messages, the problem is that the alternate app icons aren't being included in the asset catalog. However, we've double-checked that everything seems to be correct in terms of project setup: The alternate icons are in our "Images.xcassets" catalog (just like our existing app icon) We made sure that "Include all app icon assets" is checked in our project file under ➤ General ➤ App Icons and Launch Screen The alternate app icons are specified as App Icons, not Image Sets The alternate app icons have their target membership set correctly The alternate app icons are in PNG format at 1024 x 1024 size If we remove the alternate app icons from the asset catalog and rebuild and resubmit, the App Store issue disappears. Any help appreciated. Thank you!

I use App Store Connect for over 3 years but since about May 9 I noticed two things: the sales of my apps reported by App Store Connect/Trends are down approx. 80% (this could be a coincidence but I hope the data is not up-to-date) an update of one of my apps seems to be stuck in "Waiting for Review" for a couple of days now (in the weeks/months before the review process would be very quick: done in a couple of days). Anyone else having these/similar problems lately?

We are a group of 10 friends using the same device and Apple ID, but each of us has a different account within the same app. We want to purchase the same auto-renewable monthly subscription plan, each using our own app credentials. The issue: after the first person subscribes, the next user (with a different in-app account) is unable to buy the same plan—it shows "already subscribed" and only allows access after the next billing cycle. We don’t mind the auto-renewal being charged each month by a different person. We just want each app account to have access to the same package independently, for 1 month each. How can we achieve this without changing the Apple ID or device?

I hope this message finds you well. I’m reaching out to ask whether specific App Store Connect metrics available in the App Analytics dashboard can also be accessed via the App Store Connect REST API. I have reviewed the official API documentation, but I couldn’t find confirmation regarding the metrics listed below. Could you kindly clarify if the following metrics are available through the REST API? And if so, could you point me to the relevant endpoints or documentation? From the "Usage" group: Installations (Opt-in only) Active Devices Deletions (Uninstalls) From the "App Store" group: Impressions (Unique Devices) Product Page Views (Unique Devices) If these metrics are not available via the REST API, is there an alternative method to programmatically access or export them? Thank you very much in advance for your help and guidance.

I am trying to add in-app purchases to my app. I created a StoreKit Configuration file and checked the option 'Sync this file with an app in App Store Connect' because I have already completed the subscription setup in my Apple Developer account. I also tried implementing the in-app purchases directly without using the StoreKit Configuration file, but I’m getting an 'Invalid Product Identifiers' error. I’ve double-checked, and the product ID matches the one listed in my Apple account. Please guide me on what I should do.

Hello everyone, We are seeing some warnings in Xcode 16 when I archive my iOS app for distribution. During the upload phase (either via Xcode Organizer ), I get an error like: WARNING: Upload Symbols Failed The archive did not include a dSYM for MyFramework.framework with the UUIDs: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX Ensure that the archive’s dSYM folder includes a DWARF file for MyFramework.framework with the expected UUIDs. Question: How can these warnings be fixed? Is this warning safe to ignore if I know the vendor does not supply a dSYM for their framework? If I do need a proper dSYM for full symbolication, how should I request it from the vendor or generate it myself from an XCFramework?

I am using the public url https://api.storekit-sandbox.itunes.apple.com/inApps/v1/notifications/jwsPublicKeys to get the jwks keys to verify the signed payload for store kit payments. I am checking Apple server notifications. const APPLE_JWKS_URL = "https://api.storekit-sandbox.itunes.apple.com/inApps/v1/notifications/jwsPublicKeys" // Apple JWK set (cached by jose) const appleJWKS = createRemoteJWKSet(new URL(APPLE_JWKS_URL)); const jwks = await appleJWKS(); logger.debug("Apple JWKS Keys: %O", jwks); // Log the keys if (!signedPayload) { // return res.status(400).json({ error: "Missing signedPayload" }); } // Step 1: Verify JWS (signature + payload) using Apple's JWKS const { payload, protectedHeader } = await jwtVerify( signedPayload, appleJWKS, { algorithms: ["ES256"], // Apple uses ES256 for signing } );

I published a new iOS app recently and now I want to publish macOS app. The app is built in SwiftUI and macOS target is enabled using Mac Catalyst. While costomizing my macOS app page in App Store Connect I can edit most of the fields except unchecking "Sign-In Required" checkbox and entering contact details. If I uncheck "Sign-In Required" checkbox and press Save I get this generic error: "An error has occurred. Try again later.". Inspecting Console I can get this information: { appName: "appstore", payload: (1) […], eventKit: "logger", env: "PROD" } ​ appName: "appstore" ​ env: "PROD" ​ eventKit: "logger" ​ payload: Array [ {…} ] ​​ 0: Object { logLevel: "ERROR", message: "API Response Error: SAVE_APP_REVIEW_DETAILS_RESPONSE", url: "https://appstoreconnect.apple.com/apps/6739671911/distribution/macos/version/inflight", … } ​​​ componentStack: undefined ​​​ errorCode: undefined ​​​ logLevel: "ERROR" ​​​ message: "API Response Error: SAVE_APP_REVIEW_DETAILS_RESPONSE" ​​​ stackTrace: "status code: 409 --- api correlation key: " url:"https://appstoreconnect.apple.com/apps/6739671911/distribution/macos/version/inflight" I contacted Apple support but they weren't quite useful and told me to ask people on forums... I don't believe this will help as clearly something is wrong with App Store Connect and the state of my account needs to be fixed on their end.

After creating the code on app store connect, I received the email with the zip file that is supposed to include my coupon code but there is no code just the terms which is list of countries, the date the code ends, and who is providing the code (me). I tried using the name of the file or partial name of the file but was denied on app store. **Where is the code? **

Hello, We’re seeking urgent help or guidance regarding a serious issue with our app review process. We submitted our iOS app last month. It was rejected three times for various reasons, and each time we promptly resolved the issues and resubmitted. After the most recent resubmission (over a week ago), the app has been stuck in the “Waiting for Review” status. The last communication we received from Apple was: We’ve tried to follow up multiple times via email, as phone support is not available in our country. However, we’ve only received automated responses saying that the review requires additional time. No actual progress or update has been communicated since then. Our launch date is now critically close, and we're concerned that we may miss it due to the continued delay and lack of visibility into the review timeline. If anyone from the App Review team is reading this, or if any developers have been through a similar situation and can share advice, we would deeply appreciate your input. Thank you for your time and support.

Hello everyone, I’m hoping the community (and maybe someone from App Review) can point me in the right direction. I submitted my new game on 22 April 2025. The build was rejected, so I filed an appeal the same day and re‑submitted it twice after that. The appeal has shown “Waiting for Review” ever since, and I’ve never received the usual “We got your appeal” email, just the generic “We’re seeing higher volume” message. Although this is a fresh developer account, I’ve shipped 50+ apps for other organizations over the years and never ran into a delay like this, so I’m pretty sure the hold‑up isn’t about the actual build. Why it’s urgent:
Influencer promos, community streams, and some paid ads were all timed around the original launch window. After four weeks of silence people assume the game’s been cancelled, and traffic/comments are sliding fast. What I’ve tried so far: Emailed App Review → same volume auto‑reply Used the Contact Us form twice Added a short note in Resolution Center every few days If anyone from App Review sees this or if another dev has broken out of a similar appeal limbo any tip or nudge would be hugely appreciated. Thank you in advance for your time.

Hi, Since Friday 18 April 2025, around 9am, my team and I have been unable to manage one particular app in App Store Connect. Whenever we open the app’s page and try to view “General → App Information,” or when we press “Add for review” on the current iOS version, App Store Connect immediately displays “Something went wrong. Try again later.” and the content never loads. The error occurs every single time, in both Safari and Chrome on multiple Macs, while all our other apps in the same developer account behave normally. Our build and submission tooling (Fastlane) hasn’t changed for more than a year and continues to work for the rest of our apps. Every attempt to open App Information or submit the version fails. I have already opened a ticket ~1 month ago and shared all the screenshots, screen recordings and .har files but seems like really take their time to fix things. It feels like a server-side issue isolated to this single app, so any guidance or a manual unblock would be greatly appreciated.

Hello guys, I currently have a problem with Xcode cloud. When I setup a simple workflow in my Xcode project that just archives it and builds the project for TestFlight Internal testing, it will fail and give the following error: Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “DropIn.app/DropIn” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing. I've already been searching for solutions and double checked the documentation. My Xcode project is a simple iOS app with the app target and two other targets for tests and UI tests. I made sure the checkbox "Automatically manage signing" is ticked in all targets. The workflow has only one action "Archive - iOS" with TestFlight (Internal Testing Only) and a post-action "TestFlight Internal Testing - iOS" with an internal testing group assigned. I've seen people having similar problems where it turned out they had a non roman character in their name? This would also affect me if that's the case, since my name includes "ö". I also checked on app store connect and already deleted xcode cloud data, removed all certificates recreated the workflow, but it still gives this error. Any ideas on how to fix this?

I recently incorporated a new company to publish a couple apps but I’m unable to enroll on the developer program. i tried paying via the web but the payment wasn’t coming through even though the card I’m using is active. I reached out via email and they asked me to enroll via the app instead. problem is that the enroll button is always disabled! is someone else having the same issue? do you know how to fix it?