Overview

In a Playground in Xcode 27 beta 6 I don't see a way to make a new page. It used to be File->New->Playground Page. That menu item is missing. The keyboard shortcut still exists, but it produces an error "No valid file actions for insertion." Am I missing an alternative? Or is this no longer possible?

FB24767077 After programmatically setting the ID to B, manually paging back to A causes the binding to update to A and then unexpectedly back to B. The view hangs between pages while SwiftUI attempts to animate toward the stale B target. The issue occurs only when an app built with Xcode 27 runs on iOS 27. It does not occur in: Xcode 27 build running on iOS 26 Xcode 26 build running on iOS 27 Xcode 26 build running on iOS 26 Steps to reproduce: Launch the minimal reproduction project Tap “Set B” to assign B directly to the scrollPosition(id:) binding Swipe right to return to page A Expected result: After paging from B back to A, the scroll position remains A once the pager settles. Actual result: The binding emits A followed by B, even though page A is the visible, settled page. The resulting stale B value causes the animation to hang between pages. Code: struct ContentView: View { @State private var selectedPage: Page? = .a var body: some View { VStack { HStack { Button("Set B") { selectedPage = .b } Text("Selected: \(selectedPage?.rawValue ?? "nil")") } PagerView(selectedPage: $selectedPage) } .onChange(of: selectedPage, initial: false) { _, newValue in print("selectedPage: \(newValue?.rawValue ?? "nil")") } } } struct PagerView: View { @Binding var selectedPage: Page? var body: some View { ScrollView(.horizontal) { LazyHStack(spacing: .zero) { ForEach(Page.allCases) { page in Text(page.rawValue) .font(.largeTitle) .frame(maxWidth: .infinity, maxHeight: .infinity) .background(page.color) .containerRelativeFrame(.horizontal) } } .scrollTargetLayout() } .frame(height: 300) .scrollIndicators(.hidden) .scrollPosition(id: $selectedPage) .scrollTargetBehavior(.paging) .animation(.default, value: selectedPage) } } enum Page: String, CaseIterable, Identifiable { case a = "A" case b = "B" case c = "C" var id: Self { self } var color: Color { switch self { case .a: .red.opacity(0.2) case .b: .green.opacity(0.2) case .c: .blue.opacity(0.2) } } }

I am seeing "authorization failed" in every browser, using multiple cards, on VPN or off VPN. I have already tried calling support and received the run-around where nobody seems to understand what I am reporting. So I thought I would create a detailed forum post where I spell everything out so a 5 yr old could interpret it. My start-up has developed a few applications that we need to sign. In order to do this one is required to enroll in the Developer program, paying $99 a year for membership. This is where the issue occurs. No matter what card I use and no matter which browser I use, the transaction never authorizes. Before anyone jumps to the wrong conclusion, this IS NOT my bank declining a transaction. This is Apple's payment system not accepting my valid debit/credit cards. I bank with Chime, and when they decline a transaction I see a notification from the app on my phone and also my email stating what happened. This happens without fail within seconds of the transaction. I'm writing all of this because nobody on the Apple support side seems to understand what is happening and nobody has offered a solution as of yet. So I am writing all of this to draw attention to the poor experience I am having with Apple right now. In hopes that someone from Apple will see it and correct this issue. Regards, Jeff

