An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

Two hours ago we received 42 emails from Apple with the following content: iTunes Connect Dear ....., The routing number you provided for the bank account ending in ..... is no longer correct. To receive payments, update your bank info with a valid account and routing number. If you have any questions, use the Contact Us module on iTunes Connect. We have been receiving payments to this account for 5 years and nothing has changed with the account. The account is valid and all details are correct. And this is displayed under “Payments and Financial Reports”: Payment Rejected The routing number you provided for the bank account ending in .... is no longer correct. To receive payments, update your bank info with a valid account and routing number. A lovely surprise for Christmas.

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

Although the application functions correctly when deployed locally to a physical iPhone using Flutter (direct debug/development build via Xcode), we are encountering the following issues only within App Store Connect / TestFlight: 1- Internal Testing Issue: After completing all required steps in App Store Connect and adding internal testers, testers are unable to install the app. TestFlight displays the error: “Could not install app. The requested app is not available or doesn’t exist.” 2- External Testing Issue: When attempting to add a processed build to an External Testing group (Public Link), App Store Connect returns the following message: “There was an error processing your request. Please try again later.” The build has successfully uploaded and processed, and is marked as Ready to Submit in TestFlight. These issues do not occur during direct device deployment and appear to be isolated to TestFlight / App Store Connect. We would appreciate guidance on how to solve this issue which is preventing TestFlight distribution. *Note: we tried multible builds and upgraded the version 4 times, and we signed all agreements.

Can't Edit Age Ratings in App Information Section of App Store Connect for released App Versions. I only have option to View. I think some of the Age Rating questions are still unanswered but when I view them, I can't Edit them. Non-released apps of mine in App Store Connect allow me to edit answers to the Age Ratings questions but I can only View Age Rating questions for released apps. Do I have to create a new version/build and submit to App Store Connect to be able to Edit the Age Questions?

I am setting up a new app and am having problems with Xcode Cloud. From Xcode if I click on the "Cloud" button under the Report Navigator I get a spinner for a long time then get the message "Could not load Xcode Cloud data". I also visited the "Xcode Cloud" tab under my app in App Store Connect and I get a spinner and nothing loads. This is a recent account and I'm setting up Xcode Cloud for the first time. Below is what I've tried and I'm out of ideas on how to get this working. In Xcode, I signed out and back in as the Account Holder Closed Xcode and reopened This occurred yesterday and today and have not seen a problem under the Apple System Status page On the latest Xcode 16.2 Checked the Signing & Capabilities tab in Xcode and my team a bundle Id is correct and it's happy with signing. At this time on my machine I am using the distribution profile.

在已经上架的App，新增In-app Purchase，6小时后正在审核,一周过去了，还是In Review,没有收到结果，发邮件询问，让继续等待，正常都是48小时有结果的,,不知道遇到什么问题， 如何去解决这个问题呢？ 挺焦虑的....... On the already listed App, I added "In-App Purchase". It was under Review 6 hours later. A week has passed and it's still "In Review". I haven't received the result yet. I sent an email to inquire and asked to keep waiting. Normally, there is a result within 48 hours. I don't know what problem I encountered and how to solve it. Quite anxious....... Quite anxious.......

I am submitting an app to the App Store and want to understand the best way to handle keywords that include special characters. If a keyword has accents like coração and users may search for coracao without accents, should I include both versions or rely on Apple to match them automatically?

Hello, We have completed the Age Rating confirmation form and submitted it successfully. Additionally, we increased the app version, rebuilt, and uploaded a new build as recommended. However, we still received the email stating that “Your app requires additional information”. Could you please confirm whether any further action is required on our side, or if this is a known issue on App Store Connect? Thank you.

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.

