Overview

I am developing a macOS solution that exposes a cloud-backed digital signing credential as a system identity through a persistent CryptoTokenKit token extension. My main goal is to allow third-party macOS applications, especially Adobe Acrobat, to discover the signing identity through the standard macOS Keychain infrastructure and use it for signing PDF documents. Intended signing flow The flow I am trying to implement is: The user adds a cloud signing credential in my macOS container application. My application retrieves the certificate and credential metadata from a remote signing service using the CSC protocol. My application creates or updates the persistent CryptoTokenKit token configuration. The CryptoTokenKit extension exposes the certificate and its associated private-key capability as a macOS system identity. The user opens a PDF document in Adobe Acrobat and starts a digital signature operation. Adobe Acrobat discovers the identity through the standard macOS certificate and Keychain selection flow. The signing request is routed to my CryptoTokenKit token extension. My extension forwards the signing request to the remote CSC signing service and returns the resulting signature. The private key is held by the remote signing infrastructure. It is never stored or exported locally. Environment macOS 26.4.1 (25E253) Xcode 26.4.1 (17E202) Swift Persistent Token Extension created from the Xcode template macOS container application Apple silicon Mac Current implementation issue I have built a prototype consisting of a macOS container application and a persistent CryptoTokenKit token extension. While managing the persistent token configuration, I encountered a reproducible issue with TKTokenDriver.Configuration.driverConfigurations. When I access this API from the container application process, the operation can block indefinitely without returning an error. I tested different threads and dispatch queues, but the behavior remained the same. However, when I execute the same configuration operation from a newly launched helper XPC process, it completes successfully. At this stage, I would first like to confirm that the overall architecture is correct before submitting detailed code and reproduction steps. Questions Is a persistent CryptoTokenKit token extension the Apple-supported architecture for exposing a cloud-backed signing credential as a macOS system identity? What is the recommended Apple-supported pattern for creating and updating persistent TKTokenDriver.Configuration entries? Should this be done directly by the container application, or is a separate process expected? Is there any official Apple sample project or technical guidance covering persistent CryptoTokenKit tokens, network-backed signing and consumption by third-party applications? I have a focused test project and can provide minimal code, logs, process samples and detailed reproduction steps if they are useful. Any architectural guidance, sample code or experience with a similar Adobe Acrobat signing flow would be greatly appreciated. Thank you!

Hello, We have an enterprise application that provides a security agent plugin with custom UI based on SFAuthorizationPluginView. We’ve been testing it on macOS 27 Developers Betas 1 through 4 and we noticed that if we set screenUnlockMode to 2, then after a screen is locked for the second time during one session, it can no longer be unlocked. Here are the concrete steps to reproduce: Open Terminal. Run sudo defaults write /Library/Preferences/com.apple.loginwindow.plist screenUnlockMode -int 2 Lock the screen. Observe the “You must enter the password to unlock the screen” dialog window. Enter the correct password and press OK. Lock the screen again. Expected result: The dialog “You must enter the password to unlock the screen” is displayed again. Entering the correct password unlocks the screen. Actual result: The screen is black with no visible UI. Rebooting the system seems to be the only way to leave this state. Displaying custom UI at the unlock screen is a part of our core functionality and it has been working fine with screenUnlockMode = 2 since at least macOS 14. I have filed a feedback FB23918474; if it is a known issue, please merge it with mine so that I can receive updates on the matter. In the meantime, do you have any suggestions on what can be done? Thanks.

All our workflows started to fail today due to timeouts - the notarization process is unable to finish in under 1 hour. The latest submission ID that failed after 45mins: 7449abcb-0d24-441b-a992-d5c7e7d279e3 It has never been a problem for us for the past years - is there something off on Apple side?

Hello, I'm trying to notarize my Electron macOS application using a valid Developer ID Application certificate. Environment: Apple Developer Program: Active Developer ID Application certificate: Successfully created App size: ~130 MB (ZIP) Using notarytool (via electron-builder / GitHub Actions) The submission was uploaded successfully, and I received a Submission ID. Submission ID: e48ead02-a837-42cd-9d90-c4c0f014e589 However, the notarization has remained in: Status: In Progress for more than 2 hours. Running both: xcrun notarytool info and xcrun notarytool history continues to report: Status: In Progress No notarization log is available yet. I have already contacted Apple Developer Support, but I wanted to ask the community: Is it normal for a notarization submission to remain "In Progress" for several hours? Has anyone experienced this recently and eventually received an "Accepted" status? Could this indicate a temporary Apple-side queue or backend issue? Any insight would be greatly appreciated. Thank you.