Hello, I am experiencing a serious issue with my Apple Developer Program enrollment and would appreciate help from Apple staff or anyone who has experienced the same situation. I enrolled as an Individual through the Apple Developer website and completed the €99 payment on August 8, 2026 at approximately 21:57 (Portugal time). Today is August 13, 2026, so five days have passed since the purchase. The situation is currently: Apple successfully created my €99 Apple Developer Program order. I received an official Apple Store email confirming that the order is being processed. The order has not been cancelled. I have received no refund. I have received no payment rejection. The Apple Store order page still shows the order as active and processing. The order page even displays a delivery-style progress bar with Processing → Preparing to Ship → Shipped → Delivered, although this is a digital Apple Developer Program membership. My Apple Developer account still shows “Pending”. The account page still displays “Purchase your membership” and “Your purchase may take up to 48 hours to process”, even though the membership was already purchased five days ago. So Apple Store appears to have an active paid order, while the Apple Developer system behaves as if the membership has not been purchased. I contacted Apple Developer Support. Case ID: 20000133984820 The first response I received after waiting several days did not explain what happened to the existing payment or order. I was instead advised to resubmit the enrollment through the Apple Developer app. However, this does not answer the main issue: What happened to the existing €99 purchase, and why has it remained unresolved for five days? I also currently do not have access to an iPhone, iPad, or compatible Mac, so simply restarting the enrollment through the Apple Developer app is not a practical solution for me. The web enrollment is an officially supported enrollment method, and the purchase through that method has already been completed. I have replied to Developer Support requesting escalation and asking them to investigate: whether the €99 payment was successfully captured; whether the order is correctly linked to my enrollment; why the order is still being processed; whether any identity/payment verification is required; and whether the existing enrollment can be manually reviewed and activated. My application is ready for release, including real-device testing, and this unresolved enrollment is now directly blocking the launch. I am fully willing to complete any legitimate identity, address, or payment verification Apple requires. I am also available for a telephone call if Developer Support needs to verify any information. I am not looking for a workaround or a way to bypass verification. I simply need Apple to either process the enrollment I already paid for, tell me exactly what additional verification is required, or explain clearly what has happened to the existing payment/order. Has anyone recently experienced this exact situation — payment completed, order still processing, account Pending, and “Purchase your membership” still displayed after several days? If anyone from Apple Developer Relations sees this, I would greatly appreciate a review or escalation of Case ID 20000133984820. Thank you.

I’m designing a macOS privileged-service boundary and I’d like to clarify whether a process-occurrence authentication pattern previously described by Apple DTS is a supported shipping security contract, rather than just behaviour that happens to work on current macOS. Target: current macOS 26.x, using public APIs only. Threat model An arbitrary hostile process may run as the same ordinary, non-admin login user as the application. The attacker can launch an exact second copy of the legitimately signed requester binary. The attacker cannot obtain administrator / Touch ID authorization and does not control root, SIP, Recovery, the kernel, or the code-signing infrastructure. Desired property After a fresh Human-authorized operation, a root LaunchDaemon should grant authority to one specific requester process occurrence, not to every process having the same code-signing identity. Apple DTS thread 842442 describes a pattern based on: launching the requester suspended with posix_spawn(..., POSIX_SPAWN_START_SUSPENDED); obtaining a name/task port for that process; reading its TASK_AUDIT_TOKEN; resuming the process; and accepting only Mach messages whose kernel audit trailer identifies that same process occurrence. Thread 842442 also describes this area as being on “thin compatibility ice”, which is why I do not want to build a security boundary on behaviour that Apple does not intend applications to rely on. My core question is: Can a shipping macOS application rely on a pre-bound audit_token_t obtained from a suspended child and compare it against the audit token in subsequent raw Mach message trailers as a supported security boundary for that exact process occurrence? In particular, I need to know whether the supported contract covers: distinguishing another process with the exact same signed executable; PID reuse after the original process exits; messages queued before or around sender termination; a Mach send right transferred to another process — does the receiver see the audit token of the process that actually sends each message?; later exec by the original process; and whether full audit_token_t equality is an appropriate supported comparison for this purpose. If that is not a supported shipping contract, is there a current public XPC API that provides the equivalent property: binding one privileged-service session to one exact process occurrence rather than merely to its code-signing identity? I’m specifically trying to distinguish: code identity = this is an approved executable from mission authority = this one particular authorized process occurrence I’m happy with a negative answer if macOS does not expose a stable public contract for the latter. Related Apple DTS discussion: https://developer.apple.com/forums/thread/842442