Hello, Our Xcode Cloud builds are successfully archiving but fail every time during the "Export archive for app-store distribution" step. The issue appears to be a persistent authentication failure with App Store Connect that we are unable to resolve. Primary Error: The build logs show a critical authentication failure. IDEDistribution.critical.log shows: App Store Connect request for store configuration failed for account Session Proxy Provider... Unable to authenticate with App Store Connect. DVTITunesSoftwareService.log specifies the error is DVTITunesSoftwareServiceFoundation.DVTServicesSessionProviderCredentialITunesAuthenticationContextError.proxy. The build process eventually terminates during the IDEDistributionSymbolsStep with an Rsync failed error, which we believe is a symptom of the earlier authentication failure. Troubleshooting Already Performed: We have already taken the following steps without success: Verified the account used for the integration has "Account Holder" and "Admin" roles. Confirmed that Xcode Cloud's automatic signing is working correctly and is able to create new provisioning profiles. Thoroughly checked the App Store Connect web UI under Users and Access > Integrations > Xcode Cloud for a way to reset the connection, but no such option exists. Removed and re-added the Apple ID in the Xcode application's settings (Xcode > Settings > Accounts) on a local Mac. Our hypothesis is that the integrated authentication session between Xcode Cloud and App Store Connect is invalid or stale, and there is no user-facing way to reset it. Has anyone else encountered this "Session Proxy Provider" authentication error with Xcode Cloud? Is there a known solution or a different method to force a re-authentication of the service connection? Any guidance from Apple engineers or other developers would be greatly appreciated. (Developer Support Case: 102717975870)

I recently began developing iOS apps in 2025. I enrolled in an Apple Developer Account on December 10, 2025 and expected to get App Store Connect to upload my app to the app store. After succesfully paying for a membership, I tried to access App Store Connect but I'm redirected to the now-defunct iTunes Connect. Worst part is the URL mentions AppStore Connect, but the slug points to iTunesConnect and I can't get out of it: https://appstoreconnect.apple.com/WebObjects/iTunesConnect.woa/ra/gettingstarted From here, if I click on the "Apps" button, it redirects me again to the https://developer.apple.com/programs/ website. This is read-only documentation, and I can't take any action to upload my apps. Interestingly enough, if I try to access appstoreconnect.apple.com from Safari, the above loop happens. But if I try to access it from Arc Browser, I see this error instead: To access App Store Connect, you must be an individual or team member in the Apple Developer Program, or invited by an individual to access their content in App Store Connect. Learn More But I am the Account Holder. I found this related post, but it's a dead end: https://developer.apple.com/forums/thread/775608

I am already an enrolled apple dev. When I click on Program resources-App Store Connect-Users and Access, it jumps to appstoreconnect.apple.com which prompts me to login. After doing so, is shows a screen like this Then, if I click on the apps button it takes me to https://developer.apple.com/programs/ and the loop begins.

Hello, I am currently implementing External Purchase Link and External Purchase Custom Link and am encountering an issue where both ExternalPurchaseLink.canOpen and ExternalPurchaseCustomLink.isEligible always return false under all test conditions. I would like to confirm whether my setup is missing any required steps or whether this behavior is expected. Below are the details of my current environment and configuration: 🔧 1. Development Environment Xcode: 16.3, 16.4, 26.0 beta 4 Devices: iPhone running iOS 26.2 beta iPhone running iOS 16.7.12 macOS 15.5 (real device testing) Simulator iOS 18.0 Build Type: Local development build using a Developer Provisioning Profile Sandbox account signed in during testing 🔑 2. Entitlements (Developer site & Xcode) In Certificates → Identifiers → App ID, both capabilities are enabled: StoreKit External Purchase StoreKit External Purchase Link The .entitlements file in Xcode includes: com.apple.developer.storekit.external-purchase = YES com.apple.developer.storekit.external-purchase-link = YES The Provisioning Profile also contains both entitlements (confirmed via codesign -d --entitlements :-). 📄 3. Info.plist Configuration Both keys are configured with correct region codes according to documentation: SKExternalPurchase SKExternalPurchaseCustomLinkRegions 🌍 4. Test Storefront Device storefront verified as United States (US) or Portugal (PT) (US = target region for External Purchase Link, PT = EU region) But despite all the above configuration, both API calls consistently return false: ExternalPurchaseLink.canOpen // false ExternalPurchaseCustomLink.isEligible // false So I cannot proceed to testing the remaining flow (token retrieval, link opening, etc.) ------ Questions ------ ❓ Q1) Local Development Build Limitation Is it expected behavior that Developer-signed local builds always return canOpen = false / isEligible = false for External Purchase Link & Custom Link? Is there a technical or policy restriction that prevents eligibility in local dev builds? ❓ Q2) App Store Connect Configuration Requirement Are there mandatory App Store Connect settings (such as external purchase URLs, support URL, disclosures, or country configuration) that must be enabled before eligibility becomes true? Currently, no External Purchase Link or Custom Link menu is visible in my App Store Connect app settings. Is this menu only available after certain approvals or under specific conditions? ❓ Q3) TestFlight Requirement Do External Purchase Link and Custom Link only return eligibility = true on: TestFlight builds, or Distribution-signed builds? Or should eligibility also work on developer builds? Formal confirmation would be helpful. ❓ Q4) Developer Account Type Limitation We are using an Individual Developer Account (not Organization). Can Individual accounts fully request, test, and ship apps using: External Purchase Link External Purchase Custom Link Or are there limitations on account type? 🙏 Request We have completed all documented setup steps (Entitlements → Provisioning → Info.plist), but eligibility remains false, blocking feature validation. Please clarify which of the following is the cause: Local development builds do not support eligibility Missing App Store Connect configuration (not visible to us) Account type restriction Region rollout or entitlement approval requirement Any additional setup not documented publicly Thank you for your assistance.

