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.

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?

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.

Share Age Range Permission is set to 'Ask First'. Application requested for AgeRange via requestAgeRange API. System presented a consent window where user has to make a choice. User did not acted. Application was pushed to background. Our Application supports PushToTalk Framework and we have successfully joined the channel already. User tapped on the blue-pill , SystemUI will get presented. User tapped on the SystemUI, A New Full Screen SystemUI will get presented. User chosen 'Leave' option and our application left the active channel. 10 User brought the application to foreground and the previous "Share Age Range" system window disappeared. 11. After Step 10, We need to terminate and launch our application in order to get the "Share Age Range" system window. Is "Share Age Range" system window getting disappear is expected here or a BUG

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.

As per the US state law including SB2420 in Texas. We are suppose to meet their compliance. We have following queries Could you please confirm whether the provided Declared Age Range API framework is available for sandbox testing How does the API respond for a region other than Texas

We're developing an Electron app for MacOS App Store. When updating our app through TestFlight, TestFlight prompts "Close This App to Update", and when I click "Continue" our app would be "Terminated" for update. Now this is where things go wrong. On MacOS 15 our app seems to be gracefully terminating (We attached it with lldb and it shows that our app returns with 0 when we click "Continue") which is fine. However for MacOS 26 though, it seems that TestFlight just directly SIGKILLs our app (indicated by lldb), which means that all of our app's child processes are left orphaned. Even worse, our app is singleton, which means that when the app relaunches it fails, because the leftover child processes from the previously SIGKILLed session is still alive, and even if we want to kill those orphaned child processes we can't because our app is sandboxed thus cannot kill processes outside of the current sandbox. We captured output from log stream (app name redacted): 12-02 22:08:16.477036-0800 0x5452     Default     0x5a4a7              677    7    installcoordinationd: [com.apple.installcoordination:daemon] -[IXSCoordinatorProgress setTotalUnitsCompleted:]: Progress for coordinator: [com.our.app/Invalid/[user-defined//Applications/OurApp.app]], Phase: IXCoordinatorProgressPhaseLoading, Percentage: 99.454 123: Attempt to set units completed on finished progress: 214095161 2025-12-02 22:08:16.483056-0800 0x53ba     Default     0x5a5c9              167    0    runningboardd: (RunningBoard) [com.apple.runningboard:connection] Received termination request from [osservice<com.apple.installcoordinationd(274)>:677] on <RBSProcessPredicate <RBSProcessBundleIdentifierPredicate "com.our.app">> with context <RBSTerminateContext| explanation:installcoordinationd app:[com.our.app/Invalid/[user-defined//Applications/OurApp.app]] uuid:A3BC0629-124E-4165-ABB7-1324380FC354 isPlaceholder:N re portType:None maxTerminationResistance:Absolute attrs:[ 2025-12-02 22:08:16.488651-0800 0x53ba     Default     0x5a5c9              167    7    runningboardd: (RunningBoard) [com.apple.runningboard:ttl] Acquiring assertion targeting system from originator [osservice<com.apple.installcoordinationd(274)>:677] with description <RBSAssertionDescriptor| "installcoordinationd app:[com.our.app/Invalid/[user-defined//Applications/OurApp.app]] uuid:A3BC0629-124E-4165-ABB7-1324380FC354 isPlaceholder:N" ID:167-677-1463 target:system attributes:[ 2025-12-02 22:08:16.489353-0800 0x53ba     Default     0x5a5c9              167    0    runningboardd: (RunningBoard) [com.apple.runningboard:process] [app<application.com.our.app.485547.485561(501)>:2470] Terminating with context: <RBSTerminateContext| explanation:installcoordinationd app:[com.our.app/Invalid/[user-defined//Applications/OurApp.app]] uuid:A3BC0629-124E-4165-ABB7-1324380FC354 isPlaceholder:N reportType:None maxTerminationResistance:Absolute attrs:[ 2025-12-02 22:10:23.920869-0800 0x5a5a     Default     0x5a4c6              674    14   appstoreagent: [com.apple.appstored:Library] [A95D57D7] Completed with 1 result: <ASDApp: 0xc932a8780>: {bundleID = com.our.app; completedUnitCount = 600; path = /Applications/OurApp.app; installed = 0} 2025-12-02 22:10:32.027304-0800 0x5ae5     Default     0x5a4c7              674    14   appstoreagent: [com.apple.appstored:Library] [BEB5F2FD] Completed with 1 result: <ASDApp: 0xc932a8780>: {bundleID = com.our.app; completedUnitCount = 600; path = /Applications/OurApp.app; installed = 0} 2025-12-02 22:10:36.542321-0800 0x5b81     Default     0x5a4c8              674    14   appstoreagent: [com.apple.appstored:Library] [185B9DD6] Completed with 1 result: <ASDApp: 0xc932a8780>: {bundleID = com.our.app; completedUnitCount = 600; path = /Applications/OurApp.app; installed = 0} The line "Terminating with context" seems suspicious. This line is not seen on MacOS 15, only MacOS 26. Is this documented behavior? If so, how can we handle this?