In the past I was always able to install every major macOS version on an external drive so that I can test my apps. But now I'm unable to install macOS Tahoe 26 on an external drive. Actually, as far as I'm aware, there are not even official links to macOS 26 installers, but only instructions on how to update to macOS 26 from an existing macOS installation. So I thought I'd install macOS 15 on a separate drive and then update to macOS 26, but whenever I run the macOS 15 installer, tell it to install on the external drive, and reboot after the setup process completes, my MacBook just boots into my main macOS partition as if nothing happened. 3 months ago I somehow managed to install macOS Tahoe beta 1 on an external drive, I don't remember how (but I don't think it was anything crazy); booting into that beta 1 partition and trying to update doesn't work either, as my MacBook again boots into my main macOS partition. I already asked help about the update problem one month ago here, but nobody replied. Could someone at Apple please provide instructions on how one is supposed to install macOS 26 on an external drive (if possible before it becomes available to the public)? Are we supposed to buy a separate Mac for every macOS version that we want to test our apps on?

Can somebody tell me if I'm doing something wrong or SwiftUI's scrollTo(id:anchor:) just doesn't work if the ScrollView is scrolling? I have a trivial example that demonstrates the issue: import SwiftUI @main struct MyApp: App { var body: some Scene { WindowGroup { ContentView() } } } struct Item: Identifiable { let id = UUID() let timestamp: Date let text: String } struct ContentView: View { @State private var items: [Item] = (0...10_000).map{ .init(timestamp: Date(), text: "Row \($0)") } @State private var scrollPosition = ScrollPosition(idType: Item.ID.self) @State private var newMessage: String = "" var body: some View { ScrollView { LazyVStack { ForEach(items) { item in ItemView(item: item) } }.scrollTargetLayout() } .defaultScrollAnchor(.bottom, for: .initialOffset) .scrollPosition($scrollPosition, anchor: .bottom) .safeAreaBar(edge: .bottom) { HStack { TextField("Type here", text: $newMessage, axis: .vertical) .textFieldStyle(.roundedBorder) Button("Send", action: { let trimmed = newMessage.trimmingCharacters(in: .whitespacesAndNewlines) guard !trimmed.isEmpty else { return } newMessage = "" items.append(.init(timestamp: .now, text: trimmed)) withAnimation(.smooth) { scrollPosition.scrollTo(id: items.last!.id, anchor: .bottom) } }) }.padding() } } } struct ItemView: View { let item: Item var body: some View { VStack(alignment: .leading) { Text(item.text) Text(item.timestamp.formatted()) }.padding() .frame(maxWidth: .infinity, alignment: .leading) .background(Color(red: .random(in: 0...1), green: .random(in: 0...1), blue: .random(in: 0...1))) } } #Preview { ContentView() }

I'm just not getting it. My app adds a custom Import menu item to the File menu. I want to have it tell the sole ContentView to run the fileImporter. Here's how I have it set up. Changing the showFileImporter variable to supposed to make stuff happen, but it doesn't change. @main struct Blah: App { @State public var contentView = ContentView(); var body:some Scene { WindowGroup { // ContentView() // It started out defining the content like normal, but I saw somewhere that if I declared it as a var up top, then I'd have an actual object that I could tell to do things, like calling the importTerms() method below. self.contentView } .commands { CommandGroup(after:.newItem) { Button("Import…") { contentView.importTerms(); } } } } struct ContentView: View { @State private var showFileImporter = false; var body: some View { VStack { ...stuff... } } .fileImporter(isPresented:$showFileImporter, allowedContentTypes:[.text], allowsMultipleSelection:false) { result in } public func importTerms() { print("\(showFileImporter)"); // ->false showFileImporter = true; print("\(showFileImporter)"); // ->yep, still false } } But it doesn't work. It calls importTerms(), and a breakpoint inside that method does get hit. But it doesn't change the value of showFileImporter and the fileImporter never appears. What kind of weird world has Swift made where setting a variable to true doesn't set it to true and there's no error at build or runtime?

After upgrading to iOS 27 Beta 3, iBeacon region monitoring no longer behaves as it did on previous iOS versions. Issue 1 – Never exits region After connecting to an iBeacon, I power off the beacon and move several kilometers away. The app never receives an Outside (didExitRegion) event. Even after force quitting the app, powering off the beacon, locking the screen, and turning the screen back on, iOS may relaunch the app as if it were still inside the beacon region. Is this an intentional change in iOS 27 or a bug? Issue 2 – Sometimes never enters region Occasionally, the app is not awakened when entering the iBeacon region. No Inside event is delivered. The only way to recover is to manually scan and reconnect to the beacon. Otherwise, the app is never awakened by the iBeacon again. This worked reliably on iOS versions before iOS 27.

I've registered and paid for Apple developer account on June 2nd and my account is still pending. I've sent an email to Apple support and on June 8th and received a case ID number, but I still haven't received a reply as yet. What do I do?

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!