Overview

Hi all, Hoping someone has run into this or has advice. My App Store Connect account is registered as an Individual, with the legal entity/account holder under my name. I added a bank account, but the Account Holder Name on that bank account belongs to a different person than the name on my developer agreement. That other person and I are both Admins on the same App Store Connect team. It's now been well past the standard 24-hour processing window, and the bank account is still showing "Processing," with the usual banner: "Your banking updates are processing, and you should see the changes in 24 hours. You won't be able to make any additional updates until then." Separately, my Canadian GST/HST Form 506 also shows "Missing Tax Info," and my Paid Apps Agreement is "Pending User Info," so I suspect these two issues may be related/compounding. Questions: Has anyone successfully gotten Apple to approve a bank account where the Account Holder Name doesn't match the developer account's legal entity name, when both people are Admins on the same team? If not, has anyone been able to get Apple to cancel/reset a stuck bank account submission so they could resubmit under the correct account holder name? I can't edit it myself while it shows "Processing." Any luck getting a timely response from the Financial Information contact form specifically, versus general Developer Support (which just redirected me to documentation)? Appreciate any insight trying to avoid this dragging on for weeks like I've seen in a few other threads here. Thanks!

We're hitting a submission deadlock with a Capacitor-based iOS app that I suspect will affect any app using Capacitor/Cordova (or similar frameworks distributed as prebuilt binaries) once Xcode 27 ships. Setup: App built with the current Xcode, targeting the current SDK. Embeds Capacitor.framework and Cordova.framework (via ionic-team/capacitor-swift-pm). The loop: Using Ionic's latest official release: these prebuilt frameworks are still built against an older Xcode/iOS SDK. App Store Connect rejects the upload with ITMS-90111 (stale SDK), even though the app's own target and every other embedded framework are current. To fix that, we rebuilt Capacitor.framework/Cordova.framework from Capacitor's open-source iOS source (MIT-licensed, same version as the official release) using the current Xcode — confirmed via archive that every framework now reports the current SDK. That upload is then rejected with ITMS-91065 (missing signature) — the rebuilt frameworks lack an Apple SDK signature that (as far as we can tell) only Ionic's own build pipeline can produce. So: official release → current-SDK check fails. Self-rebuilt release → signature check fails. We verified this isn't a fluke with an isolated throwaway-archive test swapping only the framework source. Questions for anyone who's solved this: Is ITMS-91065's "Apple SDK signature" requirement satisfiable by re-signing a self-built .framework with our own Distribution certificate during export, or does it specifically require Apple's own build-time signature that third parties can't reproduce? Has anyone shipped a Capacitor/Cordova app successfully against a new major Xcode/SDK before Ionic cut a matching signed release? If so, how? Also filed with Ionic: ionic-team/capacitor#8537 (https://github.com/ionic-team/capacitor/issues/8537) — no response yet as of 2026-07-23.

Hello Apple Developer Community, I’m reaching out in hopes that someone from Apple or another developer who has experienced a similar situation can offer some guidance. My app, Appliance Fit Check™, has been stuck in the App Review process for nearly two months. This submission is only an update to an app that is already available, and unfortunately there has been no movement for an extended period. Over the past several weeks, I have remained patient and have done everything I know to do. I have: Contacted Apple Developer Support multiple times. Been assigned a support representative who advised me that my case had been expedited approximately three weeks ago. Continued following up politely regarding the status of my app. Despite being told the review had been expedited, there has been no visible progress. The app continues to show that it is in review, and I have not received any additional information explaining the delay. This app is extremely important to my business. Appliance Fit Check™ helps consumers determine whether an appliance will fit their existing cabinet opening before they purchase it. Installers, homeowners, and customers rely on it to help avoid costly installation problems, unnecessary returns, and modification issues. Many of my customers have been waiting for this update, and every additional week of delay impacts both my business and the people who use the app. I completely understand and respect that the App Review team handles a very large volume of submissions and works hard to maintain the quality and security of the App Store. I sincerely appreciate that effort. My intention is not to complain or bypass the review process. I’m simply trying to understand why this update has remained in review for such an extended period. If an Apple representative or supervisor happens to see this post, I would be very grateful if someone could take a look at my submission or provide any information about whether there is an issue preventing the review from moving forward. Even knowing that the review is actively progressing would provide some reassurance. Has anyone else recently experienced a review taking this long? If so, was there anything that helped move the process forward? Thank you very much for your time, and I truly appreciate any advice or assistance the community or Apple team can provide.

