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.

We are getting the above mentioned error while uploading to TestFlight. We have used a Swift Class to request for the Age Range via DeclaredAgeRange Framework. We have exposed Swift class and a helper function to be available in Objective-C layer. We have enabled the following build settings SWIFT_OBJC_INTERFACE_HEADER_NAME = "Common-Swift.h"; SWIFT_OBJC_BRIDGING_HEADER = "Common-Bridging-Header.h "; ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES = YES Also we are compiling the application using latest available Xcode release 17C52 Is there anything else we need to do to resolve the error?

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)

For testing permission response we can use the sandbox account However, when testing permission requests using the AskCenter API, none of the ask API works for me in xcode 26.2 rc and iOS 26.2 rc. For SignificantAppUpdateTopic, I got errors like "The user is in a region that does not support this type of ask" in the console log, but I've already set my billing address to Texas. For CommunicationTopic, the console shows several XPC-related errors, and I’m not sure which of them are relevant. Both of them show an alert view of "Can't ask, An unknown error occurred" Can someone help to guide us how to test the request flow? Thanks

My app's Custom Product Page (CPP) submission has been stuck in "Waiting for Review" since its initial submission on Decemberr 28th, for over two weeks now. Key Timeline and Troubleshooting: Initial Wait and Self-Check: Initially thought it was a normal queue, but there was no progress after several days. Comprehensive Troubleshooting: I have confirmed: Developer account agreements and tax status are normal/valid. This CPP is associated only with the live, published version of the app and is not linked to any pending new version. There are no "Issues to Resolve" prompts in the App Store Connect backend. Attempted Standard Solutions: I have tried "Withdraw and Resubmit" multiple times. The operation completes successfully, but the status always reverts to "Waiting for Review" and never progresses to "In Review". Contacted Official Support: I have reported this issue multiple times through the App Store Connect "Contact Us" form and via email, explaining the suspected technical fault. However, I have not received any substantive feedback. My Core Question: Could this possibly indicate that my account or this specific CPP submission has encountered some rare "lock" or data synchronization failure within the backend system? APP INFORMATIONS APP NAME:Phàm Nhân Ngự Linh Truyện OEG APP ID:com.oeg.bgyn.ios CPP SUBMISSION ID:8e5813d2-c823-4168-a2c3-7030230f11c7 I'm reaching out in desperation because this review delay has already forced us to postpone a critical marketing campaign by nearly 20 days. I'm at my wit's end and genuinely don't know what else to do. Any guidance or insight from the community would be a lifesaver—this situation is putting my job at serious risk. Please, if anyone can help, I would be immensely grateful

Hello, we get in touch as we need some guidance from Apple regarding age verification for minors in our app. Our app supports iOS 17 and above. The Declared Age Range API is available only starting on iOS 26, but we must comply with legal requirements (e.g., Texas SB 2420) and ensure that minor users cannot access certain sections of the app, regardless of the version of the operating system. Our question: What is the correct and Apple-approved approach for handling age verification and restricting access for minor users on iOS versions prior to 26, given that the Declared Age Range API is not available on those systems? We want to ensure that our implementation aligns with the regulations, the App Store Review Guidelines and platform expectations.

Apple sent a final reminder asking developers to complete the updated age rating questions in App Store Connect. Final reminder: Answer the updated age ratings questions. We’re reaching out because you have not provided responses to the updated age ratings questions in the App Information section of your app in App Store Connect. If you don’t answer these questions by January 31, 2026, you won’t be able to submit app updates in App Store Connect. The email says that if the age rating questions are not answered by 31 January 2026, you will not be able to submit app updates. What is not clear is what actually happens after that date. Many of us are in the middle of development and may not be ready to submit a new build before the deadline. The email does not explain whether this means: A) You can still submit updates after 31 January 2026, as long as you complete the age rating questionnaire before submitting, or B) The app becomes locked and cannot be updated at all once the deadline passes This is not stated explicitly in the email, which makes it confusing for me. It would be helpful if Apple could clearly confirm what developers should expect after 31 January 2026, especially for apps that are still undergoing active development. Anyone knows?

My app has been in “Ready for Review” for about ~2 weeks with no new messages in App Store Connect. I’m trying to figure out if this is normal right now or if there’s something I should do on my side. Thanks, just trying to sanity check timelines.

The title says by itself. We've been using advanced app clips a lot and have created more than hundreds of advanced app clips for the customers. Suddenly, few days ago, the most recently created advanced app clips stopped working as they got stuck with CREATE_SUBMITTED status. It seems like it has already happened before to someone else: https://developer.apple.com/forums/thread/763374 It probably be OK if it showed a Safari notification but it shows an error due to another bug reported here: https://developer.apple.com/forums/thread/803187

I am implementing In App Purchase and integrating App Store Server Notifications version 2. I am able to receive the JWSSignedPayload from Apple. The payload is Base64 encoded and contains header, payload, and signature. The documentation clearly explains how to decode the payload and extract claims such as notificationType and data. What is unclear is how to verify the JWS signature itself. I could not find concrete documentation that explains: Which Apple public key or certificate should be used for verification How to retrieve or rotate the key used to sign the payload The exact steps required to validate the JWS signature before trusting the payload Signature verification is critical for security, and simply decoding the claims without validation is not sufficient. I am looking for official guidance or a recommended approach to verify the JWSSignedPayload signature for App Store Server Notifications v2.