Hello guys I’m unable to delete the Test Information and Beta App Information sections on Apple Store Connect. I need to remove them because the app transfer process requires it. I’ve already expired all builds, removed all testers and groups, and tried every possible solution I could find online, but nothing worked. I also contacted Apple Support, but the issue hasn’t been resolved. What should I do next?

Dear Reviewers/Apple Team/Community, We have trying to submit our app continuously for review and being rejected continuously by Apple. Our app works perfectly fine in TestFlight using the same ID apple is using. We have also provided recorded video of the testing in TestFlight to Apple reviewer. However, despite our requests below things are not done: Before testing the in-app purchase subscription are not being approved, despite us requesting the same every time during submissions. At times we are getting snapshots under error category, where everything is correct even from Apple testing. We have no other way but to explain, give snapshots, give videos to Apple to help them understand how to test the app. We have requested the reviewers multiple times for a call, but we got a call only 1 time. We are not sure what is the way we can get to talk with the reviewer and understand from them the issue they are facing. Can anyone please help us out? Below is one example, it was given it us under error category, where even with apple standard, the purchase is successful. Can someone help us out plz.

I've been able to submit my app without issue so far until today, but it looks like app icon requirements either changed or being enforced differently? 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: 954a36b1-b212-4d7f-8a12-db2d6abe83e2) Validation failed Missing required icon file. The bundle does not contain an app icon for iPad of exactly '152x152' pixels, in .png format for iOS versions >= 10.0. To support older operating systems, 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: 7ded4fb3-a0f0-4542-9373-a3dcf9ace3ef) Validation failed Missing app icon. Include a large app icon as a 1024 by 1024 pixel PNG for the 'Any Appearance' image well in the asset catalog of apps built for iOS or iPadOS. Without this icon, apps can't be submitted for review. For details, visit: https://developer.apple.com/documentation/xcode/configuring-your-app-icon. (ID: 43a6785a-3917-4ac9-90b1-dc85d5b2fdd8) Contents.json I already have a 1024x1024 PNG for 'Any Apperance' so not sure what that one is about. The others I cannot find slots for, to provide a generic icon even though they wont be used since my app is only for iOS18+ I attempted adding a new icon set "App Icon" with the 120x120 PNG but that did not seem to work so I removed it. Any suggestions? *note I am also using the .Icon file created by Icon Composer (v3)

