Overview

We are integrating the App Intents framework into our iOS app to enable Siri functionality, including intents that display user data (e.g., showing upcoming schedule information) and intents that perform actions on behalf of users (e.g., submitting a time-off request). Our Legal team has asked us to provide any developer-specific integration terms or agreements that govern the engineering use of Siri and the App Intents framework — separate from the user-facing Siri, Dictation & Privacy terms. So far, the only reference we've found to App Intents or Siri in Apple's developer agreements is Section J of the Apple Developer Program License Agreement. We've also reviewed the App Store Review Guidelines, the Privacy HIG, and the Siri HIG. As a point of comparison, Apple Maps has its own specific set of developer integration terms (MapKit / Apple Maps Server API terms). Does anything equivalent exist for Siri and/or the App Intents framework? If Section J of the License Agreement and the relevant HIG sections are the complete set of terms governing developer use of App Intents and Siri, confirmation of that would also be very helpful. Thank you.

This is my case. I am based and Canada (Quebec) recently i moved to org. I am small supplier. I don't have revenue. My app is free on app store. I am forced by apple to till my tax GST and RT. My app is completely free and does not use In-App Purchases, subscriptions, or paid downloads. The Paid Applications agreement appears to have been activated accidentally, and App Store Connect is now forcing Quebec tax registration fields that do not apply to my account. I need the Paid Applications agreement removed or reset so I can continue updating my free app. I called and email number of time the support but most of the time no "support" at all most of the time is is turn off/turn on "support". I am not even able to call them I am totally blocked to connect them. Support just send you links and leave you without solutions. I am really desperate and my app is blocked month without update and using services that I paid.

Hi DTS, I have 4 notarytool submissions all stuck in "In Progress" with no movement for 12+ hours. 'xcrun notarytool log <id›' returns "Submission log is not yet available" for all of them - they don't appear to have been processed at all. Team Identifier: NS22D2XK8A 1 .dmg submission at 2026-05-12T01:35Z (12+ hours stuck) dmg submissions between 10:04Z and 12:12Z This is my first time notarizing with this Team ID - possibly the new-account first-submission "in-depth analysis" delay? The DMG passes every standard check: Signed with Developer ID Application (Team NS22D2XK8A) Hardened runtime on all 6 embedded binaries (codesign flags 0x10000) Full authority chain: Developer ID App → Developer ID CA → Apple Root CA Secure timestamp present Entitlements: allow-jit, allow-unsigned-executable-memory, disable-library-validation, network.client, network.server, files.user-selected. read-write codesign --verify -deep --strict passes cleanly spctl source = "Developer ID Application" (correct) DMG itself signed inside-out per TN2206 I have read the other recent "stuck In Progress" threads from new Developer IDs - same pattern. Could the queue be unblocked, or is there a team-side configuration that needs flipping? Happy to provide submission UUIDs + filenames privately via Feedback Assistant or DM. Thanks!

When using a web page to upload from the camera roll. During selection everything is ok but after confirming the selection, its still possible to change the selection and if media is in a processing or downloading state its not obvious to a user what is going on. This results to a confusing user experience. It doesn't seem like theres any signal back to the page in this state, its just a poor camera roll picker which doesn't block selection changes or show any progress that something is happening (i.e. localising or processing for upload). Same result on Chrome and Safari

I have already filed a bug report with a sample project via Feedback Assistant: FB22760723 When presenting a UIViewController using UIModalPresentationFormSheet alongside UISheetPresentationController with a small custom detent (e.g., around 300pt height), VoiceOver spatial swipe navigation breaks. The user is unable to swipe left or right to navigate sequentially through the accessible elements inside the sheet. Accessibility Inspector reveals that the focus seems to get trapped by the background layer (UIDimmingView / "dismiss popup"). If the sheet is taller (e.g., 600pt), the issue does not occur and swipe navigation works as expected Steps to Reproduce: Run the attached sample Objective-C/UIKit project. Turn on VoiceOver. Tap the “Open transparent modal” button to present the modal with UIModalPresentationOverFullScreen presentation. Tap the "Open form sheet" button to present the sheet (configured with a custom 300pt detent). Attempt to swipe right using VoiceOver to navigate to the next element (e.g., from the title label to the buttons). Expected Results: VoiceOver should smoothly navigate through the sequential accessibility elements inside the sheet's view hierarchy, respecting the bounds of the modal sheet. Actual Results: VoiceOver gets stuck. The swipe right/left gestures fail to move focus to the next element inside the sheet. Instead, focus often escapes to the background or doesn’t change completely.