Hi all, It has been >30 days since my app was removed, and I was served with the pending account termination notice. Similar to others, I was flagged for section 3.2(f). Submitted an appeal, explicitly addressing every possible violation, offered to show source code with entire history, and also have all the email threads of me providing customer support to my users, and also multiple 5 star reviews. However, I was met with the rejection and the confirmation that the account would be terminated. Fast forward more than 30 days, my account is still here, but no closure or clarification at all regarding what I can do moving forward. Understandably, the team deals with millions of submissions and apps, but isn’t it reasonable (given that we pay $100/yr) to at least get some clarification on what went wrong? Currently, all I want to know is, Can I create a new account and develop other apps? Or will I risk getting banned again, hence wasting another $100? If I am able to proceed, what do I need to do to make sure my app doesn’t get randomly terminated again? Why aren’t there any signs or warnings? If anyone is able to assist me on this, I would greatly appreciate it. Thank you so much!

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: 525f6327-6859-4ae7-977b-7951423127a6) getting this error while archive and validation then validation failed and got this error But in my xcode each icon is present and when i build the app then in simulator or a real phone the icon is present but while archive and validation then validation failed also i have tried a lot solution but unable to resolve this.

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

Noticed a sudden drop in my keyword rankings recently and after some digging, it looks like Apple rolled out a major ASO update, which a lot of developers seem to be talking about. Curious if anyone has insights on what specifically changed - it seems like the app title may no longer hold the same weight in keyword rankings.

I’ve been building iOS apps since 2011, took a 4-year break, returned with two new apps, and it feels like organic visibility and indexing have changed drastically compared to earlier releases. Has anyone else noticed slower indexing, fewer automatic mentions, and almost zero organic traction—has discovery changed, or is it just saturation?

My team has a robust digital accessibility program and processes for WCAG conformance in our apps. Because of this, there are definitely accessibility defects that get caught and addressed in order of impact and business priority like any other bug. Obviously we want to aim for 100% accessibility for our users, but it's a continual work in progress as new enhancements or changes are released. I'm stuck on the appropriate measurement to indicate support. If we have 50 common tasks and the most central 10 tasks are solid but some supporting (but also common) tasks have a contrast fail or accessibleLabel missing, does that make the whole app not supporting the feature? If "completing the task" is the rubric there are a whole range of interpretations for that. In a complex app, I anticipate that a group like ours will have strong support for many of the Accessibility Nutrition Labels accessibility features across tasks and devices, but realistically never be 100% free of defects for a given Apple Accessibility feature, even among core tasks. As I consider the next steps for Nutrition Labels, I do not see anything in the documentation that gives a sort of baseline or measurement for inclusion. We plan to test all steps to complete a task, and log defects accordingly with an assigned timeline for fixing them (as would be true for functional defects).

Hello Apple Dev Support, Our company is preparing to submit an iOS and iPadOS application. When development commenced nine months ago, the application name was available. However, during the submission process for internal and external testing via TestFlight, we discovered that the name is already in use. We are seeking a solution to secure our application name, ensuring its exclusive use for our purposes. We anticipate approximately four to five months of development before the application's release. If we submit our application for Apple review and receive approval but refrain from releasing it, would this action reserve or register the name for our exclusive use, preventing others from utilizing it? Thank you

Hello everyone, it's been over a month since I released a version of the app and sent it to Apple for review. What's going on? A month in review with no response from support! This is a disgrace, Apple! I released the same version on the Play Store and they approved it in 3 hours. What's happening?

Hello, I submitted my application for review and it's not being processed. Each time, I wait months for a response. This is incredibly frustrating because I'm already too late to announce my project. I've repeatedly requested an expedited review, but it doesn't work. Is anyone else experiencing the same issue?

When TestFlight was in public beta, the user had a mainland China account and downloaded the app from the mainland China App Store. However, when subscribing, the app displayed the message: "Your account is not available in the US App Store. You must switch to the Chinese App Store before making a purchase." In reality, the user's account region was already mainland China, and the app was downloaded from the mainland China Mac App Store. I've set all countries to be available in Connect. Has anyone encountered a similar issue? testflight公测时，用户是中国大陆的账号，在大陆appstore下载了应用。 但是订阅的时候，app提示：你的账户在美国商店中无法使用，在进行购买之前，你必须切换至中国商店。实际上，用户的账号地区已经是中国大陆，也是在中国大陆的mac appstore下载的应用。 我的在connect 中设置了所有国家可用，有人遇到类似的问题了吗？

I would love to partake in beta testing and reporting issues and bugs! Let me know what you got