We have two sets of screenshot images for 5.5 and 6.5 displays of the iOS app which needs a new version. When I first uploaded the screenshot set for the 6.5 display, it looks all good. Then I uploaded another set for the 5.5 display and headed back to check 6.5 images. I found some of them reported errors IMAGE_TOOL_FAILURE. Then I deleted all 6.5 screenshots, re-uploaded for the 6.5 display again. However, this time 5.5 had errors. It is like a loop. I tried tens of times. And, if I upload 6.5 first, it all looks good. And then I go to another tab, for example, the app information tab and then come back. I also find the images are marked as 'The file has been uploaded and is processing ' .

Hi,Having issues uploading our build to App Store Connect for use in TestFlight. We get a success when building through Xcode, but we get an email after it uploads via archive manager stating "ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it.". We have confirmed that we don't have any Swift dependencies and that we are running the latest Xcode (v11.3.1). We've also tried to build/deploy this on multiple computers with the same error. Our app was built using Unity, then brought into Xcode to build/deploy from there. We have never had any Swift dependencies in our project. We are able to deploy directly to our devices, but it seems that the only time we run into issues is trying to. Any help is appreciated.

I got message in "AppStore connect" saying that there is a new version of the new version of the agrrement (Your Paid Applications agreement has a new version)When clicking on the "Agree" button for the renew for the Paid app agreement i get an error message saying there is a problem, but not what problem,. This is the error message. "We are currently unable to process your request. Please try again later."Ive gottten this message for several weeksl I have been trying different versions, with the same result. I even tried to send a support case to apple, but the request has been unanswered for 3.5 weeks now. I diont know what to do..

Xcode 26.2 RC has been out for over 24 hours and it's still not possible to submit apps.

Hi everyone, we are currently facing an issue with one of our apps regarding the new icon requirements in iOS 26. • We created the app icon using Apple’s Icon Composer. • On the device, everything works perfectly: the app icon is shown on the home screen, and it can also be customized with the new iOS 26 features (colors, transparency, etc.). • However, in TestFlight the app icon is not displayed at all (in the TestFlight app on the device). • In App Store Connect, the icon is also not shown in the overview for the app. Interestingly, within the list of TestFlight builds in App Store Connect the icon is visible. What we have tried so far: • Created an archive and manually uploaded it to App Store Connect → no icon in TestFlight. • Took the working Icon Composer asset from another app target where everything works correctly, deleted the old one in this project, and copied the working asset into the problematic target. → Same behavior: visible on the device, but still missing in TestFlight and App Store Connect overview. In contrast, in another app (using the same workflow and also Icon Composer), everything works perfectly: the icon shows up on the device, in TestFlight, and in App Store Connect. Has anyone experienced a similar situation? Is there something specific that needs to be set in App Store Connect (e.g. Marketing Icon / Branding section), or could this be related to the new iOS 26 icon handling? Any help or hints would be greatly appreciated. Thanks in advance!

Will RC be allowed to upload to App Store Connect? I have tried a couple of times with 17A321 and I keep getting unsupported SDK or Xcode version. Submitted feedback FB20178551

I'm experiencing a contradictory validation issue with DeviceActivityReportExtension that creates an impossible situation: The Problem: Without NSExtensionPrincipalClass in Info.plist → App Store Connect rejects upload with: "Missing Info.plist values. No values for NSExtensionMainStoryboard or NSExtensionPrincipalClass found" With NSExtensionPrincipalClass → Local install fails with: "defines either an NSExtensionMainStoryboard or NSExtensionPrincipalClass key, which is not allowed for the extension point com.apple.deviceactivityui.report-extension" Setup: Extension point: com.apple.deviceactivityui.report-extension Using SwiftUI with @main attribute and DeviceActivityReportExtension protocol Xcode 16.2, iOS 17.6 deployment target Code structure: @main struct SpoolReport: DeviceActivityReportExtension { var body: some DeviceActivityReportScene { // Report scenes here } } The extension builds and runs perfectly without NSExtensionPrincipalClass, but cannot be uploaded to App Store Connect. Adding the key allows upload but breaks local installation. Is this a known issue? Is there a workaround or correct Info.plist configuration for DeviceActivityReportExtension? Thank you!