The MagSafe 3 cable is an amazing piece of engineering, showing charged as green and charging as amber. Please consider that "carging," being amber and "full" or "reached charging limit," is green, but for a high end company, you need to make the MagSafe wire more useful. A software MagSafe update, like macOS 26.5 was very noticeable for me, as i have the charging limit set on 80%. A new MagSafe 4 would be a simple MagSafe 3 update, creating MagSafe 4, introducing a yellow colour, to mimic macOS window controls. It is very simple, as both red and green diodes are already in MagSafe 3, light physics tells us that red+green=yellow. All we have to do is turn on both of those LED diodes, and we have yellow. MagSafe 4 should have the following: Amber:0%-50% Yellow:50%-90% Green: 90% + or reached charging limit Pulsing Amber: overheating or critical issue with power cut off Pulsing yellow: slow charger, under 30w for macbook air and under 70w for macbook pro. This should be very simple as its a few lines of code.

Hello, I would like to have MSAL login fully working in a Developer ID signed macOS application. I am using the following library for adding MSAL support to my macOS app : https://github.com/AzureAD/microsoft-authentication-library-for-objc . The MSAL login (even silent login via the MSAL broker) works fully via my company Entra ID when I run and test my local dev build. But : when I build and sign and notarize my application with a company Developer ID signature, the login fails, and I see keychain access related issues in the MSAL library log entries. The MSAL library requires the following keychain access groups to be enabled : $(AppIdentifierPrefix)com.company.app.bundle.id $(AppIdentifierPrefix)com.microsoft.identity.universalstorage The above requirement is confirmed under these links: https://learn.microsoft.com/en-us/entra/msal/objc/howto-v2-keychain-objc?tabs=objc and also their sample app : https://github.com/AzureAD/microsoft-authentication-library-for-objc/blob/410256714ee0489d212c0cbd8772259a69e7d862/MSAL/test/app/mac/MSALMacTestApp.entitlements#L18 The problem seems to be that such keychain access groups access cannot be configured for Developer ID signed applications. Would it be possible to enable such Keychain Access groups somehow for a Developer ID signed application? Thank you for any help in advance!

Hi everyone, I’m looking for advice or shared experiences regarding the Apple Developer Program membership conversion process from an Individual membership to an Organization membership. I submitted my request more than two months ago, but the process still does not appear to have started. Current support cases: Case 102844790649 Case 102884491745 I have followed up multiple times, but several follow-up emails did not receive any response, which has made it difficult to understand the actual status of the request. I have already confirmed that: Two-factor authentication is enabled on my Apple Account My organization has a valid and publicly accessible website I am ready to proceed with the migration However, I still have not received confirmation that the migration has officially begun. I would appreciate advice from anyone who has gone through this process: Is it normal for the Individual → Organization membership conversion to take more than two months? Did you receive confirmation when the migration officially started? Were there any escalation methods that helped move the process forward? Is it safe to continue publishing apps while the migration request is pending? Any advice or shared experiences would be greatly appreciated. Thank you.