Hello Apple Developer Community, I’m reaching out in hopes that someone from Apple or another developer who has experienced a similar situation can offer some guidance. My app, Appliance Fit Check™, has been stuck in the App Review process for nearly two months. This submission is only an update to an app that is already available, and unfortunately there has been no movement for an extended period. Over the past several weeks, I have remained patient and have done everything I know to do. I have: Contacted Apple Developer Support multiple times. Been assigned a support representative who advised me that my case had been expedited approximately three weeks ago. Continued following up politely regarding the status of my app. Despite being told the review had been expedited, there has been no visible progress. The app continues to show that it is in review, and I have not received any additional information explaining the delay. This app is extremely important to my business. Appliance Fit Check™ helps consumers determine whether an appliance will fit their existing cabinet opening before they purchase it. Installers, homeowners, and customers rely on it to help avoid costly installation problems, unnecessary returns, and modification issues. Many of my customers have been waiting for this update, and every additional week of delay impacts both my business and the people who use the app. I completely understand and respect that the App Review team handles a very large volume of submissions and works hard to maintain the quality and security of the App Store. I sincerely appreciate that effort. My intention is not to complain or bypass the review process. I’m simply trying to understand why this update has remained in review for such an extended period. If an Apple representative or supervisor happens to see this post, I would be very grateful if someone could take a look at my submission or provide any information about whether there is an issue preventing the review from moving forward. Even knowing that the review is actively progressing would provide some reassurance. Has anyone else recently experienced a review taking this long? If so, was there anything that helped move the process forward? Thank you very much for your time, and I truly appreciate any advice or assistance the community or Apple team can provide.

Hello, I am currently developing call-related features for our app, and I have a question regarding one of the APIs. When the app is launched from the Recents list by selecting a recent call, the activityType of the userActivity is provided as either INStartAudioCallIntentIdentifier or INStartVideoCallIntentIdentifier. However, I understand that these identifiers have been deprecated since iOS 13, and the documentation recommends using INStartCallIntentIdentifier instead. The issue is that when the app is launched from the Recents list, INStartCallIntentIdentifier is never provided. Instead, the deprecated identifiers (INStartAudioCallIntentIdentifier and INStartVideoCallIntentIdentifier) continue to be delivered. I have reviewed the available documentation, but it is not clear how developers are expected to handle this situation. Could you please advise on the recommended approach for supporting this flow? Is it expected that applications continue to handle the deprecated identifiers in this case, or is there another recommended implementation? I would greatly appreciate any guidance you can provide. Thank you.

Hello, I'm hoping someone from the App Review team can take a look at this, or that a fellow developer has advice on next steps. App: Yoinky (App ID: 6791431277) Rejection reason: Guideline 2.1 - Information Needed - New App Submission. The review team requested a screen recording, list of tested devices, app purpose/audience description, setup instructions, list of external services, and info on regional differences. Timeline: Saturday, July 18, 8:31 AM: Rejected under Guideline 2.1, requesting the information above Saturday, July 18, 3:08 PM: Replied in the Resolution Center with all 7 requested items (screen recording, tested devices, app description, setup instructions, third-party services, regional notes, and confirmation that the regulated-industry/third-party-material item doesn't apply) Saturday, July 18, 3:10 PM: Re-attached the screen recording, since it wasn't visible on the first attempt Tuesday, July 21, 8:10 AM: Followed up asking for a reply and whether a new build/re-evaluation was needed Tuesday, July 21 (evening): Still no response, so I opened a support case via Contact Us (Case ID: 102948382497) As of today, Thursday, July 23: No reply through any channel — Resolution Center or the support case I checked the case status page and the only contact option available for this case is email, so I haven't been able to request a phone callback either. I've provided everything that was requested (including a demo-free walkthrough, since the app has no accounts, purchases, or subscriptions) and just want to confirm it's being reviewed, or find out if a new build submission is needed instead. Would appreciate any guidance from Apple staff, or from other developers who've had a similar "Information Needed" rejection and gotten a response. Thanks in advance.