I have tried everything and still I am getting this. Just for a test I created a new app (Master-Detail template Xcode 11.5) I have created an entry in the iTunes Connect to receive the app upon archiving and uploading. I regenerated all new certificates for iOS Development and Distribution. I created all new Provisioning profiles. The Dev profile builds deploys and runs on my device The Dist profile builds but when I select the distribution profile I get the "Profile doesn't include the com.apple.application-identifier entitlement." error. When I download the profile within Xcode all looks good for the distribution profile: App ID: matches correctly Certificated: 1 Included includes the new signing certificate "iPhone Distribution...." Capabilities: 3 Included Includes Game Center, In-App Purchase, and Keychain Sharing Entitlements: 5 Included Includes application-identifier, keychain-access-groups, beta-reports-active, get-task-allow, and com.apple.developer.team-identifier. Im not sure what is going on. This is a standard process I have performed for quite a while. As a matter of fact I just submitted 3 applications last Sunday. Thank you for any suggestions.

I just spent way too many hours trying to figure out why my in-app subscription was stuck in “Missing Metadata” in App Store Connect, even though I had filled out everything. If you're here because you're in the same boat, this is the solution Apple doesn't make obvious. The Problem I created an auto-renewable subscription (Kanabloom Premium) and filled in all required fields. The subscription was still marked "Missing Metadata", preventing me from submitting it. The “In-App Purchases” section wasn’t showing up in my App Store version submission, which meant I couldn't even attach the subscription to my app version. I triple-checked the metadata, pricing, tax settings, review screenshot, and even resaved everything, but nothing worked. What I Tried (Before Finding the Fix) Checked that pricing was set up correctly for all countries. Uploaded the required review screenshot for the subscription. Made sure the subscription group existed and was linked properly. Refreshed, logged out/in, and tried different browsers. Read every Stack Overflow, Reddit, and Apple Developer Forum post I could find. Even tried creating a dummy subscription to see if that would reset the system. The Solution: Localizing the Subscription Group Here’s the stupidly hidden requirement that finally fixed it: ✅ Your subscription group itself (not just the subscription) needs a localized display name. App Store Connect requires each subscription group to have at least one localized display name for it to be valid. If this is missing, all subscriptions inside that group will stay stuck in “Missing Metadata” no matter how complete they are. How to Fix It: Go to App Store Connect > Subscriptions > Subscription Group Click on your subscription group (not the individual subscription). Check if there's a localization added under "Group Reference Name." If missing, add a localization (e.g., English) and save. Refresh the page and boom – the subscription will finally be "Ready to Submit." Conclusion Apple really needs to make this requirement clearer. Now that I’ve finally figured it out, hopefully, this post helps someone else avoid losing hours of their life to the same issue. If you're still stuck, double-check that: You’ve set pricing and enabled "Cleared for Sale." You’ve uploaded a review screenshot for the subscription. You’ve signed all App Store agreements and banking/tax documents. Your app's In-App Purchase capability is enabled in Xcode. Let me know if this helped you! I wish I had found a post like this sooner. 😂 This should make for a useful and searchable post in case other devs run into the same headache. Let me know if you want any tweaks before posting! 🚀