Hello, Ping Pong Connect (Apple ID 6796913239), version 1.0, build 56, was submitted on August 30, 2026 and has remained in "Waiting for Review" for 14 days. It has never entered "In Review." There are no Resolution Center messages and no requests for additional information. The demo account listed under App Review Information has been verified working. I submitted an App Review Status inquiry today via Contact Us (Case ID 102962138758). Is there anything on my side that could be holding this up, or could someone from App Review take a look? Happy to provide anything needed. Thank you.

My macOS app update has been sitting in "In Review" since Aug 31 at 12:50 PM PT — 13 days — with no messages, questions, or status changes in App Store Connect. ▎ App: NFS Files – NAS Drive Client ▎ App ID: 6789844265 ▎ Platform: macOS, version 2.0 (build 9) ▎ Submission ID: ac1eccf9-a982-492c-a6c4-c402c5f91d29 ▎ The identical iOS 2.0 submission, with the same review notes, was reviewed and approved on Sep 6. The earlier 4.3(a) concern on both platforms was addressed by removing the other network-file apps from my account and by the NFS-specific functionality described in the review notes. ▎ I've also submitted a request through the Contact Us form. Is the review still active, or is anything needed from me?

My iOS app “Artı Eksi” (version 1.0, build 13) was submitted for review on September 10, 2026, at 1:56 PM but its status has remained “Waiting for Review” without any update. The Submission ID is 1bfb533b-f2c8-4473-905c-9ee8a87ed3e6. Could you please check the submission and let me know whether there is an issue or anything I need to do?

Gidday I hope that I have posted this in the correct thread. We have had an app developed on behalf of a not-for-profit organisation that I volunteer with, and part of my role is to report every month on the total number of installations for this app. Previously, I have been able to log on to "App Store Connect" and select the app, then Analytics and on the right-hand side of the page, the date range for the life of the app. Then it would show me the total number of installations for the app's life. Can anyone out there show me how to go about this now, considering that the total date range has been removed or am I missing this entirely?

I’m using Virtualization.framework on Apple silicon with a Linux guest (VZGenericPlatformConfiguration + VZLinuxBootLoader). The VM is intentionally minimal: 2 vCPUs, 2 GiB RAM 1 virtio entropy device 2 virtio block devices (base read-only, scratch read-write) 1 virtio console with 2 ports, both isConsole = false no serial, network, sharing, socket, USB, audio, graphics, keyboard, pointing, balloon, or custom virtio devices no EFI variable store nested virtualization disabled On the normal success path the host does not call requestStop(). A destructive host stop is tracked separately and treated as failure. I need a supported way for the host to distinguish: a clean Linux guest shutdown intentionally issued by the guest after its application protocol and cleanup have completed, from an abnormal or independent shutdown path such as kernel panic, watchdog, thermal / hardware-protection shutdown, emergency shutdown, or another kernel/platform-triggered stop. guestDidStopVirtualMachine tells me that the guest stopped, but I cannot find a public contract that says which Linux/kernel/platform histories can produce that callback, nor a public shutdown reason/initiator value. My specific questions are: For VZGenericPlatformConfiguration + VZLinuxBootLoader, what is the documented complete guest-visible shutdown/reset event surface, including implicit platform events not represented by explicitly configured device arrays? What Linux-facing mechanism does VZVirtualMachine.requestStop() use in this configuration? Can guestDidStopVirtualMachine also be emitted after panic, watchdog, thermal/hardware-protection shutdown, emergency shutdown, or another guest-kernel/platform shutdown source? Are those abnormal cases guaranteed to arrive through virtualMachine(_:didStopWithError:) instead? If guestDidStopVirtualMachine can represent multiple terminal histories, is there any supported public API or documented guarantee that lets the host distinguish a clean guest system-off from the abnormal/platform-triggered cases? If not, is it correct to treat this distinction as unspecified by the public Virtualization.framework contract? I do not need private implementation details. A public/supported contract describing which terminal histories can produce each delegate callback would be enough. This matters because the host is fail-closed: it must accept PASS only after an application-level success condition and a clean guest shutdown. A successful runtime observation alone is not enough for the qualification. Environment: Apple silicon / arm64 macOS 26.6.2 (25G83) public Virtualization.framework APIs