Hi everyone, I'm wondering if anyone else is experiencing the same issue. For the past several days, I have been completely unable to install any of my TestFlight applications. The problem affects every app on my Apple Developer account, not just a single project. Here is what I've verified so far: Builds upload successfully. App Store Connect finishes processing without errors. The builds appear in TestFlight. My certificates and provisioning profiles appear to be valid. I have tested on different networks and users. The issue still persists. The installation simply fails, making it impossible to test my applications. I have already contacted Apple Support but have not yet received a response. At this point, I'm starting to wonder whether there could be an issue with my Apple Developer account or a backend problem affecting TestFlight. Has anyone experienced something similar recently? If you have, did Apple identify the cause or provide a solution? Any information would be greatly appreciated.

Hi everyone, I submitted an app update for review on July 16, and the status has been stuck at "Waiting for Review" for a full week now (7 days and counting). The app is not in a sensitive category (not health, finance, VPN, or gambling related), and there are no legal or export compliance issues that I'm aware of. A bit of background: App type: update (not a new app) Submission date: July 16, 2026 Apple Developer Program membership: active and in good standing No messages in Resolution Center or App Store Connect inbox No changes made to the submission during this period (no metadata edits, no new builds uploaded) I understand review times can fluctuate, but 7+ days in "Waiting for Review" — not even "In Review" — without any communication seems unusually long, especially for a routine update. Has anyone else experienced similar delays recently? Is there anything suggested beyond withdrawing and resubmitting (which I'd like to avoid)? Thanks in advance!