I use AES encryption on my app (it's a game), I encrypt the user data (JSON file) (levels / scores / etc...) This is how I answered the App Store Connect questions, not sure if it's correct:-Does your app use encryption? Select Yes even if your app only uses the standard encryption within Apple’s operating system. YES-Does your app qualify for any of the exemptions provided in Category 5 You can select Yes for this question if the encryption of your app is: (a) Specially designed for medical end-use (b) Limited to intellectual property and copyright protection (c) Limited to authentication, digital signature, or the decryption of data or files (d) Specially designed and limited for banking use or “money transactions”; or (e) Limited to “fixed” data compression or coding techniques NO-Does your app implement any encryption algorithms that are proprietary or not accepted as standards by international standard bodies (IEEE, IETF, ITU, etc.)? NO-Does your app implement any standard encryption algorithms instead of, or in addition to, using or accessing the encryption within Apple’s operating system? YESIs your app going to be available on the App Store in France? YESNow it's sending me to Encryption page - Add Export Compliance Documentation for ITC.apps.universal.platformName.iosIs your app designed to use cryptography or does it contain or incorporate cryptography? (Select Yes even if your app is only utilizing the encryption available within Apple’s operating system.) YESDoes your app meet any of the following: (a) Qualifies for one or more exemptions provided under Category 5 Part 2 (b) Use of encryption is limited to encryption within Apple’s operating system (c) Only makes calls over HTTPS (d) App is made available only in the U.S. and/or Canada NODoes your app implement any encryption algorithms that are proprietary or not accepted as standards by international standard bodies (IEEE, IETF, ITU, etc.)? NODoes your app implement any standard encryption algorithms instead of, or in addition to, using or accessing the encryption within Apple’s operating system? YES (it asks me to submit a copy of your French encryption declaration approval form- not sure what it is so I changed it to NO meanwhileClicked OK and then nothing happens. I'm not sure how to continue from here, In order to submit my app to test flight I need to provide export compliance information, which asks my the questions above, and then sends me to Add Export Compliance Documentation, but nothing was added ...

Hello, I am experiencing a persistent TestFlight installation issue affecting multiple unrelated apps under the same Apple Developer account. For all affected apps: Builds upload successfully to App Store Connect Processing completes normally Builds appear in TestFlight Internal and external testing can be enabled Public links generate correctly However, when attempting to install the app via TestFlight, the installation fails with the error: “The requested app is not available or doesn’t exist.” This occurs: For internal testers For external testers Across different Apple IDs Across different devices With newly created apps After incrementing build numbers After re-uploading builds After signing out/in of TestFlight After regenerating provisioning profiles After creating entirely new app entries The issue currently affects: • TubeChat AI – Apple ID 6752591427 • Vibex – Apple ID 6756860663 • vigilAI – Apple ID 6757738356 Since multiple unrelated apps are impacted in the same way, this appears to be an account-level or App Store Connect backend issue rather than a code signing or project configuration problem. Has anyone encountered a similar situation where TestFlight distribution fails across all apps within a developer account? Any guidance would be greatly appreciated.

I launched my app on the App Store and Google Play about two months ago and despite improving the icon and screenshots I have only reached around 40 downloads which makes me believe ASO is my main challenge. I started using ASO tools like TryAstro and AppTweak but the keyword metrics such as volume 39 and difficulty 0 are confusing so I would appreciate guidance on interpreting this data and on effective ASO strategies for a new app with minimal downloads or ratings.

Hi everyone, I’m hoping to get advice or hear from anyone with similar experiences. Our app Pixllove was originally rejected under Guideline 4.3 (“Spam”). We were later invited to an App Review call with Erica, who reviewed everything and confirmed verbally and in writing (April 8, 2025) that the spam classification was removed. She acknowledged that our app uses a unique concept and only required us to implement a pre-chat consent popup. We implemented exactly that: • A popup appears before any chat starts, displaying the match’s name, age, and distance. • Users must actively accept before the chat begins. • We show this clearly in our new demo video. • Full reporting/blocking/moderation is in place. However, after submitting the updated build, we were again rejected under a different interpretation of 1.2, with the reasoning that our app “connects users randomly.” This appears to be a misunderstanding, since no match occurred during their test – and it takes at least 2 users online for a match to happen. We explained this and even submitted a screenshot of the consent popup, which had been explicitly requested by Erica. Sadly, the reviewer ignored our message and Erica’s previous confirmation and labeled us as spam again. We replied and asked them to please review Erica’s note from April 8, but we haven’t received a response yet. We’re lucky to have a second review meeting scheduled for Tuesday, but this experience has been extremely frustrating and honestly, quite unprofessional — especially after being told the issue had been resolved. Has anyone experienced something similar? What can be done to ensure prior Apple Review decisions are respected by future reviewers? Thanks so much in advance, Emilija Pixllove Team

Hi everyone, I’m unable to enable Xcode Cloud for any app on my account. At the final step of the Xcode workflow setup (“Confirm App on App Store Connect”), pressing Complete always returns: “ could not be added to Xcode Cloud. Authentication credentials are invalid.” This affects both existing apps and completely new test apps with fresh bundle IDs. What I’ve verified • I am Account Holder and Admin. • All agreements are accepted. • App creation, bundle ID registration, and certificate management work normally. • I’ve removed/re-added my Apple ID in Xcode and cleared all Xcode-* tokens from Keychain. • Test apps in clean Git repos reproduce the same error. Support I have already opened Case ID 102769512657 with Apple Developer Support, but I’m posting here in case others have seen this issue or know of additional steps to confirm the provisioning state.

We submitted our apps on June 26th 2025, in order to make them available to our customers. To date, we have heard nothing from the AppStore Connect team. 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,

I'm currently experiencing the same problem that many have had with error 422 "Beta contract is missing." I read that I should contact Apple support, but when I try to access the support page and log in with my credentials, the page doesn't load and I can't generate a ticket to resolve this problem. I get the message "There was an error processing your request. Please try again later." And when I inspect with Safari it shows me this information: "errors" : [ { "id" : "9be0314c-3bd5-4143-a625-602322d7156e", "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] This is when I want to share the most recent build of my app with external groups through Testflight, but additionally, when my internal testers try to access it through Testflight app, it shows the error "The requested app is not available or doesn't exist." Could someone tell me what process I should follow or where I can correctly generate the ticket for my error? Since the Apple support page does not load. Thanks!

My account is invited to a team as admin I already accept the invitation but I can't find the team on developer.apple.com, appstoreconnect.apple.com even on XCode. My colleagues also cant find my account on the user and access tab on apple store connect but when he tried to invite me again it throw an error (A user with this email address already exists on this team.) What should I do to fix this?

I accidentally clicked on tvOS instead of iOS for a new build. So now I have a "tvOS Prepare for Submission" item in the left panel of iTunes Connect. I have no plans to make a tvOS version, so is there any way to remove that?

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,

I am the sole Account Holder for my Apple Developer Program account and am encountering an issue where the acceptance of the updated Apple Developer Program License Agreement is not syncing correctly between the two developer portals. Issue Details: Agreement Status on developer.apple.com: I successfully accepted and reviewed the updated agreement at https://developer.apple.com/account. The Agreements section confirms the acceptance date as December 11, 2025 (as seen in the attached image). Status on App Store Connect: Despite this confirmation, when I sign into https://appstoreconnect.apple.com/, I still see the following critical warning: "The Apple Developer Program License Agreement has been updated and needs to be reviewed. In order to update your existing apps and submit new apps, the Account Holder must review and accept the updated agreement by signing in to their account." Impact: This prevents me from performing key tasks, such as creating a new app, which triggers an "Agreement Update" alert that only directs me back to the already-accepted agreement on the Developer website. Troubleshooting Steps Taken: I confirmed I am logged in as the Account Holder. I cleared my browser cache and attempted the process on a fresh browser session. My macOS is fully up to date. I have already contacted Apple Developer Support but have not yet received a reply. Request for Assistance This is blocking my ability to submit and update apps. I am aware that direct phone support is often recommended for these issues, but my country is not listed for phone extension support. Has anyone else experienced this sync delay or found a workaround that resolves the "Agreement Update" alert on App Store Connect when the agreement has been accepted on the Developer website? Any advice on the next immediate steps I should take while waiting for my support ticket to be processed would be greatly appreciated.