We are working on a very space constrained custom spatial accessory. Since the form factor of the device is small, we need to add small LEDs producing small blob diameters with accordingly small distance between them. To better estimate the amount, size, and distance of the LEDs it would help to know which image sensors and field of view the six world‑facing tracking cameras have.

Im trying to enroll for Apple Developer Program. I get DUNS number mismatch even though I have registered as an organisation in D&B. How to resolve this issue

Hello, I'm currently refactoring my app to use the new Core Location APIs introduced in iOS 17 (CLLocationUpdate) and iOS 18 (CLServiceSession). I'm not quite sure how best to reproduce the current flow I've in my app right now: At app launch: If location services are authorized when in use + full accuracy: get the user current location then stop. If the services are not yet determined or denied, do nothing. Later in the app, when a user taps on a button to get its current location: Not determined: prompt and get the user current location if authorised when in use with full accuracy, then stop. Denied: present an alert (open Settings). Authorised when in use Full accuracy: get the user current location then stop. Not full accuracy: present an alert (open Settings). My issue is that I can't find a way to determine the authorisation status without prompting the user. As soon as I create a CLServiceSession to inspect the diagnostics (CLServiceSession.Diagnostic), the user is prompted. So I can't use this at app launch as I want to delay the prompt until the user first interacts with the feature actually requiring location services. Do I still need to use CLLocationManager().authorizationStatus and CLLocationManager().accuracyAuthorization at app launch? Or am I missing something in the new APIs that allow me to check a session status without prompting? Thank you!

I assume it's not just me... MacOS app reviews are taking a really long time now. The "24-48h" estimate no longer seems to be accurate. On Monday morning, I submitted both iOS and MacOS versions of our app (1137297689). The iOS version was reviewed and approved in a few hours. The MacOS versions is still waiting for review 50+ hours later. This is the second time this month this has happened. Versions released early in May had the same issue. iOS is quick, MacOS is days later (and only after I gave up and filed an expedited request). Release in April was also slow. Releases last year were normally under 24h so it's fairly recent that the release process has been super slow. It's very frustrating for our users that rely on the App Store distributions. We've had to start offering out-of-app store distribution paths due to how slow the review process is which is frustrating for us as that's more we have to maintain. Is Apple doing ANYTHING to rectify the situation?

Apple Developer Program enrollment pending for one month despite payment I’m looking for advice or help regarding my Apple Developer Program enrollment. I completed the enrollment process and paid the full 12-month membership fee, but I still cannot access or use the Developer Program. The case has now been going back and forth for approximately one month. Apple Support previously stated that I would receive a response within two business days, but that timeframe has passed without any meaningful update. I have also followed up by email, but I have not received a resolution or a clear explanation of what is still required. My company is an Estonian OÜ, and I have provided the requested company and identity information. At this point, the delay is blocking the release and testing of our iOS application, even though the membership has already been paid in full. Has anyone experienced a similar situation? Is there an Apple representative or escalation channel that can review the enrollment and help move the case forward? I would appreciate it if someone from Apple could reach out and assist with the case.

I am taking the advice in https://developer.apple.com/videos/play/tech-talks/111462/ And using (in Obj C) navigationItem.additionalOverflowItems = UIDeferredMenuElement({ provider in provider(self.persistentOverflowItems()) }) This is quite fine as I already had menus on my barButtons. But the overflow menu doesn't match my color palette. It is white, and nothing else onscreen is. White = 100% on and draws the eye, whereas overflow should be the least important item on the screen. Thus, I should be able to color it. But with Glass, we can't set the bar tint and have it do anything useful. I can set the tint color of a .backItem. But I do not see a .overflowItem to set the TintColor of. I will be tempted to not use the system Overflow (as suggested in the video and there's usually an unspoken reason for so I'd like to use the system one, just not in white), and instead favor my own More button. Am I missing something or do I need to write a feedback?