Our app has been stuck in "Waiting for Review" with no movement for 10 days. Timeline: July 13: Submitted version 2.0.1 (App ID 6584518186, a stability release) July 18: Resubmitted as 2.0.2 (build 133) with additional crash fixes — same app, same metadata Since then: no review start, no rejection, no metadata request, nothing. What we have already tried: Five (5) expedited review requests — all with concrete justification, zero response A status inquiry through Contact Us (App Review) — no response Review notes and a working demo account are fully provided and verified end-to-end Why this is urgent: this is a critical stability release. Firebase Crashlytics shows our crash-free user rate on the live version dropped to 55% — nearly half of our daily active users experience crashes (1,400+ crash events per 24 hours). The fixes are all in the waiting build. Every day of delay directly harms real users. Questions: Is there any way to find out whether a submission is simply queued vs. placed on an internal hold? App Store Connect shows only "Waiting for Review" either way. Is anyone else currently seeing 7+ day waits? (I've found several similar threads from February and May 2026 with no resolution posted.) Is there any escalation path left when expedite requests and Contact Us both go unanswered? App ID: 6584518186 Any guidance would be greatly appreciated.

I'm developing a macOS product that generates verifiable audit records of media-asset movement on endpoints, for professional media-production companies. It is not an antivirus or Data Loss Prevention product; it collects operating-system file-system events and converts them into tamper-evident audit evidence and audit reports. Target users need comprehensive endpoint audit trails for compliance with industry security standards, including Motion Picture Association Trusted Partner Network assessments. The product must reliably distinguish these operations: file copy, move, rename, and volume mount and unmount — including on external volumes. I've reviewed existing forum guidance, including Quinn's explanation that FSEvents only signals that "something changed" rather than the exact operation, and that it is designed around Spotlight and Time Machine semantics. In my own testing I've also seen inconsistent flags across cp, Finder copy, and application saves, and frequent kFSEventStreamEventFlagMustScanSubDirs events on external drives even when nothing along the path changed. Questions: Given the above, for an audit product that must reliably distinguish copy vs. move vs. rename, should FSEvents be treated as structurally unsuitable, with the Endpoint Security Framework adopted instead as the primary source? For capturing volume mount and unmount operations, is the Endpoint Security Framework the recommended source, or should this be combined with Disk Arbitration? Are there long-term supported APIs recommended for this type of endpoint audit product, to ensure compatibility with future macOS releases? Any recommended documentation, WWDC sessions, or sample code for this use case would be appreciated. For context, I'm building toward a System Extension using the Endpoint Security Framework and will file the entitlement request separately; this post is to confirm the architectural direction before committing. Thank you.

Here's a much shorter version with just the questions: Hi Apple Developer Support, We're an ad network already registered for SKAdNetwork and are integrating AdAttributionKit. We have a few questions regarding postback URL registration: Do we need to register a separate postback URL for AdAttributionKit, or is our existing SKAdNetwork postback URL reused automatically? If a separate AAK registration is required, can the AAK postback URL be the same as our existing SKAN postback URL, or does Apple require a different URL/path? If the same URL is used for both, are AAK postbacks always delivered as a JWS payload while SKAN postbacks continue to use the existing JSON format? When WWDC states that existing SKAdNetwork ad networks require "no further enrollment," does that refer only to reusing the existing ad network ID, or also to reusing the registered postback URL? Is the Developer Mode AdAttributionKit testing flow the correct way to validate ad network postback delivery? Thanks!

For the past two days ive been trying to submit for review my app and two subscriptions, but they have been coming back in red each time with an error code "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." It isn't consistent though, because sometimes ill remove the one thats red and submit it, and then all of a sudden my other subscription is in the red. I've checked everything and tried all the basics like removing it and submitting again, checking i have all the information down and they are identical, yet only one subscription is red even though when i remove it, it says the other is red as well. I've even tried completely deleting the subscription and making another, still wont submit. Any help?

Hello, I'm experiencing a serious issue with my Apple Developer account. Every app I submit stays in "Waiting for Review" for more than a month. This is not happening with just one app—it affects every app I submit. Here are the details: Every submission remains in Waiting for Review for over a month. The status never changes to In Review. I have already contacted Apple Developer Support. I also submitted an Expedited Review request, but the apps are still waiting. The apps fully comply with the App Store Review Guidelines and are complete and functional. At this point, I'm trying to understand whether there could be an issue with my developer account or if there is another reason causing all of my submissions to remain stuck in the queue. Has anyone experienced the same issue recently? If an Apple engineer sees this post, I would greatly appreciate any guidance or if my account could be checked. Thank you.

I have a project that builds fine in macOS 26 with Xcode 26. On macOS 27 b4 and Xcode beta, the same project can't build because of a framework that should be pulled from a Swift Package from a package-registry (named Registry, for example below), hosted on JFrog. I have the registry set up and have the token in keychain. The resolution of the packages works. But when I build, I get error like this: error: Missing package product 'Registry.Package_Package.Package' (in target 'Target' from project 'Project') . The real package should just be 'Registry.Package'. Any help with that? Is it a bug?

I distribute my AppleScript applet in a read only DMG file. I want to add a simple background image which encourages users to copy the applet to their Applications folder. I use the Finder function "Show View Options" which has the option to add a picture. That seems to work in macOS Tahoe. However, the background image is not visible on earlier versions of macOS. I've also found that a background image set on a Mac running Monterey is not visible on a Mac running Tahoe. Is there a way to add a background image which works across multiple macOS versions ?

We have an Apple Watch app and companion iPhone app that we distribute via Enterprise Distribution using OTA manual installation. (We are on an Apple Enterprise Developer Team) With WatchOS 26.4 and earlier, the app would install fine on both the phone and the watch. However, after updating to WatchOS 26.5 (and iOS 26.5), the app will not install on the watch. It will install on the phone and we can trust the developer/run the phone app. However, when we go into the Apple Watch app on the phone and choose "Install" for the app, it tries to install for a minute and then returns an error "The app could not be installed at this time". We have tried the following remedies: Restarting both watch and phone, and reinstalling the app on phone Factory resetting both the watch and the phone, then reinstalling app Generating a new Distribution Certificate and new manual profiles for the app in Apple Developer Looking through console logs from both the phone and the watch Confirmed that we can install other (non-Enterprise) apps on the watch Try installing a basic example app (the default Xcode watch + companion app project) There does not seem to be anything obviously amiss about the app or its packaging, it seems to be something to do with the update to WatchOS 26.5. The closest related errors we have found seems to be these: appconduitd 0x16d43f000 -[ACXInstallQueue _onQueue_deQueueNextOperation]_block_invoke_3: Failed to install app .EnterpriseInstallTest.watchkitapp (p = Y, ui = Y) : Error Domain=ACXErrorDomain Code=8 "Failed to create socket" UserInfo={NSUnderlyingError=0xcf9138e10 {Error Domain=com.apple.identityservices.error Code=20 "Socket open timed out" UserInfo={NSLocalizedDescription=Socket open timed out}}, FunctionName=-[ACXServerInstallOperation _onQueue_prepForTransferAndInstall]_block_invoke, SourceFileLine=370, NSLocalizedDescription=Failed to create socket} appconduitd 0x16d89f000 -[ACXCompanionSyncConnection _installQueuedOrCompletedForWatchBundleID:companionAppBundleID:withName:userInitiated:withError:withCompletion:]_block_invoke: Failed to install app .EnterpriseInstallTest.watchkitapp : Error Domain=ACXErrorDomain Code=8 "Failed to create socket" UserInfo={NSUnderlyingError=0xcf9138e10 {Error Domain=com.apple.identityservices.error Code=20 "Socket open timed out" UserInfo={NSLocalizedDescription=Socket open timed out}}, FunctionName=-[ACXServerInstallOperation _onQueue_prepForTransferAndInstall]_block_invoke, SourceFileLine=370, NSLocalizedDescription=Failed to create socket}

I've hit several walls and this one I cannot get past.I don't understand how subscriptions work for an app I've published and am unable to get them live. I've followed the docs online about setting up a subscription, they've been submitted and approved, I've removed the base price for my app so people aren't gated from downloading it, yet, when a person downloads the app, they have full unrestricted access without having to subscribe. I don't get it. It seems to me that I may be responsible for building a gate in my own app that requires choosing a subscription. Is that right? If so, what is the purpose and use of the subscription the App Store Connect offers? If it is incorrect and Apple should actually be directing people to choose a subscription - what am I doing wrong? I think the hole in the wall cannot get any bigger from hitting my head with it at this point. I need help that isn't just "have you read this article?" or "follow the instructions on this help page". I've done it. I've read it. Yet here I am, pleading for some actual guidance on how to get this done.

Hi Team, I'm trying to understand the behavior of the following API: HTTPCookieStorage.shared.setCookies(_:for:mainDocumentURL:) Specifically, does this API persist cookies synchronously, or does it perform the storage asynchronously in the background? Our use case is storing FCAP (frequency capping) cookies so they persist across app sessions. We call setCookies(_:for:mainDocumentURL:) and want to know whether the cookies are guaranteed to be written before the method returns, or if the actual persistence happens asynchronously. I couldn't find documentation describing the persistence semantics of this API, so I'd appreciate any clarification or guidance from Apple or anyone familiar with its implementation. Thanks

I’m working with an asset pack that contains multiple characters with a common skeletal hierarchy. This asset pack also contains animations for these characters as separate files. i.e.: run pick up idle throw In RCP2, I was able to add these animations to an Animation Library component without issue. However, in RCP3, I cannot add the skeletal animations to compatible characters. The only animations available are the transform animations, which do not animate the character. So in the animation library, I will see i.e.: run_transform idle_transform throw_transform But not run idle throw Is there something that I need to do to make the skeletal animations visible? I’ve tried adding the animation library at various levels across the hierarchy and it doesn’t seem to make a difference. Only the _transform animation is visible. I can verify that the animations themselves are compatible by manually editing the tm_entity for a character and adding the animation clip. I have to do this while RCP3 is closed but it works. I did notice that each animation is referencing a skeleton uuid. Is the UI only exposing skeletal animations with a matching skeleton uuid? Lastly, I can import both the character and the animation files as USD in a RealityKit app and successfully assign animations.