应用ID(id6754838125), A week has passed since I added in-app purchases to the already listed application, but it's still under review and I haven't received any result. I sent an email to inquire and asked me to keep waiting We used Contacts Us There is no result. 2. The call has been made for expedited review. It was submitted on December 11th and is still under review Previously, the result of the app review was available within 48 hours Now, I don't know what solutions can be made to this problem. The company is in a hurry and needs to use the App to release a new movie

Hi, I’ve been waiting for App Store review since December 3, and the submission is still in Waiting for Review status. The update itself is very important for the app, but technically simple, with no unusual changes or new permissions. In the past, reviews were completed much faster, so this delay is concerning. Is anyone else experiencing similar review times recently, or is this a known slowdown? Thanks.

Hello, Suddenly when I search for my app in AppStore, it does not display in the returned results. Interestingly, apps with similar genre or interest are returned instead. I didn't change anything in the AppStore settings. Any ideas as to why this is happening?

Hey there, We've been using App Store Connect API to manage (create/update) Advanced App Clip Experiences via App Store Connect API. Everything has worked fine, we've been able to successfully manage hundreds of app clips but all of a sudden starting on December 15th the API started returning the following error: "id" => "1e15b36b-5347-4af0-9bab-7f6626ffec65" "status" => "409" "code" => "ENTITY_ERROR.INCLUDED.INVALID_ID" "title" => "The provided entity id is invalid" "detail" => "The provided included entity id 'EN' has invalid format" "source" => array:1 [▼ "pointer" => "/included/0/id" ] It does seem to be an API bug considering it has always worked fine and we didn't change anything on our side, the /included/0/id value has always been EN and never changed. Moreover, EN still seems to be a valid value according to the API docs and there are no changes reported of that field in the API release notes. Here's the request ID: 1e15b36b-5347-4af0-9bab-7f6626ffec65 I've tried using different values through trial and error (en, EN, EN-US, ...) and none of them worked.

I would like to ask for clarification regarding my app submission with Submission ID: d293828f-8f9a-4a6d-b138-9650258ab3f3, which has been in “Waiting for Review” status for more than 7 days. I understand that review times may vary depending on queue volume and other factors. However, this extended waiting period is impacting our release timeline, and there have been no status updates or requests for additional information. Could you please help check the status of this submission or let us know if any further action is required from our side? Thank you for your time and support. I look forward to your response.

Hello App Store Review Team, I would like to ask for clarification regarding my app submission with Submission ID: d293828f-8f9a-4a6d-b138-9650258ab3f3, which has been in “Waiting for Review” status for more than 7 days. I understand that review times may vary depending on queue volume and other factors. However, this extended waiting period is impacting our release timeline, and there have been no status updates or requests for additional information. Could you please help check the status of this submission or let us know if any further action is required from our side? Thank you for your time and support. I look forward to your response.

Hi Apple Team, I hope you are doing well. I am reaching out regarding the upcoming watchOS architecture requirements announced in your official communication. According to the notice, beginning April 2026, watchOS apps uploaded to App Store Connect must include the arm64 architecture and be built with the watchOS 26 SDK. zoom current watchOS app, however, only supports arm64_32, and the app size is already over 60 MB in its current form. If we add support for both arm64_32 and arm64, the binary will almost certainly exceed the 75 MB app size limit, and potentially violate the size constraints for each architecture slice as well. This raises practical concerns about how a dual-architecture watchOS app can remain within the required size limits. Could you please advise whether Apple has any recommended approach or best practice for this scenario? For example: Does Apple suggest that developers transition to arm64-only and drop support for arm64_32 devices? Are there any exceptions, additional guidelines, or alternative mechanisms for handling apps that exceed the size limit when including both architectures? Are there recommended techniques specifically for watchOS to reduce binary size when supporting multiple architectures? Any guidance would be greatly appreciated, as we want to ensure our watchOS app remains compliant with the new requirements while continuing to deliver a reliable experience for our users. Thank you very much for your support, and we look forward to your advice.

In the verifyReceipt API response, there is a "is_trial_period" field. As detailed in WWDC 2023 the verifyReceipt is deprecated, how to fetch the fact that the subscription is during the free trial period via recommended App Store server APIs?

Dear Apple Support Team, I am adding new subscriptions to my app and tried to submit them for review. However, I received the following error message: "Your subscription could not be submitted for review. Please provide a privacy URL in App Privacy." I have already provided the privacy URL and changed nothing in the past.. Could you please advise how to resolve this issue so I can submit my new subscriptions for review? Thank you for your assistance. Best regards :)

Hi, We have submitted our app appeal on 13 November, and it has now been over a month without any update. We understand that investigation can take time, but this appears to be taking longer than expected. Does anyone have such experience before?