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 cant get my new app version built because apple has the white and blue + no longer showing to create new app version. I have a rejected app due to IAP's not approved. This requires a new version of the app to get them approved so im stuck until new version is submitted for IAPs to get approved through.

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?

Hi, I am trying to get an app approved. In app purchases say that I need to fix something without saying what needs fixing. I can't add the in-app purchases to the app review and that one does not pass because there are in-app purchases missing. How can I fix this issue? I assume that during review someone could just write whats missing but obviously they won't. The message I received said: One or more of your In-App Purchases has been returned for the following app: Literally nothing else. Regards,

Hello, I submitted an app update (submission ID: 3bbbd08f-6ca9-40a2-bdc1-a2f33061f647) that was rejected for Guideline 4.0 - Design (about ad frequency issues). The rejection message included this option: "The issues we've identified below are eligible to be resolved on your next update. If this submission includes bug fixes and you'd like to have it approved at this time, reply to this message and let us know." I replied on December 11 at 10:21 PM asking to approve the current version as a bug fix, and that I would address the ad frequency in my next update. It's now been over 35 hours with no response. Should I resubmit my binary for review? Typically, when I reply to the App Review message in such a scenario, my app gets approved in a few hours.

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.

Recently I got an email stating I need to update age rating questionnaire. I have tried to update age rating for my app in App Store using the account owner already. I have followed this tutorial (https://developer.apple.com/help/app-store-connect/manage-app-information/set-an-app-age-rating/), but the age rating cannot be updated. Anyone know how to update this, please let me know

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.

Hi everyone, I’m looking for some help or clarification regarding repeated rejections under Guideline 3.1.3 - Business - Payments - Other Purchase Methods. In earlier versions of our app we did experiment with using in-app purchases for our eSIM-related service (which App Review treats as a physical good/service). After the first rejections, we fully reworked the payment flow. In the current build we have: Completely removed any use of the in-app purchase API / StoreKit and removed all UI elements and wording mention in-app purchases. Detached all in-app purchase products and marked all previously created IAP products as “removed from sale”, so they are no longer available to users. Moved all payments to an external outside of the in-app purchase API, which (as I understand it) is exactly what Guideline 3.1.3 requires for physical goods/services. Despite this, the app is still being rejected with the same 3.1.3 message about using in-app purchases for physical goods, without any new details or updated screenshots that point to the actual problem in the latest build. One thing that might be related: in App Store Connect there are still some legacy in-app purchase products stuck in an “In Review” state. We can’t delete or fully edit them from our side, even after removing the previous builds. They are not attached to the current version and are not referenced anywhere in the code or UI, but I’m worried they might still be confusing the review process. Has anyone run into a similar situation? Can these legacy IAP products in “In Review” status still trigger 3.1.3 rejections, even if they’re not attached to the binary and removed from sale? Is there any way to get App Review or Developer Support to reset or clear these products so we can fully remove them? We’re a small team trying to launch, and at this point we feel a bit stuck in a loop where the feedback doesn’t seem to reflect the current implementation. Thanks in advance for any help or insight.

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

I'm making a wrapper library to abstract away some of the 'missing platform support' of DeclaredAgeRange until hopefully it expands to additional platforms. When I'm trying to fully enumerate all of the cases of AgeRangeDeclaration, which they all state available starting 26.0 (mysteriously added in Xcode 26.2 beta), the app crashes due to a missing symbol at launch time. This happens both for Xcode 26.1, 26.2 beta 2, and matching Xcode Cloud builds. So I've isolated it beyond "doesn't work on my machine". I just made a handful of crashes and attached a sysdiagnose to a fresh feedback. FB21121092 - DeclaredAgeRange: Eligibility property and new declaration cases unavailable on iOS 26.1 device contradicting documentation - causes runtime symbol not found crash If anyone is curious what these crashes look like I've attached the DiagnosticPayload.jsonRepresentation() generated from one of my favorite frameworks, MetricKit. Very clearly articulated in the diagnostic metadata you can see the symbol not found. "diagnosticMetaData" : { "platformArchitecture" : "arm64e", "terminationReason" : "Symbol not found: _$s16DeclaredAgeRange0bC7ServiceV0bC11DeclarationO14paymentCheckedyA2EmFWC\nReferenced from: <1894EDCB-3263-3604-8938-97D465FF3720> \/Volumes\/VOLUME\/*\/PerformanceOrganizer.app\/PerformanceOrganizer\nExpected in: <B8FD2C23-0CC9-3D94-902D-875900307A7A> \/System\/Library\/Frameworks\/DeclaredAgeRange.framework\/DeclaredAgeRange", "exceptionType" : 10, "appBuildVersion" : "745", "isTestFlightApp" : true, "osVersion" : "iPhone OS 26.1 (23B85)", "bundleIdentifier" : "dev.twincitiesapp.performanceorganizer", "deviceType" : "iPhone18,1", "exceptionCode" : 0, "signal" : 6, "regionFormat" : "US", "appVersion" : "2.0.0", "pid" : 22987, "lowPowerModeEnabled" : false } DiagnosticPayload.json This is the offending code in a type I control and make available on other platforms but leave unused. extension AgeRangeDeclaration { // A factory or initializer that takes the AgeRangeService.AgeRangeDeclaration and maps to the common AgeRangeDeclaration type public init?(platform value: AgeRangeService.AgeRangeDeclaration?) { guard let value else { return nil } switch value { // Xcode 26.1 visible cases case .selfDeclared: self = .selfDeclared case .guardianDeclared: self = .guardianDeclared // Xcode 26.2 visible cases // This is the first culprit, all of the following symbols would crash, this is just the first case .checkedByOtherMethod: self = .checkedByOtherMethod case .guardianCheckedByOtherMethod: self = .guardianCheckedByOtherMethod case .governmentIDChecked: self = .governmentIDChecked case .guardianGovernmentIDChecked: self = .guardianGovernmentIDChecked case .paymentChecked: self = .paymentChecked case .guardianPaymentChecked: self = .guardianPaymentChecked @unknown default: // Apple added new cases in Xcode 26.2 betas that were available in iOS 26.0, // so it is probable that this could happen again. If it does, assert to let developers // bring it to my attention. assertionFailure("Invalid or out of date knowledge of age range declaration \(value)") self = .unknown } } } For what it is worth, the same is also true for isEligibleForAgeFeatures which I suspect was also added to Xcode 26.2 somehow but not made available to real devices running [26.0 - 26.2). As a side note, thank you for this property, it will let me check what states I need to perform extra checks for in a clean way, I just will need it to now not crash my app on 26.0 and 26.1 runtime devices. :) Edit: DTS did confirm on a comment I had in another thread that this is a bug. Now just to wait for an Xcode beta update. https://developer.apple.com/forums/thread/807906?answerId=867205022#867205022 In any case, this is a great example of how MetricKit totally rocks capturing things other off the shelf crash tools might not have a chance to get. I did have to roll back my TestFlight to an earlier build, but MetricKit was there to send me the previous crashes as soon as the app could launch. Thanks MetricKit team!

Hello, I recently was rejected for the following reason: However, your app does not comply with: Legal 5.1.1 We noticed that your app requires users to register with personal information to access the app’s content and purchase in-app purchase products that are not account based. Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the user. User registration that requires the sharing of personal information must be optional or tied to account-specific functionality. To resolve this issue, please revise your app to not require users to register before purchasing in-app purchase products that are not account based. You may explain to the user that registering will enable them to access the purchased content from any of their iOS devices and provide them a way to register at any time, if they wish to later extend access to additional devices. Resources See guideline 5.1.1(v) - Account Sign-In to learn more about our requirements for apps with account-based content and features. I replied: We require the user to login/sign up because it relates directly to the core functionality of our App. If the user deletes the App and chooses to reinstall it, his data will be saved on our server because the sign up system allows their data to be saved. This allows the User to restore all his in-app purchases and for our database to always keep track of the User’ in-app purchased consumable items. Apple requires a restore feature for in app purchases and we allow the user to restore his in app purchases by tying their account to an email or social media login. The login is required to prevent users from hacking the app. The diamond and coin systems are stored on our back end database servers. Once a user logins in, the back end stores how much coins and diamonds are associated with that account. This prevents users from manually altering how many coins or diamonds they have. It preserves the integrity of the app and the Apple App Store itself. Our servers store all user progression and data. Without the login / sign up system, we cannot sync the back end database. The login / sign up feature is crucial to the functionality of the app to prevent hacking and to keep track of the users database and more importantly, keep account and restore capabilities available for any in app purchases. To which the review board responded with: Although requesting that users register to for tracking users’ purchases and game progresses is acceptable, requiring users to fully register for an account before entering the game is not. Users should be allowed to access none account-based features before registration and login. You may also choose to alert users that accessing game without binding an account may result in losing game progress or in-app purchase items. To resolve this issue, please revise your app to let users freely access your app’s non account-based features, such as accessing the game, prior to registration or login. Once the user decides to use account-based features, the app may present the registration or login feature at that time. My understanding is this... I need to implement a "play as guest" mode where Users do not need to register. This will automatically generate an account for that User. However, am I allowed to require the user to register before conducting any in-app purchases, or other activities on the app?? What is this asking for? Do I need to allow the guest user to be able to purchase and do all the things a registered user can?

My app has been waiting for review for over 7 days. I know it's nearing the holidays but at most I think it should take 5d. Should I maybe developer reject my app and resubmit it? I have already tried expedited review.

Hi there. I work for a company that develops a SaaS service. Users have to register before using the SaaS as all the data they save in the application must be linked to their account. Why that? Because it is a multi-platform SaaS currently running on web and Android, so, the user must have access to his/her contents on every platform he/she intends to use. Also, some features depend on our back-end system to process the data and return an analysis based on them. That said, Apple is rejecting our app claiming that we should not require the user to register an account before purchasing a subscription. The problem is: how can the user store their data in our servers without an account? We do offer a free tier account, but the users must be logged in to have access to their data and have the analysis performed by the back-end service. Does anybody have gone through a similar issue? I need clarifications on how to solve this. Thanks in advance.

Hi everyone, I am seeking urgent advice or attention from the App Review team regarding a Pending Termination Notice I received for Section 3.2(f). The Situation: I recently acquired a portfolio of apps from another developer to start my business on the App Store. Three months after the transfer, my account was flagged for removal because one of these acquired apps "repeatedly violated guidelines to evade the review process." The Problem: I am being punished for the previous owner's actions. I have never submitted a new build, metadata update, or review request for this specific app since acquiring it. The Timeline (Proof of Innocence): August 4, 2025: Last update submitted by the Previous Owner. September 6, 2025: I signed the Purchase Agreement to start my business. September 9, 2025: App Transferred to my account. December 11, 2025: Termination Notice received. As the timeline proves, the alleged "evasion attempts" via submissions occurred before I even owned the app. Regarding "Unresolved Issues": I am aware the app had an old "Unresolved Issue" flag from September 2024. However, the previous owner successfully released multiple updates throughout late 2024 and 2025 despite this flag. As a newcomer to the App Store, I reasonably interpreted this as a system glitch in App Store Connect, given that Apple continued to approve new versions for a whole year. My Appeal: I have submitted an appeal via the Contact Us form, stating: I am a bona fide purchaser with legal proof (Purchase Contract & Bank Transfer records). I have never touched the code or submitted a build for this app. I am willing to immediately remove the problematic app to save my account and the other legitimate apps I am operating. Request: If an Apple Staff member sees this. Please review the transfer logs. I am a victim of the seller's hidden violations, not a participant in fraud. Has anyone else faced a termination for an acquired app they never updated? Thank you.

Hi Apple Staff / App Review Team, We’re following up because we haven’t received a substantive reply to our previous forum post or our messages in App Store Connect. Context (unchanged): Our last update focused on performance/stability, bug fixes, and numeric balance tuning (difficulty/rewards). We also added a small, user-initiated News panel (globe icon in the main menu) that displays one static announcement image and can be closed at any time. There are no links, no navigation, no login/UGC/ads, and no executable content in that panel. We don’t collect personal data (no IDFA/ATT). Safeguards already in place: Post-release changes are restricted to numeric balance values only (no feature toggles, no navigation changes). The announcement is strictly read-only (one static asset from our own domain) with an offline fallback. Internal release policy forbids any post-review feature switches or concept changes. What we’re asking for: Specific guidance on what observation(s) led to the 3.2(f) determination. Whether a resubmission under the constraints above is acceptable (we can tighten further if preferred). We’re ready to provide any materials immediately and submit a new build as soon as we receive direction. Thank you for your help—could you please escalate or advise on next steps?

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.

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.

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.

I have 2 apps. I do not want to update the binaries as we are doing overhauling in the meantime. I actually attended to these issues a couple of months back when I received the first notification and thought everything was ok until we received the final reminder email hours ago. I have two apps: app_1: the age rating was auto computed in August 2025 with no missing fields and the new age rating is in line with our expectations, so I just left it as it is app_2: the age rating had some missing answers, and I was unable to input anything so I created a new release and then updated the age ratings. the app is now in "pending submission" stage but the age ratings have been updated. I did not submit the release for review. !!! in both cases, the updated age ratings are updated & LIVE for both our apps and can be seen in our appstore listings !!! but I still get the final reminder email anyway. Q1) should I do anything? Q2) anyone else in the same boat (not keen to submit a new binary for review)? We really are in the middle of some changes and can't submit a new build now Q3) what happens after 31 Jan 2026? Can we still submit a new release with the latest age rating questions? Or totally can't update anymore?