Hello, I am encountering the following error when uploading a build to App Store Connect: ITMS-90555: Thinned app size is too large – Your on-demand resources in the universal variant are 30 GB, which exceeds the maximum allowable size. After app thinning, the total size of your on-demand resource asset packs in any variant must be less than 30 GB. Our application includes a large amount of font resources delivered via ODR. Before making structural changes, I need clarification because the documentation does not fully explain how ODR size calculations work per variant. Environment Xcode: (latest stable) Distribution method: App Store submission ODR total size before thinning: approximately (28 GB) Build processing fails immediately with the ITMS-90555 error Questions How exactly does App Thinning compute the size of ODR asset packs per variant? Is ODR size evaluated: Per device-specific variant, Or is the “universal variant” treated as an additional variant that must independently stay under 30GB? The documentation mentions a 30GB limit per variant, but the universal variant error message is ambiguous. If device-specific variants are below 30GB but only the “universal variant” exceeds it, is the build still rejected? In our case: iPhone-only variants appear to be below the limit, But the universal variant exceeds 30GB due to aggregated resources. Is this expected behavior? Best practices for managing very large ODR sets (e.g., fonts) Fonts are small individually, but thousands of them produce very large ODR groups. Is there recommended guidance from Apple for: Structuring ODR bundles to avoid the universal variant exceeding the limit Segmenting ODR by device class / feature sets Any alternative packaging strategies Are there tools or logs that reveal how App Store Connect decides variant groupings and ODR size? At the moment, the failure only shows the ITMS-90555 error without further detail. Case-ID for DTS reference DTS advised submitting this question here. Case-ID: 17273913 Any clarification from Apple engineers or community members who have navigated ODR size limits would be greatly appreciated. Thank you very much!

iosアプリをAppStoreへ公開した後に何らかの理由で戻しが必要になった場合、緊急申請で問題無いアプリを再リリースするのが最速の方法でしょうか？ もしも、より良い方法があれば教えてください。 戻し用のアプリバージョンを用意しておいてリリース予定のアプリを公開した後にすぐ審査を回すという方法を見つけたのですが、審査の90%が24時間以内（ちょっと数字が違うかも？）と言われている以上緊急申請の方が早いですか？

Dear Apple Support, I am writing to report a payment issue with my App Store Connect developer account. The latest payment is marked as "Paid" in the Payments and Financial Reports section, but as of today, more than 3 business days have passed and the funds have not yet arrived in my bank account. I have double-checked that my banking information is accurate and up to date. I would appreciate it if you could investigate this issue and provide further clarification on the current status of the payment. Thank you in advance for your support.

Logging out: The platform logs people out super quickly (e.g. within like a couple of hours), it would be great to be able to stay logged in within the same day and not have to log back in every time. Latency: In general, it can be really slow to load, and sometimes pages fully load without anything on them. The team then has to refresh the page for e.g. dashboards to be shown Submission of PPO & In-app events: PPO tests and in-app events can only be submitted on the latest version, which means that you need to wait for a period when we're not having a new version of the app reviewed. If this is regularly the case, it's difficult to submit. Sometimes you then submit e.g. an in-app event, but it takes a while and the review is removed in favour of an app update. Solution: The whole thing should follow a similar process to CPPs whereby you don't need to upload to the latest version, or you should be able to select which app version you're uploading to and be able to select the latest. Rather than having to delete and build again every time. Pricing updates: The amount of time that it takes to change pricing is insane and results in a reluctance to make price changes. There are a number of ways that this could be improved: a) Don't only allow us to select prices from a drop down list. This process adds like 3 extra clicks to every single price change. Just make the prices editable (e.g you can type) in a list, Google Play Console does this very well. b) For promotions, allow us to set e.g. "20% off the default price" and then when we make pricing updates to the default price the promotional price will update automatically. Instead currently we have to go in and manually calculate 20% off every single price based on the new price and update it ourselves, it's crazy. Reporting on promotions: Currently, there is no ability to see a time series of conversions with specific promotions with configurable date ranges, you can just see the total redemptions up to a certain date. This means we're manually having to look at the number of redemptions up to a certain date and then if we wanted to see a daily breakdown we'd need to look at ever date in isolation and calculate the increase in number of redemptions.