macOS is the operating system for Mac.

Posts under macOS tag

200 Posts

Post

Replies

Boosts

Views

Activity

Authentication-UI refusal for a file-based certificate query on macOS
The guidance in https://developer.apple.com/forums/thread/739774 explains the context search list, the kSecMatchSearchList override and continued use of deprecated file-based APIs where that keychain model is required. For a SecItemCopyMatching query using kSecClassCertificate and an explicitly supplied file-based test keychain, what is the supported way to refuse authentication UI rather than allow a prompt? I am considering macOS 26.6.1 with the macOS 27.0 SDK; please clarify applicability to that combination and any relevant application-context restrictions. In particular, which refusal mechanism applies to the file-based path given the deprecation of earlier authentication-UI options? If access would require keychain unlock or authentication UI, is an error guaranteed, or can the query omit items and return success? A public documentation reference and any version limitations would be helpful. This is a contract question for a prospective test; I have not run it or reproduced a problem.
0
0
90
18h
productbuild and Keychain Access concern
productbuild cmd: productbuild --component /Applications/Very\ Large\ Number\ Calculator.app /Applications --sign "3rd Party Mac Developer Installer: Alain_B " /Applications/Very\ Large\ Number\ Calculator.pkg Give this error: Cannot write product to "/Applications/Very Large Number Calculator.pkg". (Could not find appropriate signing identity for “3rd Party Mac Developer Installer: Alain_B ”.) But Keychain Access show "3rd Party Mac Developer Installer" is in Certificates: 3rd Party Mac Developer Application: 10 digits (64......J5) certificate login Nov 10, 2027 at 8:02:04 AM Alain_B private key login 3rd Party Mac Developer Installer: Alain_B (64......J5) certificate login Apr 19, 2027 at 8:32:51AM Apple Development: Alain_B (35......P5) certificate login Oct 19, 2027 at 9:29:59 AM Apple Development: Alain_B (Alain_B ) private key login Apple Distribution: Alain_B (64MZBY64J5) certificate login Oct 26, 2027 at 9:36:16 AM Alain_B private key login Apple Root CA certificate login Feb 9, 2035 at 4:40:36 PM Apple Worldwide Developer Relations Certification Authority certificate login Feb 19, 2030 at 7:00:00 PM Apple Worldwide Developer Relations Certification Authority certificate login Mar 18, 2036 at 8:00:00 PM Developer ID Certification Authority certificate login Feb 1, 2027 at 5:12:15 PM Developer ID Certification Authority certificate login Sep 16, 2031 at 8:00:00 PM What can I do ? Thank you.
4
0
242
22h
Kernel panic in EXDisplayPipeService.swift:472 (Exclaves) when the mic or camera turns on during Mac Virtual Display on Vision Pro
My MacBook Pro panics and restarts every time an app turns on the microphone or the camera while I am using the Mac through Mac Virtual Display on Apple Vision Pro. It has never happened on the Mac's own screen. Eight panics on November 20, eight out of eight attempts in this setup. Every report has the same string. Only the "actual" number and the type change: panic(cpu 7 caller 0xfffffe004ecb4010): [Exclaves] $JgEXDisplayPipeDriverT605XComponent.EXDisplayPipeComponent.ini:EXDisplayPipeDriverKitT605X/EXDisplayPipeService.swift:472: Fatal error: actual: 1100,expected: 3000,type: MIC,error: 0x2000000 at PC: 0x8021020, LR: 0x8020db8The eight panics: 09:00 type MIC actual 1908 09:06 type MIC actual 2015 09:12 type MIC actual 1114 09:18 type MIC actual 2801 10:04 type CAM actual 77 10:31 type CAM actual 1414 11:12 type CAM actual 2845 11:30 type MIC actual 1100Setup: MacBook Pro (Mac17,10), Apple M5 Max, 128 GB macOS 27.2.1 (26B8132), xnu-13432.41.4~62/RELEASE_ARM64_T6050 Apple Vision Pro, visionOS [VERSION] Lid open. With Mac Virtual Display running the built-in screen goes dark, and System Information lists a single display: "Sidecar Display", 6720 x 2880, AirPlay, virtual, main. The built-in panel is not in the list. Steps: Put on Vision Pro and start Mac Virtual Display. Open anything that uses the microphone or camera. The Mac panics and restarts within a few seconds. The app does not seem to matter. The first four panics came while joining Microsoft Teams calls, and the three CAM panics came when a camera preview started (one was just opening Teams Settings > Devices). The eighth came from a different app that only records audio through AVAudioEngine on the built-in microphone, with no call running on the Mac at all. My guess, and it is only a guess: this driver draws the secure microphone and camera indicator on the built-in panel, the check at line 472 wants the indicator shown for 3000 of something, and with the built-in panel off it cannot get there. I would expect the capture to be refused, or the indicator to move to the active display, before a panic. Filed as FB25658677 with all the panic reports attached. Two questions: Is anyone else seeing this panic string, with or without a Vision Pro? I could not find it anywhere. Does anyone know whether an external microphone (USB or AirPods) takes a different path that avoids this driver? I have not tested it, since a wrong guess costs a restart.
0
0
63
1d
Supported termination of a specific unresponsive embedded XPC service instance
We are evaluating a signed macOS launcher app with an embedded XPC service. The service would own a VZVirtualMachine. Before permitting VM startup, the launcher must bind the admitted job to the actual service instance and establish any required termination authority. We need clarification on the following: Is there a public, supported mechanism for the containing app to terminate that specific service instance if it becomes unresponsive, including before its first application-level reply? If so, what API, signing, sandbox, entitlement, and authorization conditions apply? How can the termination target remain bound to that instance despite PID reuse or service regeneration? Is transfer of a task-control right from the service to the launcher, followed by task_terminate, supported for this purpose? If it requires the service to respond first, is there a supported alternative for a pre-reply hang? What supported observation confirms termination of that same process instance, separately from acceptance of a termination request? What lifecycle behavior applies if the containing launcher itself terminates unexpectedly? We understand from threads 848542 and 850709 that Virtualization is expected to reclaim a guest after its owner exits, but provides neither a teardown timeline guarantee nor a successor-process guest-completion handle. We are not requesting such a guarantee or treating service exit as proof of completed VM reclamation. Please identify applicable documentation and any platform-version restrictions.
2
0
77
1d
Accessory Access: IOUSBHostInterface can’t be opened after AAUSBAccessory.open() (QEMU-based VM app)
Hi, I’m building a macOS hypervisor app based on QEMU + Hypervisor.framework (a fork of the open-source UTM project). Following Quinn’s advice in DTS case 23599042, I’m trying to implement USB passthrough on macOS 27 with Accessory Access instead of com.apple.vm.device-access. Since the app doesn’t use the Virtualization framework, I take the IOUSBHostDevice from AAUSBAccessory.open(serviceQueue:) and forward the transfers to QEMU through usbredir. What works “Claim USB Accessory” capability (com.apple.developer.accessory-access.usb), plus com.apple.security.app-sandbox and com.apple.security.device.usb registerListener(:matchingCriteria:); the user assigns the device from the “Virtual Machine Accessories” menu bar item; usbAccessoryDidConnect fires open(serviceQueue:) returns an IOUSBHostDevice; control transfers with enqueueDeviceRequest work; configureWithValue(:matchInterfaces:) succeeds What fails Opening any interface. IOUSBHostInterface(__ioService:options:queue:interestHandler:) on the device’s child IOUSBHostInterface services always fails: Error: Unable to open io_service_t object and create user client. with reason: IOServiceOpen failed. Error: Failed to create IOUSBHostInterface. with reason: Failed [super init] IOUSBHostErrorDomain 0xe00002c9 I tried with the interfaces as delivered, after configureWithValue(1, matchInterfaces: false) and after configureWithValue(1, matchInterfaces: true). No sandbox violations are logged. Device: USB 3 mass storage stick. macOS 27.0.1, Xcode 27.2. Questions Is interface and pipe access (IOUSBHostInterface / IOUSBHostPipe) supposed to work for an AAUSBAccessory opened by an app that doesn’t use the Virtualization framework? If so, what’s the right way to get those objects? If not, is the default control endpoint the intended scope? In that case I’ll file a feedback report, since bulk and interrupt endpoints are needed for USB passthrough in non-Virtualization hypervisors. Thanks!
2
0
53
2d
State Restoration no longer works in a Mac Catalyst based app when run on macOS 27.x
As reported in FB25363417: A UIKit based app running on macOS 27.2 (or macOS 27.0.1) via Mac Catalyst no longer has functioning state restoration. Upon app restart, there is no NSUserActivity being provided to the scene in the UISceneDelegate method scene(_:willConnectTo:options:). This can be tested with Apple’s own sample app “Restoring your app’s state”. Just update the sample project with support for a Mac Catalyst build. Using Xcode 27.2 on a Mac with macOS 27.0 or 27.2, build and run the Mac Catalyst version of the app. The main screen appears with a list of products. Select any product so you see details of the product. Quit the app. Run the app again. Note that you are not returned to the previously selected product detail screen. Instead, you just see the main list of products. If you run the same app and perform the same steps on a Mac running macOS 26.x, then when the app is restarted, you correctly get returned to the previously selected product detail screen. The problem is being caused by no NSUserActivity being passed into the scene delegate on app startup. While running the app on a Mac with macOS 27.x, put a breakpoint on the initial guard statement in scene(_:willConnectTo:options:) and you will see there is no activity on app restart. This is impacting paid customers of my existing app since upgrading to macOS 27. They no longer get returned to the app’s previous state when restarting the app. It is expected that state restoration should work on macOS 27 just as well as it does under macOS 26 in an app built with Mac Catalyst.
1
0
163
2d
UITableView row reordering no longer works under macOS 27 with Mac Catalyst
Under macOS 27 using Mac Catalyst for a UIKit-based app, If you present a view controller with a table view as a form sheet or page sheet, row reordering fails to function. You can drag a row as expected but the blue movement bar never appears and if you drop the row it simply returns to its original location. The exact same view controller presented as a popover works just fine. The exact same view controller not presented as a modal (such as the app's root controller) works just fine. This is a serious bug affecting existing applications and being reported by paying customers. This has been reported as FB25038883 which includes a simple sample app demonstrating the issue.
4
1
571
2d
API to get the system pointer’s actual rendered size (respecting Accessibility → Pointer size)?
I'm positioning a tooltip-style panel relative to the mouse pointer and need to avoid overlapping the pointer glyph itself. This works fine at the default pointer size, but breaks once the user sets System Settings → Accessibility → Pointer → Pointer size to something larger than Normal — the pointer is visibly bigger on screen, but my offset doesn't grow to match, so the tooltip overlaps it. The only cursor-size-related value I've found any API expose is the ratio behind that same setting, read via: /usr/bin/defaults read com.apple.universalaccess mouseDriverCursorSizeThis returns a scale factor (1.0 = Normal, larger toward Large), not a size in points. I'm using it to scale a fixed offset, but that only approximates the real on-screen footprint of the pointer glyph — it doesn't tell me the glyph's actual rendered bounding box, so the tooltip still clips the pointer at larger sizes. Question: Is there a supported API — AppKit, Accessibility, or otherwise — that returns the system pointer's actual rendered size (bounding box, in points) reflecting the user's Pointer size setting? Or is there a different recommended approach for positioning UI relative to the live pointer without overlapping it, that doesn't depend on knowing that size directly? Minimal repro (AppKit, Swift Package Manager, no storyboard/xib — ~150 lines): enum CursorPrefs { static func readPointerScale() -> Double { let process = Process() process.executableURL = URL(fileURLWithPath: "/usr/bin/defaults") process.arguments = ["read", "com.apple.universalaccess", "mouseDriverCursorSize"] let outputPipe = Pipe() process.standardOutput = outputPipe process.standardError = Pipe() try? process.run() process.waitUntilExit() let data = outputPipe.fileHandleForReading.readDataToEndOfFile() let output = String(data: data, encoding: .utf8)?.trimmingCharacters(in: .whitespacesAndNewlines) ?? "" guard let scale = Double(output), scale >= 1.0 else { return 1.0 } return scale } } // A tracking-area view shows a tooltip-style NSPanel near NSEvent.mouseLocation, // offset by a fixed amount scaled by the value above. At Pointer size = Large, // the tooltip still overlaps the (visibly bigger) pointer glyph, because the // value is a ratio, not the glyph's rendered size in points.Steps to reproduce: Run the demo app (swift run, or open Package.swift in Xcode and Run). Open System Settings → Accessibility → Pointer → Pointer size and set it to Large. Quit and relaunch the demo (it reads the setting once at launch). Move the mouse over the gray box in the window. The floating tooltip tracks the pointer but still overlaps the now-larger pointer glyph. Environment: macOS 14.7.8 (23H730, Xcode 16.2 (16C5032a), Swift 5.9, arm64 (Apple Silicon). Happy to attach the full repro project as a zip if useful — it's a single main.swift plus an SPM manifest, no external dependencies.
3
1
1.4k
3d
Can macOS sandbox-exec confine writes to a directory that doesn’t exist yet?
I’m evaluating an offline command-line tool launched from Terminal on macOS. The parent process creates an enclosing directory, then launches the tool through /usr/bin/sandbox-exec -p with an inline profile. The tool must create its own output directory, which is absent at launch. Can a macOS sandbox profile reliably enforce all of the following for that invocation? Allow reads of the tool’s interpreter, dependencies and input files. Deny network access and creation of child processes by the sandboxed tool. Allow the tool to create /path/to/work/proof/producer001 and write beneath it, while denying writes outside that directory, including writes through symlinks or other path aliases. The proposed profile denies file-write* globally and allows it only under a subpath rule for the output directory. Does that exception cover creation of the directory itself when only its parent exists? Does deny process-fork cover all child-process creation paths, including posix_spawn? Is there a supported way to inspect or validate the effective policy for an exact command and working directory before invoking it? If sandbox-exec is unsuitable for this use, is there a supported macOS mechanism for applying these restrictions to a command-line tool launched from Terminal? A documentation reference would be helpful.
1
0
111
4d
iOS 27b3 SDK: iOS App on Mac crashes on UISearchBar focus
Our app crashes when compiled with the iOS 27 beta 3 SDK and run as an iOS app on Mac, on both macOS 26 and macOS 27, as soon as a UISearchBar receives focus. The crash is due to this exception: *** Assertion failure in BOOL _screenBasedFocusUnsupported(void)(), UIScreen.m:3.725 Accessing the focus system through UIScreen is no longer supported. ( 0 CoreFoundation 0x000000018bea31c0 __exceptionPreprocess + 176 1 libobjc.A.dylib 0x000000018b91e91c objc_exception_throw + 88 2 Foundation 0x000000018e092644 -[NSMutableDictionary(NSMutableDictionary) initWithContentsOfFile:] + 0 3 UIKitCore 0x00000001c5dae8ec _screenBasedFocusUnsupported + 272 4 UIKitCore 0x00000001c5dae960 -[UIScreen _preferredFocusedWindow] + 24 5 UIKitCore 0x00000001c4ea3a60 -[UIScreen _mainSceneReferenceBounds] + 200 6 UIKitCore 0x00000001c4ea3914 -[UIScreen _mainSceneBoundsForInterfaceOrientation:] + 40 7 UIKitCore 0x00000001c5708134 +[UINavigationBar defaultSizeForOrientation:] + 76 8 UIKitCore 0x00000001c6222c88 -[_UISearchPresentationController _layoutPresentationWithSize:transitionCoordinator:] + 704 9 UIKitCore 0x00000001c622296c -[_UISearchPresentationController containerViewWillLayoutSubviews] + 84 10 UIKitCore 0x00000001c549304c block_destroy_helper.13 + 25112 11 UIKitCore 0x00000001c549344c block_destroy_helper.13 + 26136 12 UIKitCore 0x00000001c4ea26a8 -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 1648 13 QuartzCore 0x0000000196103dbc _ZN2CA5Layer15perform_update_EPS0_P7CALayerjNS_17LayerUpdateReasonEPNS_11TransactionE + 460 14 QuartzCore 0x000000019610390c _ZN2CA5Layer17update_if_needed_EPNS_11TransactionENS_17LayerUpdateReasonE + 692 15 QuartzCore 0x0000000196035d2c _ZN2CA7Context18commit_transactionEPNS_11TransactionEdPd + 608 16 QuartzCore 0x0000000195e69520 _ZN2CA11Transaction6commitEv + 652 17 AppKit 0x0000000190fe116c __37+[NSDisplayCycle currentDisplayCycle]_block_invoke.7 + 44 18 CoreFoundation 0x000000018be34ad0 __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 28 19 CoreFoundation 0x000000018be34a10 __CFRunLoopDoBlocks + 396 20 CoreFoundation 0x000000018be33e54 __CFRunLoopRun + 2356 21 CoreFoundation 0x000000018bf06234 _CFRunLoopRunSpecificWithOptions + 532 22 HIToolbox 0x0000000198c1f560 RunCurrentEventLoopInMode + 320 23 HIToolbox 0x0000000198c228bc ReceiveNextEventCommon + 488 24 HIToolbox 0x0000000198dac14c _BlockUntilNextEventMatchingListInMode + 48 25 AppKit 0x00000001909163d0 _DPSBlockUntilNextEventMatchingListInMode + 228 26 AppKit 0x000000019026a084 _DPSNextEvent + 576 27 AppKit 0x0000000190dff96c -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688 28 AppKit 0x0000000190dff678 -[NSApplication(NSEventRouting) nextEventMatchingMask:untilDate:inMode:dequeue:] + 72 29 AppKit 0x000000019025d13c -[NSApplication run] + 368 30 AppKit 0x00000001902357b0 NSApplicationMain + 880 31 AppKit 0x000000019047c958 +[NSWindow _savedFrameFromString:] + 0 32 UIKitMacHelper 0x00000001aa2651bc UINSApplicationMain + 972 33 UIKitCore 0x00000001c4e1aed4 UIApplicationMain + 144 34 UIKitCore 0x00000001c548bda0 block_destroy_helper.31 + 8880 35 DigitalConcertHall.debug.dylib 0x0000000106e41bd8 $sSo21UIApplicationDelegateP5UIKitE4mainyyFZ + 128 36 DigitalConcertHall.debug.dylib 0x0000000106e41b4c $s18DigitalConcertHall11AppDelegateC5$mainyyFZ + 32 37 DigitalConcertHall.debug.dylib 0x0000000106e4afc0 __debug_main_executable_dylib_entry_point + 28 38 dyld 0x000000018b9ac4e4 start + 6992 ) I could not test with the iOS 27 beta 4 SDK due to this blocking issue: https://developer.apple.com/forums/thread/839012 However, when I tried to set up a simple sample project, I could not reproduce the issue. Does anybody know what might be causing this? I filed feedback FB24201508
8
2
2.1k
5d
Credential Provider Extension should allow BE=0, BS=0 for device-bound passkeys
In these threads, it was clarified that Credential Provider Extensions must set both Backup Eligible (BE) and Backup State (BS) flags to 1 in authenticator data: https://developer.apple.com/forums/thread/745605 https://developer.apple.com/forums/thread/787629 However, I'm developing a passkey manager that intentionally stores credentials only on the local device. My implementation uses: kSecAttrAccessibleWhenUnlockedThisDeviceOnly for keychain items kSecAttrTokenIDSecureEnclave for private keys No iCloud sync or backup These credentials are, by definition, single-device credentials. According to the WebAuthn specification, they should be represented with BE=0, BS=0. Currently, I'm forced to set BE=1, BS=1 to make the extension work, which misrepresents the actual backup status to relying parties. This is problematic because: Servers using BE/BS flags for security policies will incorrectly classify these as synced passkeys Users who specifically want device-bound credentials for higher security cannot get accurate flag representation Request: Please allow Credential Provider Extensions to return credentials with BE=0, BS=0 for legitimate device-bound passkey implementations. Environment: macOS 26.2 (25C56), Xcode 26.2 (17C52)
2
5
1.4k
5d
Battery chart time labels shifted hours ahead on macOS 27 (endOfDay wrong in BatteryUI.plist)
the "last 24 hours" battery level and screen on usage charts in system settings > battery have the hour labels shifted way ahead of real time. the bars are in the right order, the axis is just wrong. at 17:13 it was showing stuff up to like 23:00. at 10:05 a few days later it was about 12 hours ahead. the "last charged to 100%" time above the chart is correct tho. my clock and time zone are fine (asia/manila, set automatically, synced). the battery data itself is right too, i checked the power log and the plug in and unplug times match what actually happened. i dug into it and found the problem in `/private/var/db/powerlog/Library/BatteryLife/Debug/BatteryUI.plist`, which is what the battery pane gets from PerfPowerServices. `endOfDay` comes back as the next hour instead of midnight: PLBatteryUIQueryTime 2026-10-24 17:13:25 (local) endOfHour 2026-10-24 18:00:00 <- correct endOfDay 2026-10-24 18:00:00 <- should be 2026-10-25 00:00:00 so the chart puts 00:00 at 18:00 yesterday and everything ends up 6 hours off. it looks like the chart always labels its right edge as 24:00, so the further you are from midnight the worse it gets. restarting PerfPowerServices (`sudo killall PerfPowerServices`) doesn't fix it, the new process sends the same values right away. macos 27.0.1 (26A434). this was fine on macos 26. looks like the same bug as https://developer.apple.com/forums/thread/852392
0
0
136
5d
CloudKit sync fails in macOS TestFlight build – sandbox denies com.apple.cloudd
I have a macOS SwiftUI app using SwiftData with CloudKit synchronization. Bundle ID: com.mjsapps.PhrasePin CloudKit container: iCloud.com.mjsapps.PhrasePin CloudKit synchronization works when running the app from Xcode using the Development environment. However, synchronization does not work in the TestFlight / Production build. The Production schema has been deployed successfully. The TestFlight build has the expected entitlements, including: com.apple.developer.icloud-container-environment = Production com.apple.developer.icloud-container-identifiers = iCloud.com.mjsapps.PhrasePin com.apple.developer.icloud-services = CloudKit com.apple.security.app-sandbox = true com.apple.security.network.client = true The TestFlight build is signed as: Authority=TestFlight Beta Distribution Identifier=com.mjsapps.PhrasePin TeamIdentifier=8D6TX86CQK CloudKit/Core Data logging shows that the app is trying to use: container=iCloud.com.mjsapps.PhrasePin:Production but synchronization fails with: CKErrorDomain Code=6 Error connecting to CloudKit daemon NSCocoaErrorDomain Code=4099 The macOS sandbox log shows: Sandbox: PhrasePin(...) deny(1) mach-lookup com.apple.cloudd As a result, no com.apple.coredata.cloudkit.zone is created in the Production private database and no SwiftData records are synchronized. The problem has been reproduced on: macOS Sequoia 15.7.7 macOS Sequoia 15.7.9 The same app works with CloudKit in Development when run from Xcode. I have already submitted a Feedback Assistant report, but have not received a response. Has anyone seen this behavior with SwiftData + CloudKit in a sandboxed macOS TestFlight build? Is there an additional entitlement or provisioning requirement needed for access to com.apple.cloudd in Production?
1
0
67
5d
macos 27 - unexpected/new errno from BSD socket connect() when pending connections exceed backlog
Please consider the trivial C program attached to this thread. The code creates a socket() and listen()s for connections, but (intentionally) doesn't accept() the connections. The listen() is done using a small backlog (of 1). This test then does several connect() attempts and expects that the connect() attempts will accumulate in the pending queue and once the queue exceeds the backlog limit, then as specified in man listen: The backlog parameter defines the maximum length for the queue of pending connections. If a connection request arrives with the queue full, the client may receive an error with an indication of ECONNREFUSED. then the connect() attempt will receive a ECONNREFUSED. However, in macos 27, such a connect() attempt leads to ECONNRESET (Connection reset by peer) instead of ECONNREFUSED. Is this expected? Experiments show that prior versions of macos were returning a ETIMEDOUT for such connect() attempts. If this new error is expected from connect() when the backlog limit has exceeded, should it be specified in the man listen documentation? Rename the attached main.c.txt to main.c. Compiling the attached program on macos 27, using clang main.c and then running ./a.out results in: ----------------------- MacOS version: 27.0.1 Kernel version: Darwin Kernel Version 27.0.0: Tue Aug 11 21:02:16 PDT 2026; root:xnu-13432.1.9~1/RELEASE_ARM64_T8112 ----------------------- started server at at 127.0.0.1:52753 with a backlog of 1 connect() attempt 1 - connected connect() attempt 2 - connected connect() attempt 3 - connected connect() attempt 4 - connected connect() attempt 5 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 6 - connected connect() attempt 7 - connected connect() attempt 8 - connected connect() attempt 9 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 10 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 11 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 On a related note, it's unclear why several of the connect() attempts succeeded instead of just 1 of them succeeding. On prior versions of macos, the output of the same program is: ----------------------- MacOS version: 26.7.1 Kernel version: Darwin Kernel Version 25.6.0: Tue Aug 18 17:49:13 PDT 2026; root:xnu-12377.161.15.700.19~2/RELEASE_ARM64_T6000 ----------------------- started server at at 127.0.0.1:52451 with a backlog of 1 connect() attempt 1 - connected connect() attempt 2 - failed to connect() - Operation timed out connect() attempt 3 - failed to connect() - Operation timed out connect() attempt 4 - failed to connect() - Operation timed out connect() attempt 5 - failed to connect() - Operation timed out connect() attempt 6 - failed to connect() - Operation timed out connect() attempt 7 - failed to connect() - Operation timed out connect() attempt 8 - failed to connect() - Operation timed out connect() attempt 9 - failed to connect() - Operation timed out connect() attempt 10 - failed to connect() - Operation timed out connect() attempt 11 - failed to connect() - Operation timed out and this output is much more understandable and deterministic. main.c.txt
3
0
380
6d
Supported App Sandbox metadata access through an inherited file descriptor, without reopening the object
We are evaluating a macOS design before implementation. This is a platform-support question, not a report of an observed runtime failure. No actual controller executable, helper executable or deployment configuration has been selected or qualified. Our objective is to let a small, fixed-purpose helper examine an already-open object’s identity and access control list (ACL) metadata while preserving the original object reference and ownership. Proposed configuration A trusted controller would launch one native C helper using an explicit executable target and posix_spawn. The controller would need to qualify for the documented nonsandboxed-parent case, without a conflicting inherited sandbox. We do not assume that an absent entitlement alone establishes this. The helper would be the main executable of its own signed application bundle, using its own ordinary App Sandbox rather than inheriting the controller’s sandbox. Its proposed additional filesystem permission would be com.apple.security.temporary-exception.files.absolute-path.read-only, containing exactly two fixed directory entries beneath a user’s development workspace, outside the helper’s container. The literal private paths are omitted. The controller would already own a read-only file descriptor for one regular file or directory within those trees. It would retain its original reference and pass a known duplicate referring to the same open object to the helper. The helper would perform one metadata observation. The proposed operations are fstat for object identity and fgetattrlist requesting ATTR_CMN_RETURNED_ATTRS and ATTR_CMN_EXTENDED_SECURITY, with FSOPT_REPORT_FULLSIZE and without FSOPT_PACK_INVAL_ATTRS. Required boundaries The helper must use only the inherited descriptor for the subject observation. The design does not permit: Reopening or resolving the subject through a pathname, bookmark or URL. Substituting a copied file or another object reference. Reading file contents, enumerating directories, changing permissions, or modifying shared descriptor flags or file offsets. Expanding the exception to an ancestor, home directory or broader workspace. Disabling an existing sandbox or using private interfaces to bypass restrictions. Parent-side traversal and identity checks remain separate responsibilities. Strict ancestor directories are not additional helper ACL subjects. We understand that a read-only directory exception and ordinary sandbox/container capabilities may permit more than the helper’s intended metadata operations. Metadata-only behaviour would be a reviewed-code obligation; we are not asking App Sandbox to enforce an exact metadata-only operation filter. Questions Supported launch and activation: Under what documented parent-context, signing, bundle, container and launch conditions can this helper establish its own ordinary App Sandbox? What supported mechanism or guarantee establishes that the sandbox is effective before the subject metadata operation? Required metadata permissions: Does the proposed read-only exception support fstat and the specified extended-security fgetattrlist request through an inherited read-only descriptor, for both regular files and directories? Please distinguish descriptor survival from permission to perform these operations, including any additional access-control conditions. Scope, identity and lifetime: What documented behaviour applies to descendant coverage, aliases, hard links, renames or namespace changes after the descriptor was opened? Please distinguish the lifetime of the inherited object reference from the lifetime of the static directory permission. Our design would refuse uncertainty rather than reopen, rebind or widen access. Evidence and support boundary: Which public documentation, interfaces or authoritative guarantees support this exact composition, and which parts require separate empirical qualification? Please identify applicable macOS versions and restrictions. Distinguish platform support from any distribution or App Store review requirements. If these requirements cannot be combined through supported interfaces, please identify the incompatible requirement. An approach requiring broader access, pathname reopening, a replacement object or a different handoff architecture would be a design change requiring separate review, not a solution within the stated constraints. Permission failures, unsupported requests and incomplete metadata would remain unavailable results. They would not be interpreted as proof that an ACL is absent. Complete ACL-absence interpretation and native resource bounds remain separate qualification questions. Apple material already reviewed Resolving App Sandbox Inheritance Problems App Sandbox Temporary Exception Entitlements Accessing files from the macOS App Sandbox
1
0
246
6d
Control fan speed on MacPro 3.1 (early 2008)
I have a MacPro 3.1 (early 2008) that has Linux installed on it (Debian 13). One of the fans runs at top speed of 2500 rpm because some sensor in the board can't report the temperature to the OS. The Motherboard model is Mac-F42C88C8. Searched the internet to see if I could find any information on how to identify the sensor or the SMC information about it. I would like to know if there is any information that anyone knows about this and where could I start trying to make a driver to control the fan by getting the value in the sensor. I can see in the program coolercontrol in Linux the Fan that is at high speed is named 'IO' Thanks Regards
0
0
97
1w
Sandboxed app can't delete AppleDouble (._) files of quarantined files on exFAT, even with user-selected access.
My Mac App Store utility removes Mac metadata files (._* AppleDouble files and .DS_Store) from external drives formatted exFAT or FAT32. The app is sandboxed with com.apple.security.files.user-selected.read-write and com.apple.security.files.bookmarks.app-scope. The user grants access to the volume through NSOpenPanel. Deleting a ._ file works, except when its companion file carries com.apple.quarantine (for example, a file downloaded with Safari and copied to the drive with Finder). Then: let partner = volume + "/Nirvana.zip" // has com.apple.quarantine let appleDouble = volume + "/._Nirvana.zip" removexattr(partner, "com.apple.quarantine", XATTR_NOFOLLOW) // -1, errno 1 (EPERM) unlink(appleDouble) // -1, errno 1 (EPERM)The same unlink succeeds from Terminal (not sandboxed, without Full Disk Access). On exFAT the extended attributes live in the ._ file, so I assume the sandbox refuses because deleting it would remove the quarantine attribute. Tried, with no change: Full Disk Access granted to the app. Adding com.apple.security.files.user-selected.executable (verified in the built app with codesign -d --entitlements -). On a real drive (a music library), about 71% of the ._ files belong to quarantined files, so this is most of what users want removed. Is there a supported way for a sandboxed app to remove these files: an entitlement, an API, or an explicit user action? If not, can you confirm it's intended behavior, so I can explain it accurately to users? macOS 27.2, Xcode 27.2, Apple silicon. Focused sample project available (one source file). DTS case 23240704.
5
0
174
1w
Verifying a stored file-based Keychain trusted-application requirement
I'm evaluating a macOS file-based Keychain ACL that should authorize one application identity, defined by an intended code-signing requirement. The application is a shared Python interpreter; I understand that trusting it does not restrict access to an individual script. I read the related Apple Developer Forums discussion, which explains that complete ACL introspection is not supported and that the stored trusted-application code-signing requirement is accessible through SPI rather than public API. My narrower question is whether there is a supported verification operation that does not require exposing that requirement: Given a SecTrustedApplicationRef obtained through SecACLCopyContents, can a public API establish that its stored caller-matching requirement is no broader than the intended application requirement? Confirming that the intended application is accepted would establish only that it matches, not that additional application identities are excluded. I also don't want to assume that CFEqual against a newly created reference, matching paths, or matching SecTrustedApplicationCopyData results proves equivalent authorization. Apple's documentation describes the CopyData result as opaque. If this comparison is unsupported, what documented provisioning or operating-system enforcement guarantees should an application rely on instead? Is controlled provisioning the intended boundary, or is a different supported Keychain design appropriate? Most importantly, if verifying the exact trusted-application restriction isn't supported, what is Apple's recommended secure approach for allowing a local Python trading application to retrieve Keychain credentials without granting access to every script using the same Python interpreter? A fake-only example using a disposable test Keychain and synthetic generic-password item has been prepared but has not been built or run because full Xcode was unavailable. This is an API-contract question; no runtime failure or ACL attack is claimed, and no assumption is made that published source exactly matches the installed framework.
1
0
90
1w
Is NavigationSplitView on macOS 27 broken?
On macOS 27 Beta 2, a simple NavigationSplitView example exhibits bizarre behaviour when the window is resized. The sidebar seemingly expands and collapses at random as the window is resized. The symptoms can be exacerbated with toolbar items. The sidebar appears to behave correctly when an inspector view is not present. Copy paste the code below into a new Xcode 27 project and run on macOS 27 and then resize the window: File -> New -> Project... -> App import SwiftUI @main struct MyApp: App { var body: some Scene { WindowGroup { ContentView() } } } struct ContentView: View { var body: some View { NavigationSplitView { Text("Sidebar") } detail: { Text("Content") } .inspector(isPresented: .constant(true)) { Text("Inspector") } } } Adding .frame or .inspectorColumnWidth to any of the Text views does not appear to fix the issues. macOS: 27.0 Beta (26A5368g) Xcode: 27.0 beta 2 (27A5209h)
Topic: UI Frameworks SubTopic: SwiftUI Tags:
6
1
771
1w
Authentication-UI refusal for a file-based certificate query on macOS
The guidance in https://developer.apple.com/forums/thread/739774 explains the context search list, the kSecMatchSearchList override and continued use of deprecated file-based APIs where that keychain model is required. For a SecItemCopyMatching query using kSecClassCertificate and an explicitly supplied file-based test keychain, what is the supported way to refuse authentication UI rather than allow a prompt? I am considering macOS 26.6.1 with the macOS 27.0 SDK; please clarify applicability to that combination and any relevant application-context restrictions. In particular, which refusal mechanism applies to the file-based path given the deprecation of earlier authentication-UI options? If access would require keychain unlock or authentication UI, is an error guaranteed, or can the query omit items and return success? A public documentation reference and any version limitations would be helpful. This is a contract question for a prospective test; I have not run it or reproduced a problem.
Replies
0
Boosts
0
Views
90
Activity
18h
productbuild and Keychain Access concern
productbuild cmd: productbuild --component /Applications/Very\ Large\ Number\ Calculator.app /Applications --sign "3rd Party Mac Developer Installer: Alain_B " /Applications/Very\ Large\ Number\ Calculator.pkg Give this error: Cannot write product to "/Applications/Very Large Number Calculator.pkg". (Could not find appropriate signing identity for “3rd Party Mac Developer Installer: Alain_B ”.) But Keychain Access show "3rd Party Mac Developer Installer" is in Certificates: 3rd Party Mac Developer Application: 10 digits (64......J5) certificate login Nov 10, 2027 at 8:02:04 AM Alain_B private key login 3rd Party Mac Developer Installer: Alain_B (64......J5) certificate login Apr 19, 2027 at 8:32:51AM Apple Development: Alain_B (35......P5) certificate login Oct 19, 2027 at 9:29:59 AM Apple Development: Alain_B (Alain_B ) private key login Apple Distribution: Alain_B (64MZBY64J5) certificate login Oct 26, 2027 at 9:36:16 AM Alain_B private key login Apple Root CA certificate login Feb 9, 2035 at 4:40:36 PM Apple Worldwide Developer Relations Certification Authority certificate login Feb 19, 2030 at 7:00:00 PM Apple Worldwide Developer Relations Certification Authority certificate login Mar 18, 2036 at 8:00:00 PM Developer ID Certification Authority certificate login Feb 1, 2027 at 5:12:15 PM Developer ID Certification Authority certificate login Sep 16, 2031 at 8:00:00 PM What can I do ? Thank you.
Replies
4
Boosts
0
Views
242
Activity
22h
Kernel panic in EXDisplayPipeService.swift:472 (Exclaves) when the mic or camera turns on during Mac Virtual Display on Vision Pro
My MacBook Pro panics and restarts every time an app turns on the microphone or the camera while I am using the Mac through Mac Virtual Display on Apple Vision Pro. It has never happened on the Mac's own screen. Eight panics on November 20, eight out of eight attempts in this setup. Every report has the same string. Only the "actual" number and the type change: panic(cpu 7 caller 0xfffffe004ecb4010): [Exclaves] $JgEXDisplayPipeDriverT605XComponent.EXDisplayPipeComponent.ini:EXDisplayPipeDriverKitT605X/EXDisplayPipeService.swift:472: Fatal error: actual: 1100,expected: 3000,type: MIC,error: 0x2000000 at PC: 0x8021020, LR: 0x8020db8The eight panics: 09:00 type MIC actual 1908 09:06 type MIC actual 2015 09:12 type MIC actual 1114 09:18 type MIC actual 2801 10:04 type CAM actual 77 10:31 type CAM actual 1414 11:12 type CAM actual 2845 11:30 type MIC actual 1100Setup: MacBook Pro (Mac17,10), Apple M5 Max, 128 GB macOS 27.2.1 (26B8132), xnu-13432.41.4~62/RELEASE_ARM64_T6050 Apple Vision Pro, visionOS [VERSION] Lid open. With Mac Virtual Display running the built-in screen goes dark, and System Information lists a single display: "Sidecar Display", 6720 x 2880, AirPlay, virtual, main. The built-in panel is not in the list. Steps: Put on Vision Pro and start Mac Virtual Display. Open anything that uses the microphone or camera. The Mac panics and restarts within a few seconds. The app does not seem to matter. The first four panics came while joining Microsoft Teams calls, and the three CAM panics came when a camera preview started (one was just opening Teams Settings > Devices). The eighth came from a different app that only records audio through AVAudioEngine on the built-in microphone, with no call running on the Mac at all. My guess, and it is only a guess: this driver draws the secure microphone and camera indicator on the built-in panel, the check at line 472 wants the indicator shown for 3000 of something, and with the built-in panel off it cannot get there. I would expect the capture to be refused, or the indicator to move to the active display, before a panic. Filed as FB25658677 with all the panic reports attached. Two questions: Is anyone else seeing this panic string, with or without a Vision Pro? I could not find it anywhere. Does anyone know whether an external microphone (USB or AirPods) takes a different path that avoids this driver? I have not tested it, since a wrong guess costs a restart.
Replies
0
Boosts
0
Views
63
Activity
1d
Supported termination of a specific unresponsive embedded XPC service instance
We are evaluating a signed macOS launcher app with an embedded XPC service. The service would own a VZVirtualMachine. Before permitting VM startup, the launcher must bind the admitted job to the actual service instance and establish any required termination authority. We need clarification on the following: Is there a public, supported mechanism for the containing app to terminate that specific service instance if it becomes unresponsive, including before its first application-level reply? If so, what API, signing, sandbox, entitlement, and authorization conditions apply? How can the termination target remain bound to that instance despite PID reuse or service regeneration? Is transfer of a task-control right from the service to the launcher, followed by task_terminate, supported for this purpose? If it requires the service to respond first, is there a supported alternative for a pre-reply hang? What supported observation confirms termination of that same process instance, separately from acceptance of a termination request? What lifecycle behavior applies if the containing launcher itself terminates unexpectedly? We understand from threads 848542 and 850709 that Virtualization is expected to reclaim a guest after its owner exits, but provides neither a teardown timeline guarantee nor a successor-process guest-completion handle. We are not requesting such a guarantee or treating service exit as proof of completed VM reclamation. Please identify applicable documentation and any platform-version restrictions.
Replies
2
Boosts
0
Views
77
Activity
1d
Accessory Access: IOUSBHostInterface can’t be opened after AAUSBAccessory.open() (QEMU-based VM app)
Hi, I’m building a macOS hypervisor app based on QEMU + Hypervisor.framework (a fork of the open-source UTM project). Following Quinn’s advice in DTS case 23599042, I’m trying to implement USB passthrough on macOS 27 with Accessory Access instead of com.apple.vm.device-access. Since the app doesn’t use the Virtualization framework, I take the IOUSBHostDevice from AAUSBAccessory.open(serviceQueue:) and forward the transfers to QEMU through usbredir. What works “Claim USB Accessory” capability (com.apple.developer.accessory-access.usb), plus com.apple.security.app-sandbox and com.apple.security.device.usb registerListener(:matchingCriteria:); the user assigns the device from the “Virtual Machine Accessories” menu bar item; usbAccessoryDidConnect fires open(serviceQueue:) returns an IOUSBHostDevice; control transfers with enqueueDeviceRequest work; configureWithValue(:matchInterfaces:) succeeds What fails Opening any interface. IOUSBHostInterface(__ioService:options:queue:interestHandler:) on the device’s child IOUSBHostInterface services always fails: Error: Unable to open io_service_t object and create user client. with reason: IOServiceOpen failed. Error: Failed to create IOUSBHostInterface. with reason: Failed [super init] IOUSBHostErrorDomain 0xe00002c9 I tried with the interfaces as delivered, after configureWithValue(1, matchInterfaces: false) and after configureWithValue(1, matchInterfaces: true). No sandbox violations are logged. Device: USB 3 mass storage stick. macOS 27.0.1, Xcode 27.2. Questions Is interface and pipe access (IOUSBHostInterface / IOUSBHostPipe) supposed to work for an AAUSBAccessory opened by an app that doesn’t use the Virtualization framework? If so, what’s the right way to get those objects? If not, is the default control endpoint the intended scope? In that case I’ll file a feedback report, since bulk and interrupt endpoints are needed for USB passthrough in non-Virtualization hypervisors. Thanks!
Replies
2
Boosts
0
Views
53
Activity
2d
State Restoration no longer works in a Mac Catalyst based app when run on macOS 27.x
As reported in FB25363417: A UIKit based app running on macOS 27.2 (or macOS 27.0.1) via Mac Catalyst no longer has functioning state restoration. Upon app restart, there is no NSUserActivity being provided to the scene in the UISceneDelegate method scene(_:willConnectTo:options:). This can be tested with Apple’s own sample app “Restoring your app’s state”. Just update the sample project with support for a Mac Catalyst build. Using Xcode 27.2 on a Mac with macOS 27.0 or 27.2, build and run the Mac Catalyst version of the app. The main screen appears with a list of products. Select any product so you see details of the product. Quit the app. Run the app again. Note that you are not returned to the previously selected product detail screen. Instead, you just see the main list of products. If you run the same app and perform the same steps on a Mac running macOS 26.x, then when the app is restarted, you correctly get returned to the previously selected product detail screen. The problem is being caused by no NSUserActivity being passed into the scene delegate on app startup. While running the app on a Mac with macOS 27.x, put a breakpoint on the initial guard statement in scene(_:willConnectTo:options:) and you will see there is no activity on app restart. This is impacting paid customers of my existing app since upgrading to macOS 27. They no longer get returned to the app’s previous state when restarting the app. It is expected that state restoration should work on macOS 27 just as well as it does under macOS 26 in an app built with Mac Catalyst.
Replies
1
Boosts
0
Views
163
Activity
2d
UITableView row reordering no longer works under macOS 27 with Mac Catalyst
Under macOS 27 using Mac Catalyst for a UIKit-based app, If you present a view controller with a table view as a form sheet or page sheet, row reordering fails to function. You can drag a row as expected but the blue movement bar never appears and if you drop the row it simply returns to its original location. The exact same view controller presented as a popover works just fine. The exact same view controller not presented as a modal (such as the app's root controller) works just fine. This is a serious bug affecting existing applications and being reported by paying customers. This has been reported as FB25038883 which includes a simple sample app demonstrating the issue.
Replies
4
Boosts
1
Views
571
Activity
2d
API to get the system pointer’s actual rendered size (respecting Accessibility → Pointer size)?
I'm positioning a tooltip-style panel relative to the mouse pointer and need to avoid overlapping the pointer glyph itself. This works fine at the default pointer size, but breaks once the user sets System Settings → Accessibility → Pointer → Pointer size to something larger than Normal — the pointer is visibly bigger on screen, but my offset doesn't grow to match, so the tooltip overlaps it. The only cursor-size-related value I've found any API expose is the ratio behind that same setting, read via: /usr/bin/defaults read com.apple.universalaccess mouseDriverCursorSizeThis returns a scale factor (1.0 = Normal, larger toward Large), not a size in points. I'm using it to scale a fixed offset, but that only approximates the real on-screen footprint of the pointer glyph — it doesn't tell me the glyph's actual rendered bounding box, so the tooltip still clips the pointer at larger sizes. Question: Is there a supported API — AppKit, Accessibility, or otherwise — that returns the system pointer's actual rendered size (bounding box, in points) reflecting the user's Pointer size setting? Or is there a different recommended approach for positioning UI relative to the live pointer without overlapping it, that doesn't depend on knowing that size directly? Minimal repro (AppKit, Swift Package Manager, no storyboard/xib — ~150 lines): enum CursorPrefs { static func readPointerScale() -> Double { let process = Process() process.executableURL = URL(fileURLWithPath: "/usr/bin/defaults") process.arguments = ["read", "com.apple.universalaccess", "mouseDriverCursorSize"] let outputPipe = Pipe() process.standardOutput = outputPipe process.standardError = Pipe() try? process.run() process.waitUntilExit() let data = outputPipe.fileHandleForReading.readDataToEndOfFile() let output = String(data: data, encoding: .utf8)?.trimmingCharacters(in: .whitespacesAndNewlines) ?? "" guard let scale = Double(output), scale >= 1.0 else { return 1.0 } return scale } } // A tracking-area view shows a tooltip-style NSPanel near NSEvent.mouseLocation, // offset by a fixed amount scaled by the value above. At Pointer size = Large, // the tooltip still overlaps the (visibly bigger) pointer glyph, because the // value is a ratio, not the glyph's rendered size in points.Steps to reproduce: Run the demo app (swift run, or open Package.swift in Xcode and Run). Open System Settings → Accessibility → Pointer → Pointer size and set it to Large. Quit and relaunch the demo (it reads the setting once at launch). Move the mouse over the gray box in the window. The floating tooltip tracks the pointer but still overlaps the now-larger pointer glyph. Environment: macOS 14.7.8 (23H730, Xcode 16.2 (16C5032a), Swift 5.9, arm64 (Apple Silicon). Happy to attach the full repro project as a zip if useful — it's a single main.swift plus an SPM manifest, no external dependencies.
Replies
3
Boosts
1
Views
1.4k
Activity
3d
Can macOS sandbox-exec confine writes to a directory that doesn’t exist yet?
I’m evaluating an offline command-line tool launched from Terminal on macOS. The parent process creates an enclosing directory, then launches the tool through /usr/bin/sandbox-exec -p with an inline profile. The tool must create its own output directory, which is absent at launch. Can a macOS sandbox profile reliably enforce all of the following for that invocation? Allow reads of the tool’s interpreter, dependencies and input files. Deny network access and creation of child processes by the sandboxed tool. Allow the tool to create /path/to/work/proof/producer001 and write beneath it, while denying writes outside that directory, including writes through symlinks or other path aliases. The proposed profile denies file-write* globally and allows it only under a subpath rule for the output directory. Does that exception cover creation of the directory itself when only its parent exists? Does deny process-fork cover all child-process creation paths, including posix_spawn? Is there a supported way to inspect or validate the effective policy for an exact command and working directory before invoking it? If sandbox-exec is unsuitable for this use, is there a supported macOS mechanism for applying these restrictions to a command-line tool launched from Terminal? A documentation reference would be helpful.
Replies
1
Boosts
0
Views
111
Activity
4d
iOS 27b3 SDK: iOS App on Mac crashes on UISearchBar focus
Our app crashes when compiled with the iOS 27 beta 3 SDK and run as an iOS app on Mac, on both macOS 26 and macOS 27, as soon as a UISearchBar receives focus. The crash is due to this exception: *** Assertion failure in BOOL _screenBasedFocusUnsupported(void)(), UIScreen.m:3.725 Accessing the focus system through UIScreen is no longer supported. ( 0 CoreFoundation 0x000000018bea31c0 __exceptionPreprocess + 176 1 libobjc.A.dylib 0x000000018b91e91c objc_exception_throw + 88 2 Foundation 0x000000018e092644 -[NSMutableDictionary(NSMutableDictionary) initWithContentsOfFile:] + 0 3 UIKitCore 0x00000001c5dae8ec _screenBasedFocusUnsupported + 272 4 UIKitCore 0x00000001c5dae960 -[UIScreen _preferredFocusedWindow] + 24 5 UIKitCore 0x00000001c4ea3a60 -[UIScreen _mainSceneReferenceBounds] + 200 6 UIKitCore 0x00000001c4ea3914 -[UIScreen _mainSceneBoundsForInterfaceOrientation:] + 40 7 UIKitCore 0x00000001c5708134 +[UINavigationBar defaultSizeForOrientation:] + 76 8 UIKitCore 0x00000001c6222c88 -[_UISearchPresentationController _layoutPresentationWithSize:transitionCoordinator:] + 704 9 UIKitCore 0x00000001c622296c -[_UISearchPresentationController containerViewWillLayoutSubviews] + 84 10 UIKitCore 0x00000001c549304c block_destroy_helper.13 + 25112 11 UIKitCore 0x00000001c549344c block_destroy_helper.13 + 26136 12 UIKitCore 0x00000001c4ea26a8 -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 1648 13 QuartzCore 0x0000000196103dbc _ZN2CA5Layer15perform_update_EPS0_P7CALayerjNS_17LayerUpdateReasonEPNS_11TransactionE + 460 14 QuartzCore 0x000000019610390c _ZN2CA5Layer17update_if_needed_EPNS_11TransactionENS_17LayerUpdateReasonE + 692 15 QuartzCore 0x0000000196035d2c _ZN2CA7Context18commit_transactionEPNS_11TransactionEdPd + 608 16 QuartzCore 0x0000000195e69520 _ZN2CA11Transaction6commitEv + 652 17 AppKit 0x0000000190fe116c __37+[NSDisplayCycle currentDisplayCycle]_block_invoke.7 + 44 18 CoreFoundation 0x000000018be34ad0 __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 28 19 CoreFoundation 0x000000018be34a10 __CFRunLoopDoBlocks + 396 20 CoreFoundation 0x000000018be33e54 __CFRunLoopRun + 2356 21 CoreFoundation 0x000000018bf06234 _CFRunLoopRunSpecificWithOptions + 532 22 HIToolbox 0x0000000198c1f560 RunCurrentEventLoopInMode + 320 23 HIToolbox 0x0000000198c228bc ReceiveNextEventCommon + 488 24 HIToolbox 0x0000000198dac14c _BlockUntilNextEventMatchingListInMode + 48 25 AppKit 0x00000001909163d0 _DPSBlockUntilNextEventMatchingListInMode + 228 26 AppKit 0x000000019026a084 _DPSNextEvent + 576 27 AppKit 0x0000000190dff96c -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688 28 AppKit 0x0000000190dff678 -[NSApplication(NSEventRouting) nextEventMatchingMask:untilDate:inMode:dequeue:] + 72 29 AppKit 0x000000019025d13c -[NSApplication run] + 368 30 AppKit 0x00000001902357b0 NSApplicationMain + 880 31 AppKit 0x000000019047c958 +[NSWindow _savedFrameFromString:] + 0 32 UIKitMacHelper 0x00000001aa2651bc UINSApplicationMain + 972 33 UIKitCore 0x00000001c4e1aed4 UIApplicationMain + 144 34 UIKitCore 0x00000001c548bda0 block_destroy_helper.31 + 8880 35 DigitalConcertHall.debug.dylib 0x0000000106e41bd8 $sSo21UIApplicationDelegateP5UIKitE4mainyyFZ + 128 36 DigitalConcertHall.debug.dylib 0x0000000106e41b4c $s18DigitalConcertHall11AppDelegateC5$mainyyFZ + 32 37 DigitalConcertHall.debug.dylib 0x0000000106e4afc0 __debug_main_executable_dylib_entry_point + 28 38 dyld 0x000000018b9ac4e4 start + 6992 ) I could not test with the iOS 27 beta 4 SDK due to this blocking issue: https://developer.apple.com/forums/thread/839012 However, when I tried to set up a simple sample project, I could not reproduce the issue. Does anybody know what might be causing this? I filed feedback FB24201508
Replies
8
Boosts
2
Views
2.1k
Activity
5d
Credential Provider Extension should allow BE=0, BS=0 for device-bound passkeys
In these threads, it was clarified that Credential Provider Extensions must set both Backup Eligible (BE) and Backup State (BS) flags to 1 in authenticator data: https://developer.apple.com/forums/thread/745605 https://developer.apple.com/forums/thread/787629 However, I'm developing a passkey manager that intentionally stores credentials only on the local device. My implementation uses: kSecAttrAccessibleWhenUnlockedThisDeviceOnly for keychain items kSecAttrTokenIDSecureEnclave for private keys No iCloud sync or backup These credentials are, by definition, single-device credentials. According to the WebAuthn specification, they should be represented with BE=0, BS=0. Currently, I'm forced to set BE=1, BS=1 to make the extension work, which misrepresents the actual backup status to relying parties. This is problematic because: Servers using BE/BS flags for security policies will incorrectly classify these as synced passkeys Users who specifically want device-bound credentials for higher security cannot get accurate flag representation Request: Please allow Credential Provider Extensions to return credentials with BE=0, BS=0 for legitimate device-bound passkey implementations. Environment: macOS 26.2 (25C56), Xcode 26.2 (17C52)
Replies
2
Boosts
5
Views
1.4k
Activity
5d
Battery chart time labels shifted hours ahead on macOS 27 (endOfDay wrong in BatteryUI.plist)
the "last 24 hours" battery level and screen on usage charts in system settings > battery have the hour labels shifted way ahead of real time. the bars are in the right order, the axis is just wrong. at 17:13 it was showing stuff up to like 23:00. at 10:05 a few days later it was about 12 hours ahead. the "last charged to 100%" time above the chart is correct tho. my clock and time zone are fine (asia/manila, set automatically, synced). the battery data itself is right too, i checked the power log and the plug in and unplug times match what actually happened. i dug into it and found the problem in `/private/var/db/powerlog/Library/BatteryLife/Debug/BatteryUI.plist`, which is what the battery pane gets from PerfPowerServices. `endOfDay` comes back as the next hour instead of midnight: PLBatteryUIQueryTime 2026-10-24 17:13:25 (local) endOfHour 2026-10-24 18:00:00 <- correct endOfDay 2026-10-24 18:00:00 <- should be 2026-10-25 00:00:00 so the chart puts 00:00 at 18:00 yesterday and everything ends up 6 hours off. it looks like the chart always labels its right edge as 24:00, so the further you are from midnight the worse it gets. restarting PerfPowerServices (`sudo killall PerfPowerServices`) doesn't fix it, the new process sends the same values right away. macos 27.0.1 (26A434). this was fine on macos 26. looks like the same bug as https://developer.apple.com/forums/thread/852392
Replies
0
Boosts
0
Views
136
Activity
5d
CloudKit sync fails in macOS TestFlight build – sandbox denies com.apple.cloudd
I have a macOS SwiftUI app using SwiftData with CloudKit synchronization. Bundle ID: com.mjsapps.PhrasePin CloudKit container: iCloud.com.mjsapps.PhrasePin CloudKit synchronization works when running the app from Xcode using the Development environment. However, synchronization does not work in the TestFlight / Production build. The Production schema has been deployed successfully. The TestFlight build has the expected entitlements, including: com.apple.developer.icloud-container-environment = Production com.apple.developer.icloud-container-identifiers = iCloud.com.mjsapps.PhrasePin com.apple.developer.icloud-services = CloudKit com.apple.security.app-sandbox = true com.apple.security.network.client = true The TestFlight build is signed as: Authority=TestFlight Beta Distribution Identifier=com.mjsapps.PhrasePin TeamIdentifier=8D6TX86CQK CloudKit/Core Data logging shows that the app is trying to use: container=iCloud.com.mjsapps.PhrasePin:Production but synchronization fails with: CKErrorDomain Code=6 Error connecting to CloudKit daemon NSCocoaErrorDomain Code=4099 The macOS sandbox log shows: Sandbox: PhrasePin(...) deny(1) mach-lookup com.apple.cloudd As a result, no com.apple.coredata.cloudkit.zone is created in the Production private database and no SwiftData records are synchronized. The problem has been reproduced on: macOS Sequoia 15.7.7 macOS Sequoia 15.7.9 The same app works with CloudKit in Development when run from Xcode. I have already submitted a Feedback Assistant report, but have not received a response. Has anyone seen this behavior with SwiftData + CloudKit in a sandboxed macOS TestFlight build? Is there an additional entitlement or provisioning requirement needed for access to com.apple.cloudd in Production?
Replies
1
Boosts
0
Views
67
Activity
5d
macos 27 - unexpected/new errno from BSD socket connect() when pending connections exceed backlog
Please consider the trivial C program attached to this thread. The code creates a socket() and listen()s for connections, but (intentionally) doesn't accept() the connections. The listen() is done using a small backlog (of 1). This test then does several connect() attempts and expects that the connect() attempts will accumulate in the pending queue and once the queue exceeds the backlog limit, then as specified in man listen: The backlog parameter defines the maximum length for the queue of pending connections. If a connection request arrives with the queue full, the client may receive an error with an indication of ECONNREFUSED. then the connect() attempt will receive a ECONNREFUSED. However, in macos 27, such a connect() attempt leads to ECONNRESET (Connection reset by peer) instead of ECONNREFUSED. Is this expected? Experiments show that prior versions of macos were returning a ETIMEDOUT for such connect() attempts. If this new error is expected from connect() when the backlog limit has exceeded, should it be specified in the man listen documentation? Rename the attached main.c.txt to main.c. Compiling the attached program on macos 27, using clang main.c and then running ./a.out results in: ----------------------- MacOS version: 27.0.1 Kernel version: Darwin Kernel Version 27.0.0: Tue Aug 11 21:02:16 PDT 2026; root:xnu-13432.1.9~1/RELEASE_ARM64_T8112 ----------------------- started server at at 127.0.0.1:52753 with a backlog of 1 connect() attempt 1 - connected connect() attempt 2 - connected connect() attempt 3 - connected connect() attempt 4 - connected connect() attempt 5 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 6 - connected connect() attempt 7 - connected connect() attempt 8 - connected connect() attempt 9 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 10 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 11 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 On a related note, it's unclear why several of the connect() attempts succeeded instead of just 1 of them succeeding. On prior versions of macos, the output of the same program is: ----------------------- MacOS version: 26.7.1 Kernel version: Darwin Kernel Version 25.6.0: Tue Aug 18 17:49:13 PDT 2026; root:xnu-12377.161.15.700.19~2/RELEASE_ARM64_T6000 ----------------------- started server at at 127.0.0.1:52451 with a backlog of 1 connect() attempt 1 - connected connect() attempt 2 - failed to connect() - Operation timed out connect() attempt 3 - failed to connect() - Operation timed out connect() attempt 4 - failed to connect() - Operation timed out connect() attempt 5 - failed to connect() - Operation timed out connect() attempt 6 - failed to connect() - Operation timed out connect() attempt 7 - failed to connect() - Operation timed out connect() attempt 8 - failed to connect() - Operation timed out connect() attempt 9 - failed to connect() - Operation timed out connect() attempt 10 - failed to connect() - Operation timed out connect() attempt 11 - failed to connect() - Operation timed out and this output is much more understandable and deterministic. main.c.txt
Replies
3
Boosts
0
Views
380
Activity
6d
Supported App Sandbox metadata access through an inherited file descriptor, without reopening the object
We are evaluating a macOS design before implementation. This is a platform-support question, not a report of an observed runtime failure. No actual controller executable, helper executable or deployment configuration has been selected or qualified. Our objective is to let a small, fixed-purpose helper examine an already-open object’s identity and access control list (ACL) metadata while preserving the original object reference and ownership. Proposed configuration A trusted controller would launch one native C helper using an explicit executable target and posix_spawn. The controller would need to qualify for the documented nonsandboxed-parent case, without a conflicting inherited sandbox. We do not assume that an absent entitlement alone establishes this. The helper would be the main executable of its own signed application bundle, using its own ordinary App Sandbox rather than inheriting the controller’s sandbox. Its proposed additional filesystem permission would be com.apple.security.temporary-exception.files.absolute-path.read-only, containing exactly two fixed directory entries beneath a user’s development workspace, outside the helper’s container. The literal private paths are omitted. The controller would already own a read-only file descriptor for one regular file or directory within those trees. It would retain its original reference and pass a known duplicate referring to the same open object to the helper. The helper would perform one metadata observation. The proposed operations are fstat for object identity and fgetattrlist requesting ATTR_CMN_RETURNED_ATTRS and ATTR_CMN_EXTENDED_SECURITY, with FSOPT_REPORT_FULLSIZE and without FSOPT_PACK_INVAL_ATTRS. Required boundaries The helper must use only the inherited descriptor for the subject observation. The design does not permit: Reopening or resolving the subject through a pathname, bookmark or URL. Substituting a copied file or another object reference. Reading file contents, enumerating directories, changing permissions, or modifying shared descriptor flags or file offsets. Expanding the exception to an ancestor, home directory or broader workspace. Disabling an existing sandbox or using private interfaces to bypass restrictions. Parent-side traversal and identity checks remain separate responsibilities. Strict ancestor directories are not additional helper ACL subjects. We understand that a read-only directory exception and ordinary sandbox/container capabilities may permit more than the helper’s intended metadata operations. Metadata-only behaviour would be a reviewed-code obligation; we are not asking App Sandbox to enforce an exact metadata-only operation filter. Questions Supported launch and activation: Under what documented parent-context, signing, bundle, container and launch conditions can this helper establish its own ordinary App Sandbox? What supported mechanism or guarantee establishes that the sandbox is effective before the subject metadata operation? Required metadata permissions: Does the proposed read-only exception support fstat and the specified extended-security fgetattrlist request through an inherited read-only descriptor, for both regular files and directories? Please distinguish descriptor survival from permission to perform these operations, including any additional access-control conditions. Scope, identity and lifetime: What documented behaviour applies to descendant coverage, aliases, hard links, renames or namespace changes after the descriptor was opened? Please distinguish the lifetime of the inherited object reference from the lifetime of the static directory permission. Our design would refuse uncertainty rather than reopen, rebind or widen access. Evidence and support boundary: Which public documentation, interfaces or authoritative guarantees support this exact composition, and which parts require separate empirical qualification? Please identify applicable macOS versions and restrictions. Distinguish platform support from any distribution or App Store review requirements. If these requirements cannot be combined through supported interfaces, please identify the incompatible requirement. An approach requiring broader access, pathname reopening, a replacement object or a different handoff architecture would be a design change requiring separate review, not a solution within the stated constraints. Permission failures, unsupported requests and incomplete metadata would remain unavailable results. They would not be interpreted as proof that an ACL is absent. Complete ACL-absence interpretation and native resource bounds remain separate qualification questions. Apple material already reviewed Resolving App Sandbox Inheritance Problems App Sandbox Temporary Exception Entitlements Accessing files from the macOS App Sandbox
Replies
1
Boosts
0
Views
246
Activity
6d
Control fan speed on MacPro 3.1 (early 2008)
I have a MacPro 3.1 (early 2008) that has Linux installed on it (Debian 13). One of the fans runs at top speed of 2500 rpm because some sensor in the board can't report the temperature to the OS. The Motherboard model is Mac-F42C88C8. Searched the internet to see if I could find any information on how to identify the sensor or the SMC information about it. I would like to know if there is any information that anyone knows about this and where could I start trying to make a driver to control the fan by getting the value in the sensor. I can see in the program coolercontrol in Linux the Fan that is at high speed is named 'IO' Thanks Regards
Replies
0
Boosts
0
Views
97
Activity
1w
Sandboxed app can't delete AppleDouble (._) files of quarantined files on exFAT, even with user-selected access.
My Mac App Store utility removes Mac metadata files (._* AppleDouble files and .DS_Store) from external drives formatted exFAT or FAT32. The app is sandboxed with com.apple.security.files.user-selected.read-write and com.apple.security.files.bookmarks.app-scope. The user grants access to the volume through NSOpenPanel. Deleting a ._ file works, except when its companion file carries com.apple.quarantine (for example, a file downloaded with Safari and copied to the drive with Finder). Then: let partner = volume + "/Nirvana.zip" // has com.apple.quarantine let appleDouble = volume + "/._Nirvana.zip" removexattr(partner, "com.apple.quarantine", XATTR_NOFOLLOW) // -1, errno 1 (EPERM) unlink(appleDouble) // -1, errno 1 (EPERM)The same unlink succeeds from Terminal (not sandboxed, without Full Disk Access). On exFAT the extended attributes live in the ._ file, so I assume the sandbox refuses because deleting it would remove the quarantine attribute. Tried, with no change: Full Disk Access granted to the app. Adding com.apple.security.files.user-selected.executable (verified in the built app with codesign -d --entitlements -). On a real drive (a music library), about 71% of the ._ files belong to quarantined files, so this is most of what users want removed. Is there a supported way for a sandboxed app to remove these files: an entitlement, an API, or an explicit user action? If not, can you confirm it's intended behavior, so I can explain it accurately to users? macOS 27.2, Xcode 27.2, Apple silicon. Focused sample project available (one source file). DTS case 23240704.
Replies
5
Boosts
0
Views
174
Activity
1w
Verifying a stored file-based Keychain trusted-application requirement
I'm evaluating a macOS file-based Keychain ACL that should authorize one application identity, defined by an intended code-signing requirement. The application is a shared Python interpreter; I understand that trusting it does not restrict access to an individual script. I read the related Apple Developer Forums discussion, which explains that complete ACL introspection is not supported and that the stored trusted-application code-signing requirement is accessible through SPI rather than public API. My narrower question is whether there is a supported verification operation that does not require exposing that requirement: Given a SecTrustedApplicationRef obtained through SecACLCopyContents, can a public API establish that its stored caller-matching requirement is no broader than the intended application requirement? Confirming that the intended application is accepted would establish only that it matches, not that additional application identities are excluded. I also don't want to assume that CFEqual against a newly created reference, matching paths, or matching SecTrustedApplicationCopyData results proves equivalent authorization. Apple's documentation describes the CopyData result as opaque. If this comparison is unsupported, what documented provisioning or operating-system enforcement guarantees should an application rely on instead? Is controlled provisioning the intended boundary, or is a different supported Keychain design appropriate? Most importantly, if verifying the exact trusted-application restriction isn't supported, what is Apple's recommended secure approach for allowing a local Python trading application to retrieve Keychain credentials without granting access to every script using the same Python interpreter? A fake-only example using a disposable test Keychain and synthetic generic-password item has been prepared but has not been built or run because full Xcode was unavailable. This is an API-contract question; no runtime failure or ACL attack is claimed, and no assumption is made that published source exactly matches the installed framework.
Replies
1
Boosts
0
Views
90
Activity
1w
Is NavigationSplitView on macOS 27 broken?
On macOS 27 Beta 2, a simple NavigationSplitView example exhibits bizarre behaviour when the window is resized. The sidebar seemingly expands and collapses at random as the window is resized. The symptoms can be exacerbated with toolbar items. The sidebar appears to behave correctly when an inspector view is not present. Copy paste the code below into a new Xcode 27 project and run on macOS 27 and then resize the window: File -> New -> Project... -> App import SwiftUI @main struct MyApp: App { var body: some Scene { WindowGroup { ContentView() } } } struct ContentView: View { var body: some View { NavigationSplitView { Text("Sidebar") } detail: { Text("Content") } .inspector(isPresented: .constant(true)) { Text("Inspector") } } } Adding .frame or .inspectorColumnWidth to any of the Text views does not appear to fix the issues. macOS: 27.0 Beta (26A5368g) Xcode: 27.0 beta 2 (27A5209h)
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
6
Boosts
1
Views
771
Activity
1w