Hi, I’m pretty new to AppKit and I’m trying to make an NSTextField inside an NSTableView both: Editable Multi-line / wrapping Right now, wrapping works fine until I set: tf.isEditable = true Then the text becomes a single line. How do I make it editable while still wrapping correctly? import AppKit final class ViewController: NSViewController, NSTableViewDataSource, NSTableViewDelegate { let tableView = NSTableView() let text = String(repeating: "A", count: 500) override func viewDidLoad() { super.viewDidLoad() view = tableView tableView.addTableColumn(NSTableColumn()) tableView.usesAutomaticRowHeights = true tableView.dataSource = self tableView.delegate = self } func numberOfRows(in tableView: NSTableView) -> Int { 1 } func tableView(_ tableView: NSTableView, viewFor tableColumn: NSTableColumn?, row: Int) -> NSView? { let cell = NSTableCellView() let tf = NSTextField(wrappingLabelWithString: text) tf.lineBreakMode = .byCharWrapping if let tableColumn { tf.preferredMaxLayoutWidth = tableColumn.width } tf.isEditable = true // comment this out and wrapping works cell.addSubview(tf) tf.translatesAutoresizingMaskIntoConstraints = false NSLayoutConstraint.activate([ tf.leadingAnchor.constraint(equalTo: cell.leadingAnchor), tf.trailingAnchor.constraint(equalTo: cell.trailingAnchor), tf.topAnchor.constraint(equalTo: cell.topAnchor), tf.bottomAnchor.constraint(equalTo: cell.bottomAnchor), ]) return cell } }

Hi everyone, I'm experiencing an unusually long wait time for my TestFlight external build review and wanted to see if others are facing similar issues in 2026. Current Status: Platform: iOS App Version: 1.2.90 (Build 24) Build Type: TestFlight External Testing Current Status: In Review - not "Waiting for Review" Time in Current Status: Over 2 weeks Submission Timeline: Current Submission: Wednesday at 9:49 AM (iOS 1.2.90 Build 24) Previous Submission: March 9, 2026 at 2:20 PM (iOS 1.2.90 Build 11) - Status: Completed (Rejected) Full History: March 9, 2026 2:20 PM - Initial submission (Build 11) March 15, 2026 5:25 AM - Rejection from Apple March 24 - April 15, 2026 - Multiple back-and-forth communications (5 messages total) April 15, 2026 2:22 PM - Last response from Apple Recent (Wednesday 9:49 AM) - Resubmitted new build (Build 24) Current - Still "In Review" after 2+ weeks What I've Tried: ✅ Addressed all rejection issues from the previous review ✅ Submitted a new build with higher build number (11 → 24) ✅ Submitted expedited review request through App Store Connect ✅ Contacted Apple Developer Support via email ✅ Requested phone callback for escalation What Concerns Me: The build has been stuck in "In Review" status for over 2 weeks This is AFTER already going through a full review cycle (rejection + resubmission) Normal review times are supposed to be 24-48 hours, even with the 2026 backlog The previous review cycle took over 1 month (March 9 → April 15) This is completely blocking our beta testing program Questions for the Community: Is anyone else experiencing 2+ week "In Review" times for TestFlight external builds in 2026? Does a previous rejection cause indefinite review delays on resubmission? Has anyone successfully resolved this by canceling and submitting a brand new build? Are there effective escalation paths beyond standard support channels? Could this indicate an account-level review issue? What I Understand: Review times have increased in 2026 due to higher submission volumes Previous rejections can lead to more thorough reviews However, 2+ weeks "In Review" (not even "Waiting") seems abnormal This delay is severely impacting our development timeline and beta testing plans. Any advice or shared experiences would be greatly appreciated! Thanks in advance for your help.

Hi, We are awaiting processing of our enrolment. We have submitted everything and are still waiting. We haven't had any correspondence.

Feedback ID: FB22759977 After clicking add to apple wallet in our app, I launch the PKAddPaymentPassViewController and click next. It loads for a few seconds and then I get: [] ProvisioningOperationComposer: Step '' failed with error Error Domain=PKProvisioningErrorDomain Code=5 UserInfo={PKErrorHTTPResponseStatusCodeKey=500}

Building the Sovereign Lattice — A Deterministic 96-Path Governance & Telemetry Runtime I'm an architect focused on context-aware inference at the silicon-sensor boundary. I've built a framework that maps multi-modal physiology (HRV, temp, motion, audio) into a compact on-device vector to gate Neural Engine workloads — reducing false interrupts and preserving battery, with all processing in Secure Enclave. It aligns with your work on sleep apnea and hearing features on Watch/AirPods, and silicon roadmap under the new hardware org. Over the last development cycle, I’ve been architecting and stress-testing a system called the Sovereign Lattice: a formally verified, replayable, cryptographically anchored telemetry and execution framework built around a canonical 96-Path Omega Matrix. The goal is not to build another opaque AI stack. The goal is to build deterministic governance infrastructure for next-generation intelligent systems. The architecture combines: • Formal verification (TLA+) • Chained HotStuff consensus • Merkle-rooted replay validation • Ed25519 canonical state signing • Guardian-gated supervisory logic • Real-time telemetry orchestration • Distributed rollback containment • Adversarial threat modeling • Sovereign edge execution At the center is a bounded 96-path topology that maps: execution domains recovery states supervisory gates signal routing consensus transitions telemetry vectors cross-domain orchestration The runtime is partitioned into five Guardian domains: Γ₁ Warden Γ₂ Arbiter Γ₃ Keeper Γ₄ Sentinel Γ₅ Sealer Each domain enforces deterministic transition constraints, rollback policies, integrity checks, and consensus boundaries. Current validation results: ✅ 34/34 stress tests passing ✅ TLC-checked formal invariants ✅ 176,788 TPS burst throughput ✅ Guardian p99 latency: 0.026ms ✅ End-to-end p99 latency: 0.015ms ✅ 10K-leaf Merkle verification pipeline operational ✅ Byzantine-resilient consensus architecture specified ✅ Threat model completed across all supervisory domains The architecture is designed for future deployment across: • Healthcare telemetry systems • Institutional risk infrastructure • Autonomous coordination networks • Federated edge AI systems • Replay-verifiable governance platforms • Sovereign digital infrastructure The most important realization during development: The system becomes credible when treated as a deterministic telemetry and governance fabric — not as abstract symbolism. Everything is bounded. Everything is replayable. Everything is measurable. Everything is cryptographically attestable. The remaining frontier is live deployment: validator governance hardware attestation federated synchronization adversarial testing empirical calibration real-world supervisory execution We are approaching an era where intelligent systems will require: not just inference — but provable governance, deterministic execution, and replayable trust infrastructure. 96 Paths. 5 Guardians. 1 Lattice. Built for sovereign execution.

Hello, I'm evaluating possibility to use virtualization to setup on-permise parallel testing system for a product I work on. My compatibility range is wide, i.e. it would cover macOS 12 - 26, so any testcase needs to be executed on at least 5 different OS versions (and introducing any parallization to the test execution would mean I deal with higher number of VMs). As far as I understand, there is a constraint in Apple Software License, that limits number of OS VM installations per one physical system to 2 (section 2.B.(iii)) in case of OS downloaded from the Internet or through App Store. Clearly these days a single high-end Mac hardware could sustain more than 2 VMs running in parallel. The license also mentions it is also possible to be in a volume or maintenance license program and then the terms of this program apply instead. So I wonder how do people normally deal with the above limitation? What is the path I need to follow if I want to be able to run more than "2 additional copies or instances of" macOS on my VMs?

Hi everyone, I'm hoping someone has run into this before because it's completely blocking our release. When we try to submit a new version of our app, we get an error saying the Account Holder must accept a pending agreement. The problem is, when the Account Holder logs into App Store Connect, there are no agreements showing up to accept. To make things worse, the Business page is broken — every time we try to open it, it throws an error and won't load at all. This means we can't access the Agreements, Tax, and Banking section through the UI. Things we've already tried: Logging in as the Account Holder (not just an Admin) Trying different browsers and incognito mode Going directly to appstoreconnect.apple.com/agreements/#/ Checking email for any agreement links from Apple Nothing has worked so far. The page just errors out every time. Has anyone experienced this and found a fix? Did you have to go through Apple Support directly to get it resolved? We've already reached out to Apple Support but wanted to check here in case there's a known workaround we're missing. Any help is appreciated!

Hello, My app (Apple ID: 6760485927) has been in "Waiting for Review" status since May 7, 2026 — now over 5 days with no progress and no messages in the Resolution Center. The account is in good standing, all agreements and banking information are active, and no action appears to be required from my side. Could someone from the App Review team please check whether there is any issue with this submission, or confirm that it is simply pending reviewer assignment? Thank you.

Dear App Review Team, I'm following up on our submission with App ID: 6762607820, submitted on April 30, 2026. The build has now been sitting in 'Waiting for Review' for 12 days. During that time, we have received no status update, no rejection, no metadata feedback, and no communication of any kind. We have also reached out via Apple Developer Support regarding this issue and have not received a response from that channel either. A 12-day silence is significantly outside the typical review window Apple publishes. We need clarity on the following: The current status of the submission and the reason it has not entered active review after 12 days A concrete timeline for when the review will begin or conclude Confirmation of whether any internal flag, hold, or routing issue is affecting this build The submission is complete and ready for review on our end. We respectfully ask for a prompt response and resolution. Thank you.

Hello, our App (appleId: 6761799912) has stuck in review process since 30+ days ago, I have tried resubmit it for few times, please check the status of our App, thank you!! I understand that review times can vary and that the queue may currently be experiencing higher-than-usual volume. I'm not trying to escalate — I simply want to confirm whether: 1、There is any specific issue or blocker with this submission 2、Any additional information or documentation is required from my side 3、Or whether the app is simply still pending reviewer assignment Thank you

When working with an Objective-C project in Xcode 26.5, I'm unable to establish outlet and action connections by dragging between XIB files and the corresponding .h header files. This drag-and-drop connection works perfectly after switching to Xcode 26.3.0. In addition, under Xcode 26.5, drag-and-drop linking works normally for projects using Swift files together with XIB files. The issue only occurs with Objective-C .h files and XIB files.

Hi, We are able to successfully perform in-app provisioning and add cards to the native wallet. However, we are unable to retrieve the existing card status from the wallet. Even when the card is already added to the device or Apple Watch, the status is always returning as false for both. Could you please let us know if there are any additional configurations, entitlements, or issuer onboarding steps required to retrieve the existing card status from Apple Wallet?