Hi all, This has been bothering me for quite a while. Basically my new iMac (bought for a few months only) started to crash randomly. I went to the genius bar and they couldn't do anything to identify the issue, I tried reinstalling the OS and even reinstalling an older version of Mac OS as well, but still seeing this issue. Today it happened twice and below are the details: Mac specs: Model Name: iMac  Model Identifier: iMac20,1  Processor Name: 10-Core Intel Core i9  Processor Speed: 3.6 GHz  Number of Processors: 1  Total Number of Cores: 10  L2 Cache (per Core): 256 KB  L3 Cache: 20 MB  Hyper-Threading Technology: Enabled  Memory: 16 GB  Boot ROM Version: 1554.100.64.0.0 (iBridge: 18.16.14556.0.0,0)  Serial Number (system): xxx  Hardware UUID: xxx  Activation Lock Status: Enabled The DiagnosticReports around the time it crashed has a lot of files with .gpuRestart, e.g.: Kernel_2021-04-27-213412_Zhuzengs-iMac.gpuRestart and file WindowServer_2021-04-27-213319_Zhuzengs-iMac.userspace_watchdog_timeout.spin in between. The details of the the first gpuRestart file Tue Apr 27 21:32:13 2021 Event: GPU Reset Date/Time: Tue Apr 27 21:32:13 2021 Application: Path: Tailspin: /Library/Logs/DiagnosticReports/gpuRestart2021-04-27-213213.tailspin GPUSubmission Trace ID: 0 OS Version: Mac OS X Version 10.15.7 (Build 19H1030) Graphics Hardware: AMD Radeon Pro 5300 Signature: 2 Report Data: GPU Log Version: 1 Restart Channel: 18 VMPT --THE STATE OF THE DRIVER AMDRadeonX6000_AMDNavi14GraphicsAccelerator state: ENABLED PCIe Device: [3:0:0], DID=0x7340, RID=0x47, SSID=0x219 TotalVideoRAMBytes: 0x00000000ff000000 (4278190080) Uptime 21:50:05.077572 [00] Channel: GFX, last reset at 0:00:00.000000 CompletedTS = 0x005be078, SubmittedTS = 0x005be079 SentTS = 0x005be078, sent at 21:49:00.896511, ScheduledTS = 0x005be079, submitted at 21:50:03.672539 Wait for Channel 18, TS 0xef924 PendingEvent: YES NumberOfPendingCB = 1, FirstPendingTS = 0x005be079, LastPendingTS = 0x005be079 FirstPendingCB: ProcessID = 225, ProcessName = WindowServer, SubmitContext = Unknown (0) GPUAddress = 0x0000000431cef000, Size = 0x000001d3, VMID = 2 ContentValidation = PASS Buffer range 0x0 .. 0x100:c0012800 80000000 80000000 c0026900 00000081 80000000 40004000 c0026900 By searching online this seems to be happening to others as well but I failed to find a common fix for this. Any help would be hugely appreciated!!!

中国大陆多数iphone手机用户在更新iOS26.6.1和26.6.2等等出现面容无法使用，相机前置无法使用了，后置可以正常使用，我作为iPhone深爱粉，我希望这个问题可以及时解决，出现这种问题的人越来越多，大陆抖音等社交媒体平台中有很多人对这个问题提出反馈

I'm posting this here after reading Quinn's post here: https://developer.apple.com/forums/thread/799000 The above entitlement is mentioned in IOUSBHostControllerInterface.h. It isn't an entitlement one can add using the + button on the Capabilities panel in Xcode. If I try to add it by hand, Xcode complains that it isn't in my profile. Is this a managed entitlement? We'd like to create a local USB "device" to represent a real device reachable over a network.

Is anyone else having issues uploading an archive to App Store Connect? I went to validate an archive of my app, and seems to hang during validation. I've tried just validating the app, and tried Transporter as well. It hangs on the analyzing app. How to troubleshoot?