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.

I have already submitted the updated age rating options and even published a new version of the app after doing so. However, I still received an email with the subject “Final reminder: Answer the updated age ratings questions,” stating that the age rating options have not been submitted. I checked the App Information section, and all the required age rating options are correctly selected. Has anyone else received a similar email? Is there any additional action that needs to be taken?

The latest version of Xcode available on: https://developer.apple.com/download/applications/ is Xcode 26.2 build 17C52. It was released today, December 12, 2025. However, uploads are failing with error: Validation failed. This bundle is invalid. Apple is not currently accepting applications built with this version of Xcode. I have verified my Xcode is not beta: I think that at least the non-release candidate, latest version of Xcode should be allowed to submit apps.

I received the email from Apple entitled "Final reminder: Answer the updated age ratings questions." However if I login to App Connect, or click on the link in the email to go directly to App Connect, there are no questions. There are 6 tabs/sections in App Connect, flicking through them, there are no questions about age ratings. Even if I could find these questions, if there are no apps actually released to the App Store (and no plans to release any) is answering these questions necessary? The Apple email sounds quite threatening in its tone, hinting at consequences if you don't comply, but I can't comply because no questions in App Connect are being presented.

This is the error that I get when I build for the iOS App Store or run on my connected iPad (with App Store release). This is my first iOS app that i have developed. When I build for development I get no errors and runs fine on my iPad (also simulator ipads). I have several Mac apps on the app store. The embedded.mobileprovision file is in my app bundle. com.nawctsd.riotpad is the Bundle Identifier in the app and in the App ID Configuration.

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?

在已经上架的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.......

Has anyone else received the email “Final reminder: Answer the updated age ratings questions.” even though all live apps were updated for the age ratings months ago? We only have one new app that we created, but we haven’t even set up age ratings for it yet. The app has never had a build uploaded. Did we receive this email because of this app? We also deleted some apps in the past. Could the email have been sent because of those deleted apps?

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?

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 recently published version 1.0 of my first app, but I'm unable to update it. In App Store Connect, I select my App and on the left under iOS App there are currently 2 platform records, but I believe there should be 1. On the bottom is a green check mark and "1.0 Ready for Distribution". Above that with a yellow check mark is "1.0043 Prepare for submission". I believe I mistakenly pressed add platform instead of + version. Now I don't see a + Version button on my Ready for Distribution platform. I don't see any way to delete this extra platform record. For uploading, I have been using a DevOps build pipeline that uploads the final build to app store connect. It reports that the builds are being uploaded successfully, but I don't see them anywhere in the build versions. I have tried saving the 1.0043 version but I'm unable to attach any of the builds I'm uploading. Please help, I've finally got a live app but I'm unable to update it. Am I correct that the extra platform record is what's keeping me from updating it? If so, how can I delete it? Thank you!

Hey all, We're trying to submit an updated build of our app for review, however the Submit button is not visible. There are no other alerts anywhere of any issues and the latest build has ben processed normally. Any ideas? Apple is just referring us back to some generic Help topics, so we're stuck here. Thx!

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.

I’m having an issue where Product.products(for:) returns an empty array in sandbox testing, even though my subscriptions appear fully configured in App Store Connect. Setup: iOS app using StoreKit 2 (async/await) Two auto-renewable subscriptions configured Both subscriptions show “Ready to Submit” status Pricing set for all regions Localization complete (English US) Review screenshots uploaded Review notes added 7-day free trial configured Testing Environment: Real device (iPhone, iOS 18+) TestFlight build uploaded AFTER subscriptions marked Ready to Submit Sandbox tester account logged in via Settings → Developer → Sandbox Apple Account Cleared purchase history multiple times What I See: 🛒 Fetching IAP products... 🛒 ✅ Products loaded: 0 🛒 ❌ No products found What I’ve Tried: Verified Product IDs match exactly (character-for-character) Clean builds and fresh TestFlight installs Multiple sandbox account sign-out/sign-in cycles Cleared sandbox purchase history Waited 24+ hours after metadata completion Same StoreKit 2 code works in another app with non-consumable IAP Code Sample: private let productIDs = [ "com.myapp.monthly", "com.myapp.yearly" ] func loadProducts() async { do { let products = try await Product.products(for: productIDs) print("Products loaded: \(products.count)") } catch { print("Failed: \(error.localizedDescription)") } } Questions: Is there additional propagation time needed for auto-renewable subscriptions vs non-consumables? Are there any hidden metadata requirements beyond what shows in App Store Connect? Has anyone experienced this where subscriptions simply never propagate to sandbox? Any help appreciated. Already submitted a support case to Apple but looking for community insights.

In the latest release of my app, I received a "Validation failed (409)" notification and cannot release my app. The full context is : Validation failed (409) No architectures in the binary. Lipo failed to detect any architectures in the bundle executable. The only thing I did that lead into this problem is, I changed the display name of my app. (in plist file, CFBundleDisplayName) I have tried different times with different configs of my app, Now the app was rejected even I switch back to the old branch which is succeed last week.

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.