Explore the core architecture of the operating system, including the kernel, memory management, and process scheduling.

Posts under Core OS subtopic

Post

Replies

Boosts

Views

Activity

Core OS Resources
General: DevForums subtopic: App & System Services > Core OS Core OS is a catch-all subtopic for low-level APIs that don’t fall into one of these more specific areas: Processes & Concurrency Resources Files and Storage Resources Networking Resources Network Extension Resources Security Resources Virtualization Resources Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com"
0
0
2.2k
Aug ’25
Virtualization.framework — stop completion and storage release
Hello Apple Developer Support, We are evaluating a macOS VM controller using VZVirtualMachine and would appreciate clarification: Does stop(completionHandler:) have any documented maximum completion time? What should a controller do if completion never arrives? After successful completion, are all backend writes finished and disk-image resources released, or is additional teardown required? What documented sequence establishes that the VM’s complete writable storage set—including disk images and macOS auxiliary storage—can safely be deleted, replaced or restored? Do these guarantees depend on caching/synchronization mode or macOS version? We understand that forced stop does not guarantee a clean guest shutdown or application consistency. Our question concerns host-side storage quiescence and resource release. Documentation references would be helpful. Thank you.
0
0
88
18h
Updating an FSKit module to use the new Handler protocols
I have a file system extension that currently uses the various now-deprecated Operations protocols. I have a few questions about moving to the new Handler protocols. First, my module is going to maintain backwards compatibility with macOS Sequoia for the foreseeable future, but I would also like to be able to take advantage of new FSKit features for users who are on newer OS versions. What approach would you recommend: Having an FSVolume conform to both the various Operations and Handler protocols (e.g. both FSVolumeKernelOffloadedIOOperations and FSVolume.KernelOffloadedIOHandler with the latter tagged with @available) an immediate issue I see trying to do this is I run into the error Method 'activate(options:)' with Objective-C selector 'activateWithOptions:replyHandler:' conflicts with previous declaration with the same Objective-C selector when trying to conform to both FSVolume.Handler and FSVolume.Operations. Having two separate FSVolume implementations, one used for older OS versions with Operations support and one used on newer OS versions with Handler support? Keeping the use of pre-existing Operations protocols while only using the Handlers for newer features (e.g. things like SeekRegionHandler) Second, I see at https://developer.apple.com/documentation/fskit/fsvolumehandlerresult/requestedattributes that I must populate all requested attributes. Does this value only have a meaning if the initializer for the actual concrete result type has an initializer that takes in a FSItem.Attributes instance, or is there some way I’m supposed to populate those? (As a concrete example, FSCheckAccessResult has init(accessAllowed:) which doesn’t take in any attributes.)
6
0
966
1d
"IOSurface creation failed" drawing to CGContext
(more details on StackOverflow) I'm getting messages like the following, SOMETIMES, when I draw to a CGContext IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5207703552; IOSurfaceAllocSize = 9461418; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } call to context.draw(): context.draw(photo.image, in: CGRect(x: 0, y: top, width: width, height: height), byTiling: false) The results are just fine, so the draw seems to be working. It also, most often, draws without producing this error, but it fails pretty often. I'm not sure where to begin looking to sort out what I might need to do differently to avoid this error message in the console. Complete code: import Foundation import SwiftUI func generateSpritesImage(thumbPhotos: [Photo], width: Int, filename: URL) -> [Int] { var indices = [Int]() let totalHeight = thumbPhotos.reduce(0) { $0 + $1.heightOfImage(ofWidth: width) } debugPrint("creating context") let context = CGContext(data: nil, width: width, height: totalHeight, bitsPerComponent: 8, bytesPerRow: 0, space: CGColorSpace(name: CGColorSpace.sRGB)!, bitmapInfo: CGImageAlphaInfo.noneSkipLast.rawValue)! var top = totalHeight for photo in thumbPhotos { let height = photo.heightOfImage(ofWidth: width) indices.append(top - totalHeight) top -= height debugPrint("drawing \(photo.filteredFileURL())") context.draw(photo.image, in: CGRect(x: 0, y: top, width: width, height: height), byTiling: false) } debugPrint("write jpeg") writeJpegFromContext(context: context, filename: filename) return indices } func writeJpegFromContext(context: CGContext, filename: URL) { let cgImage = context.makeImage()! let bitmapRep = NSBitmapImageRep(cgImage: cgImage) let jpegData = bitmapRep.representation(using: NSBitmapImageRep.FileType.jpeg, properties: [:])! try! jpegData.write(to: filename) } sample of output: "drawing 0002-_MG_8542.jpg" "drawing 0003-_MG_8545.jpg" "drawing 0004-_MG_8550.jpg" IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5211357184; IOSurfaceAllocSize = 9983331; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } "drawing 0005-_MG_8555.jpg" IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5221351424; IOSurfaceAllocSize = 10041215; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } "drawing 0006-_MG_8562.jpg" "drawing 0007-_MG_8563.jpg" IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5376163840; IOSurfaceAllocSize = 10109756; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } "drawing 0008-_MG_8584.jpg" "drawing 0009-_MG_8618.jpg" IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5394612224; IOSurfaceAllocSize = 8425564; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } "drawing 0010-_MG_8627.jpg" "drawing 0011-_MG_8649.jpg" "drawing 0012-_MG_8658.jpg" "drawing 0013-_MG_8665.jpg" "drawing 0014-_MG_8677.jpg" "drawing 0015-_MG_8675.jpg" "drawing 0016-_MG_8676.jpg" "drawing 0017-IMGP0873.jpg" "drawing 0018-_MG_8719.jpg" "drawing 0019-_MG_8743.jpg" ...
4
1
2.8k
1d
macOS: pre-established stop mechanism when a VM supervisor stops progressing
I am evaluating a bounded workload host using Virtualization.framework on Apple silicon. This is a question about supported architecture and API contracts, not a report of a reproduced bug. No particular macOS release has yet been qualified for this design; please identify the releases and prerequisites to which an answer applies. I have read the discussions about cleanup after the VM-owning application terminates: https://developer.apple.com/forums/thread/848542 https://developer.apple.com/forums/thread/850709 I understand that this cleanup is different from an externally observable, time-bounded teardown guarantee. I am not asking again for a replacement application's handle to a VM whose owner has already died. The unresolved case is different: A host application owns a VM, but its serial VM-control queue is no longer progressing. A separate supervisor is intended to initiate the fallback stop action against that application. An external stop trigger occurs. The supervisor is then lost or stops progressing before it enters the signal operation; the VM-owning application remains alive. Loss of the supervisor role does not necessarily mean that its process has exited, so a process-exit notification cannot be assumed. Complete host or kernel failure is not part of this scenario. Is there a supported public mechanism that can be established before workload preparation and retain authority to act on the same target application after this loss, without requiring another action by the supervisor or progress on the VM-control queue? For any such mechanism, I would particularly appreciate clarification of: How its authority is bound to the intended target during incomplete setup, including process creation that has begun but has not returned a usable target identity. Assuming an already-running watchdog leaves this setup boundary unanswered. Which actor performs the remaining action when the supervisor cannot, and what lifecycle, privilege and progress assumptions that actor requires. Whether any documented progress bound applies when a required operation does not return. The design requirement is completion of the whole prescribed stop/escalation attempt, including required failure-handling steps, within 10 seconds of the same first external trigger. Starting a timer or entering a signal call is not equivalent to completing that attempt. This is not a request for unconditional successful process or VM termination. A supported narrower mechanism, or an explicit statement that macOS provides no such contract for this case, would also be useful. I am looking for public interfaces and their documented limits, not private helper-process identities or kernel implementation details. Thank you.
8
0
123
1d
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
64
1d
macOS 27: supported ACL absence and enumeration semantics
I am designing a fail-closed filesystem ACL verifier and would appreciate clarification of the supported public API contract. The observed environment is macOS 27.0, build 26A428, on Apple silicon. Disk Utility identifies the Data volume mounted at /System/Volumes/Data as APFS (Encrypted). Finder shows Xcode 27.2, and Xcode displays a built-in macOS 27.2 component. The exact SDK build and the SDK to be used for validation remain unconfirmed. I am considering acl_get_fd_np with ACL_TYPE_EXTENDED and acl_get_entry. Could someone clarify: How can a caller distinguish an absent ACL, a valid zero-entry ACL, and failed or unavailable ACL retrieval on an existing object? Under what documented conditions, if any, does a NULL result with ENOENT establish that an ACL is absent? How can a caller recognise valid enumeration completion without confusing it with invalid ACL state or another EINVAL failure? Is there a supported descriptor-bound public API or documented sequence for making these distinctions? How should omitted security attributes and truncated attribute buffers be interpreted? Which of these guarantees depend on the macOS build, SDK version, or filesystem? What guarantees apply to object identity and concurrent changes between reading ACL evidence and a later operation? I intend to classify ambiguous evidence as indeterminate and do not intend to modify ACLs on assessed objects. Thank you.
0
0
47
1d
Which macOS version first exports Logger.isEnabled(type:)?
An app built with Xcode 27.1 for a macOS 15 deployment target called Logger.isEnabled(type:). In the SDK's swiftinterface the method sits under Logger's @available(macOS 11.0, ...) with no availability of its own, so it compiled without a warning. On macOS 15.6.1, libswiftos.dylib doesn't export it, and dyld stopped the app at launch: Symbol not found: _$s2os6LoggerV9isEnabled4typeSbSo0a5_log_E2_ta_tF Expected in: /usr/lib/swift/libswiftos.dylibThe macOS 15.5 SDK's libswiftos.tbd doesn't list the symbol and the 27 SDK does. I haven't checked macOS 26. Switching to OSLog.isEnabled(type:) fixed it. Which macOS version first exports this symbol? Write-up: https://yardlet.app/blog/logger-isenabled-macos-15.html
4
0
113
2d
Which memory entitlements can an independent iOS developer use?
I'm researching the memory limits and capabilities available to ordinary third-party iOS applications. My project, Kairavox, is a native iOS application whose initial CPU design uses a software AArch64 interpreter. Its long-term goal is to run a genuine, unmodified iPadOS installation as a guest. Before making further architectural decisions, I want to understand what memory capabilities are actually available to independent developers. Our initial guest research target is an iPad 9th generation running iPadOS 27.2.1. The host iPhone model has not yet been fixed. I've found Apple's documentation for: Increased Memory Limit, with the key com.apple.developer.kernel.increased-memory-limit. Extended Virtual Addressing, with the key com.apple.developer.kernel.extended-virtual-addressing. Increased Debugging Memory Limit, which Apple describes as providing additional memory during development and internal testing. I'd appreciate clarification on the following for current iOS versions: Which iPhone models and iOS versions support each of these capabilities? Is there a public compatibility list? Can an independent developer request the Increased Memory Limit entitlement? If so, what is the current request and provisioning-profile process? Does Extended Virtual Addressing increase only address-space capacity, or can it also raise an app's physical-memory limit? What is the exact entitlement key for Increased Debugging Memory Limit, and what are its limits for development, ad hoc, and internal TestFlight builds? Are any of these capabilities available with free Personal Team signing? Does paid Apple Developer Program membership change eligibility, or is separate authorization required? If granted, may an app use additional available memory as backing for software-emulated guest RAM? Are there documented limits or workload restrictions? I understand that an entitlement would not reserve physical RAM or prevent memory pressure and termination. Apple's current iOS supported-capabilities table lists Extended Virtual Addressing and Increased Debugging Memory Limit, but I could not find Increased Memory Limit there. Is that table complete for this capability, or does availability depend on the device, account, or another process? I'm not assuming these entitlements are available to every developer. Documentation or specific eligibility guidance would be very helpful. Thank you.
1
0
49
2d
Is JIT execution possible for ordinary third-party iOS apps?
I'm researching whether a normally signed third-party iOS application can use Just-In-Time (JIT) compilation on a stock, unjailbroken iPhone. My project, Kairavox, aims to run a genuine, unmodified iPadOS installation as a guest inside a native iOS application. JIT compilation is central to our intended execution architecture: we want to translate and execute guest AArch64 instructions through dynamically generated native code. We intend to test through personal development signing and sideloading using AltStore or SideStore. App Store distribution is not a requirement. I've found Apple's documentation for: Allow Execution of Just-In-Time (JIT) Compiled Code Entitlement Porting Just-In-Time Compilers to Apple Silicon Alternative Browser Engines in the European Union However, the first two appear to concern the macOS Hardened Runtime context. Apple's alternative browser engine provisions also describe a specifically authorized exception, which does not describe our application. I'd appreciate clarification on what is supported for an ordinary third-party iOS app: Is there a documented iOS API or entitlement that allows a normally signed third-party app to allocate writable memory, generate machine code, and execute that code at runtime? Does iOS support MAP_JIT for ordinary third-party applications, or is it restricted to other Apple platforms or specially authorized applications? Is com.apple.security.cs.allow-jit exclusively a macOS Hardened Runtime entitlement, or does it have any application on iOS? Can an app using free Personal Team development signing execute JIT-generated code? Does paid Apple Developer Program membership change this? Do development, ad hoc, or other signing arrangements differ in their JIT permissions? Is there a documented process for an independent developer to request the necessary capability? Does installing an app through AltStore or SideStore change its OS-granted executable-memory permissions, or does it retain the permissions associated with its signed build? Are there any documented restrictions on using JIT-generated native code for CPU emulation or virtualization workloads? I understand that Apple's EU alternative-browser-engine authorization is a narrow exception for eligible browser applications. I'm not assuming it applies to Kairavox. The main question is whether an independent developer can build and test a JIT-based application on a stock iPhone using an officially supported signing and permission model. Thank you.
1
0
51
2d
Improve PTT System UI Visibility When Location Indicators Are Active
Observed Limitation When location services are active, the iOS location indicator may overlap with or hide the PTT blue button or system UI in the notch / Dynamic Island area. Requested Changes Ensure PTT controls remain visible and accessible when location indicators are displayed. Improve system UI positioning to prevent conflicts with other system indicators.
1
0
35
2d
Support Multiple PTT Applications on the Same iOS Device
Observed Limitation The PTT framework appears to restrict active usage to one PTT application per device. When another application is already registered or connected to a PTT channel, a second application may be unable to use the PTT service. Requested Changes Allow multiple PTT applications to coexist on the same device. Support independent registration and channel management for each application. Provide system-level coordination of PTT resources between applications.
1
0
31
2d
Can a restore replace a file in an App Group container while the app's process is alive?
For an iOS app that stores a SQLite database in its App Group container and has no extension targets, can iCloud restore, Finder or Apple Devices restore, or Quick Start replace a file in that container while the app's normal process remains alive, including while suspended? If iOS terminates the process first, can the app relaunch before all App Group files have finished restoring? Please identify any differences between these restore paths and any documented guarantee. Related: thread 845479 gave the general rule for the app's own container.
3
0
127
2d
Supported non-admin service identity for a macOS LaunchDaemon
I'm developing a private macOS application on an Apple-silicon Mac mini running macOS Golden Gate 27.2. I'm evaluating a system LaunchDaemon running under a dedicated, non-administrator identity that cannot log in interactively. A separate desktop application would communicate with the daemon through authenticated local IPC. Before implementing this architecture, I would like to establish the officially supported approach. My main question: What is the Apple-supported method for creating and maintaining a dedicated, non-administrator, non-interactive service identity for a system LaunchDaemon on macOS 27.2? In particular: Is there a documented procedure for creating, restricting, disabling, recovering and eventually removing this identity? Are dscl, sysadminctl or another account-management mechanism supported for this purpose? Can a LaunchDaemon run under this identity without an interactive user login, including when registered through SMAppService? Are there any secure-token, FileVault, volume-ownership or keychain restrictions that would affect this design? If a dedicated non-login service identity is not a supported architecture, what alternative does Apple recommend? I'd particularly appreciate links to official Apple documentation or guidance from Apple engineers. Thank you.
10
0
579
3d
Full Disk Access on macOS 27.3
I'm looking into the changes being implemented and I find this way of handling by Apple on short notice problematic. Now our customers (those that don't have MDM) will have to jump through hoops to enable FDA for our product, a security product that also uses Endpoint Security. We already have the entitlement for endpoint security, which requires FDA in order to work, so why make it so difficult instead of just allowing FDA for apps that have this entitlement? Why only backup applications are exempted?
2
0
130
3d
Access to related files outside Sandbox with NSFileCoordinator and NSFilePresenter does not work anymore in macOS 27.3 beta 2
In macOS 27.3 beta 2, it is no longer possible to use NSFileCoordinator with NSFilePresenter instances to open a SQLite file with related WAL and SHM files when a sandboxed app has access to the primary SQLite file. In macOS 27.3 beta 1 and previous macOS releases, the Related File Access API works as expected. This happens regardless where the files are located, so it seems to be unrelated to recent changes in Privacy & Security, although it could be an unexpected side effect of these changes. Instead of correctly registering NSFilePresenter instances, errors like the following are logged in the XCode console: NSFileSandboxingRequestRelatedItemExtension: Failed to issue extension for /Users/testuser/Desktop/Sample/Example.sqlite-wal because: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" (The related item is protected by a different storage class than the primary item) UserInfo={NSDebugDescription=The related item is protected by a different storage class than the primary item} +[NSFileCoordinator addFilePresenter:] could not get a sandbox extension. primaryPresentedItemURL: file:///Users/testuser/Desktop/Sample/Example.sqlite, presentedItemURL: file:///Users/testuser/Desktop/Sample/Example.sqlite-walThe mentioned Related File Access API is documented here. I have filed a Feedback, which includes a sample project: FB25625743 My question is: Is this a bug, or new intended behavior, or is there something else changed that should be dealed with when using this API in macOS 27.3 beta 2?
1
0
73
3d
Can macOS verify a worker’s effective sandbox policy before it runs?
I’m building a local app on an Apple silicon Mac. Before a worker or any of its child processes can run, I need to verify the worker’s effective filesystem and network restrictions, including inherited restrictions. I need to allow that same pending launch only if the policy matches, and deny it if verification fails or times out. I reviewed Apple’s App Sandbox guidance and the Endpoint Security documentation for exec authorization and entitlement metadata. I haven’t found documentation showing that these expose the complete effective policy for the pending launch. Is there a supported public macOS API that provides this guarantee? If so, which API and macOS versions support it? If not, is this outside what the public APIs can verify?
1
0
201
3d
Subject: Critical APFS Data Loss Bug & Error 1110 Loop during official Finder Update on iPhone 14 (A15)
Hello, I am requesting an engineering escalation regarding a critical bug in Apple's APFS update pipeline that trapped an iPhone 14 (A15, 128 GB) in recovery mode during an official Finder update from iOS 16.6 to iOS 18 (27.2.1, 24B156) on macOS 14.5. The device hardware is 100% healthy (Apple MRI diagnostics all green), the passcode is known, and 101,175 MB (341,967 files) of user data remain intact on the flash storage. However, the device cannot boot or complete an update due to a corruption caused by Apple's own restore tools. --- ### What Happened (Verified in Logs): 1. **Initial Full Storage State:** The device had ~105 GB utilized and was updated via Finder using "Update" (not Restore). 2. **Destructive fsck Behavior:** In pass 3, the restore ramdisk ran `/sbin/fsck_apfs -dy /dev/disk2`. On the nearly full container, fsck erroneously flagged 8,182 live omap mappings as "orphans" and deallocated them, causing extent-ref b-tree node `0x10bb3` to be zeroed out (TRIMmed by the flash controller). 3. **Split Failure:** In pass 4, the iOS 18 System volume installed and sealed, but `split_data_volume` failed in 4 seconds when `apfs_migrator` encountered block `0x10bb3` (`obj_read` checksum failure returning EILSEQ / error 92). 4. **False Error 1110 Loop:** Every subsequent attempt now halts immediately at `space_checks` with Error 1110. --- ### Reverse Engineering Proof: Disassembly of `restored_update` (arm64e, VA 0x10001afcc / 0x10001b0e8) confirms a major error-handling bug: When `splitter_dump` encounters the unreadable block `0x10bb3`, it fails with `EILSEQ` (92). Instead of handling this error, `restored_update` executes: `mov x19, #-1; mov x0, x19; ret` The caller receives `-1 bytes of free space`, logs: "Data volume requires splitting. Splitter will leave -1 bytes of free space after completion. Current free space on device: 6620069888 bytes. Insufficient space on device to run splitter" and aborts with **CHECKPOINT FAILURE:(FAILURE:1110)**. The device is NOT out of space (it has 6.3 GB free); it is blocked solely because `restored_update` misinterprets an EILSEQ filesystem error as negative free space. --- ### Current State & Request: - The encryption keys and SEP/gigalocker are intact (`gigalocker: ONLINE`). - In the restore ramdisk, `/dev/disk2s2` mounts cleanly as read-write on `/mnt2`. - Zero APFS snapshots remain on the volume, meaning the extent-ref tree is theoretically fully reconstructible from the valid fsroot inode tree. I am requesting assistance from CoreOS / APFS engineering: 1. Is there an engineering update ramdisk or build that can bypass the `splitter_dump` EILSEQ check, or rebuild the extent-ref tree, so the update can finalize? 2. Alternatively, can an engineering liaison facilitate a non-destructive extraction given that the volume mounts read-write and the user passcode is known? I can immediately provide full terminal transcripts, Finder updater logs (`iPhoneUpdater-*.log`), and disassembly details. Thank you, Samuel Journo
1
0
106
3d
Core OS Resources
General: DevForums subtopic: App & System Services > Core OS Core OS is a catch-all subtopic for low-level APIs that don’t fall into one of these more specific areas: Processes & Concurrency Resources Files and Storage Resources Networking Resources Network Extension Resources Security Resources Virtualization Resources Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com"
Replies
0
Boosts
0
Views
2.2k
Activity
Aug ’25
Virtualization.framework — stop completion and storage release
Hello Apple Developer Support, We are evaluating a macOS VM controller using VZVirtualMachine and would appreciate clarification: Does stop(completionHandler:) have any documented maximum completion time? What should a controller do if completion never arrives? After successful completion, are all backend writes finished and disk-image resources released, or is additional teardown required? What documented sequence establishes that the VM’s complete writable storage set—including disk images and macOS auxiliary storage—can safely be deleted, replaced or restored? Do these guarantees depend on caching/synchronization mode or macOS version? We understand that forced stop does not guarantee a clean guest shutdown or application consistency. Our question concerns host-side storage quiescence and resource release. Documentation references would be helpful. Thank you.
Replies
0
Boosts
0
Views
88
Activity
18h
Updating an FSKit module to use the new Handler protocols
I have a file system extension that currently uses the various now-deprecated Operations protocols. I have a few questions about moving to the new Handler protocols. First, my module is going to maintain backwards compatibility with macOS Sequoia for the foreseeable future, but I would also like to be able to take advantage of new FSKit features for users who are on newer OS versions. What approach would you recommend: Having an FSVolume conform to both the various Operations and Handler protocols (e.g. both FSVolumeKernelOffloadedIOOperations and FSVolume.KernelOffloadedIOHandler with the latter tagged with @available) an immediate issue I see trying to do this is I run into the error Method 'activate(options:)' with Objective-C selector 'activateWithOptions:replyHandler:' conflicts with previous declaration with the same Objective-C selector when trying to conform to both FSVolume.Handler and FSVolume.Operations. Having two separate FSVolume implementations, one used for older OS versions with Operations support and one used on newer OS versions with Handler support? Keeping the use of pre-existing Operations protocols while only using the Handlers for newer features (e.g. things like SeekRegionHandler) Second, I see at https://developer.apple.com/documentation/fskit/fsvolumehandlerresult/requestedattributes that I must populate all requested attributes. Does this value only have a meaning if the initializer for the actual concrete result type has an initializer that takes in a FSItem.Attributes instance, or is there some way I’m supposed to populate those? (As a concrete example, FSCheckAccessResult has init(accessAllowed:) which doesn’t take in any attributes.)
Replies
6
Boosts
0
Views
966
Activity
1d
"IOSurface creation failed" drawing to CGContext
(more details on StackOverflow) I'm getting messages like the following, SOMETIMES, when I draw to a CGContext IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5207703552; IOSurfaceAllocSize = 9461418; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } call to context.draw(): context.draw(photo.image, in: CGRect(x: 0, y: top, width: width, height: height), byTiling: false) The results are just fine, so the draw seems to be working. It also, most often, draws without producing this error, but it fails pretty often. I'm not sure where to begin looking to sort out what I might need to do differently to avoid this error message in the console. Complete code: import Foundation import SwiftUI func generateSpritesImage(thumbPhotos: [Photo], width: Int, filename: URL) -> [Int] { var indices = [Int]() let totalHeight = thumbPhotos.reduce(0) { $0 + $1.heightOfImage(ofWidth: width) } debugPrint("creating context") let context = CGContext(data: nil, width: width, height: totalHeight, bitsPerComponent: 8, bytesPerRow: 0, space: CGColorSpace(name: CGColorSpace.sRGB)!, bitmapInfo: CGImageAlphaInfo.noneSkipLast.rawValue)! var top = totalHeight for photo in thumbPhotos { let height = photo.heightOfImage(ofWidth: width) indices.append(top - totalHeight) top -= height debugPrint("drawing \(photo.filteredFileURL())") context.draw(photo.image, in: CGRect(x: 0, y: top, width: width, height: height), byTiling: false) } debugPrint("write jpeg") writeJpegFromContext(context: context, filename: filename) return indices } func writeJpegFromContext(context: CGContext, filename: URL) { let cgImage = context.makeImage()! let bitmapRep = NSBitmapImageRep(cgImage: cgImage) let jpegData = bitmapRep.representation(using: NSBitmapImageRep.FileType.jpeg, properties: [:])! try! jpegData.write(to: filename) } sample of output: "drawing 0002-_MG_8542.jpg" "drawing 0003-_MG_8545.jpg" "drawing 0004-_MG_8550.jpg" IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5211357184; IOSurfaceAllocSize = 9983331; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } "drawing 0005-_MG_8555.jpg" IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5221351424; IOSurfaceAllocSize = 10041215; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } "drawing 0006-_MG_8562.jpg" "drawing 0007-_MG_8563.jpg" IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5376163840; IOSurfaceAllocSize = 10109756; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } "drawing 0008-_MG_8584.jpg" "drawing 0009-_MG_8618.jpg" IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5394612224; IOSurfaceAllocSize = 8425564; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } "drawing 0010-_MG_8627.jpg" "drawing 0011-_MG_8649.jpg" "drawing 0012-_MG_8658.jpg" "drawing 0013-_MG_8665.jpg" "drawing 0014-_MG_8677.jpg" "drawing 0015-_MG_8675.jpg" "drawing 0016-_MG_8676.jpg" "drawing 0017-IMGP0873.jpg" "drawing 0018-_MG_8719.jpg" "drawing 0019-_MG_8743.jpg" ...
Replies
4
Boosts
1
Views
2.8k
Activity
1d
macOS: pre-established stop mechanism when a VM supervisor stops progressing
I am evaluating a bounded workload host using Virtualization.framework on Apple silicon. This is a question about supported architecture and API contracts, not a report of a reproduced bug. No particular macOS release has yet been qualified for this design; please identify the releases and prerequisites to which an answer applies. I have read the discussions about cleanup after the VM-owning application terminates: https://developer.apple.com/forums/thread/848542 https://developer.apple.com/forums/thread/850709 I understand that this cleanup is different from an externally observable, time-bounded teardown guarantee. I am not asking again for a replacement application's handle to a VM whose owner has already died. The unresolved case is different: A host application owns a VM, but its serial VM-control queue is no longer progressing. A separate supervisor is intended to initiate the fallback stop action against that application. An external stop trigger occurs. The supervisor is then lost or stops progressing before it enters the signal operation; the VM-owning application remains alive. Loss of the supervisor role does not necessarily mean that its process has exited, so a process-exit notification cannot be assumed. Complete host or kernel failure is not part of this scenario. Is there a supported public mechanism that can be established before workload preparation and retain authority to act on the same target application after this loss, without requiring another action by the supervisor or progress on the VM-control queue? For any such mechanism, I would particularly appreciate clarification of: How its authority is bound to the intended target during incomplete setup, including process creation that has begun but has not returned a usable target identity. Assuming an already-running watchdog leaves this setup boundary unanswered. Which actor performs the remaining action when the supervisor cannot, and what lifecycle, privilege and progress assumptions that actor requires. Whether any documented progress bound applies when a required operation does not return. The design requirement is completion of the whole prescribed stop/escalation attempt, including required failure-handling steps, within 10 seconds of the same first external trigger. Starting a timer or entering a signal call is not equivalent to completing that attempt. This is not a request for unconditional successful process or VM termination. A supported narrower mechanism, or an explicit statement that macOS provides no such contract for this case, would also be useful. I am looking for public interfaces and their documented limits, not private helper-process identities or kernel implementation details. Thank you.
Replies
8
Boosts
0
Views
123
Activity
1d
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
64
Activity
1d
macOS 27: supported ACL absence and enumeration semantics
I am designing a fail-closed filesystem ACL verifier and would appreciate clarification of the supported public API contract. The observed environment is macOS 27.0, build 26A428, on Apple silicon. Disk Utility identifies the Data volume mounted at /System/Volumes/Data as APFS (Encrypted). Finder shows Xcode 27.2, and Xcode displays a built-in macOS 27.2 component. The exact SDK build and the SDK to be used for validation remain unconfirmed. I am considering acl_get_fd_np with ACL_TYPE_EXTENDED and acl_get_entry. Could someone clarify: How can a caller distinguish an absent ACL, a valid zero-entry ACL, and failed or unavailable ACL retrieval on an existing object? Under what documented conditions, if any, does a NULL result with ENOENT establish that an ACL is absent? How can a caller recognise valid enumeration completion without confusing it with invalid ACL state or another EINVAL failure? Is there a supported descriptor-bound public API or documented sequence for making these distinctions? How should omitted security attributes and truncated attribute buffers be interpreted? Which of these guarantees depend on the macOS build, SDK version, or filesystem? What guarantees apply to object identity and concurrent changes between reading ACL evidence and a later operation? I intend to classify ambiguous evidence as indeterminate and do not intend to modify ACLs on assessed objects. Thank you.
Replies
0
Boosts
0
Views
47
Activity
1d
Which macOS version first exports Logger.isEnabled(type:)?
An app built with Xcode 27.1 for a macOS 15 deployment target called Logger.isEnabled(type:). In the SDK's swiftinterface the method sits under Logger's @available(macOS 11.0, ...) with no availability of its own, so it compiled without a warning. On macOS 15.6.1, libswiftos.dylib doesn't export it, and dyld stopped the app at launch: Symbol not found: _$s2os6LoggerV9isEnabled4typeSbSo0a5_log_E2_ta_tF Expected in: /usr/lib/swift/libswiftos.dylibThe macOS 15.5 SDK's libswiftos.tbd doesn't list the symbol and the 27 SDK does. I haven't checked macOS 26. Switching to OSLog.isEnabled(type:) fixed it. Which macOS version first exports this symbol? Write-up: https://yardlet.app/blog/logger-isenabled-macos-15.html
Replies
4
Boosts
0
Views
113
Activity
2d
Which memory entitlements can an independent iOS developer use?
I'm researching the memory limits and capabilities available to ordinary third-party iOS applications. My project, Kairavox, is a native iOS application whose initial CPU design uses a software AArch64 interpreter. Its long-term goal is to run a genuine, unmodified iPadOS installation as a guest. Before making further architectural decisions, I want to understand what memory capabilities are actually available to independent developers. Our initial guest research target is an iPad 9th generation running iPadOS 27.2.1. The host iPhone model has not yet been fixed. I've found Apple's documentation for: Increased Memory Limit, with the key com.apple.developer.kernel.increased-memory-limit. Extended Virtual Addressing, with the key com.apple.developer.kernel.extended-virtual-addressing. Increased Debugging Memory Limit, which Apple describes as providing additional memory during development and internal testing. I'd appreciate clarification on the following for current iOS versions: Which iPhone models and iOS versions support each of these capabilities? Is there a public compatibility list? Can an independent developer request the Increased Memory Limit entitlement? If so, what is the current request and provisioning-profile process? Does Extended Virtual Addressing increase only address-space capacity, or can it also raise an app's physical-memory limit? What is the exact entitlement key for Increased Debugging Memory Limit, and what are its limits for development, ad hoc, and internal TestFlight builds? Are any of these capabilities available with free Personal Team signing? Does paid Apple Developer Program membership change eligibility, or is separate authorization required? If granted, may an app use additional available memory as backing for software-emulated guest RAM? Are there documented limits or workload restrictions? I understand that an entitlement would not reserve physical RAM or prevent memory pressure and termination. Apple's current iOS supported-capabilities table lists Extended Virtual Addressing and Increased Debugging Memory Limit, but I could not find Increased Memory Limit there. Is that table complete for this capability, or does availability depend on the device, account, or another process? I'm not assuming these entitlements are available to every developer. Documentation or specific eligibility guidance would be very helpful. Thank you.
Replies
1
Boosts
0
Views
49
Activity
2d
Is JIT execution possible for ordinary third-party iOS apps?
I'm researching whether a normally signed third-party iOS application can use Just-In-Time (JIT) compilation on a stock, unjailbroken iPhone. My project, Kairavox, aims to run a genuine, unmodified iPadOS installation as a guest inside a native iOS application. JIT compilation is central to our intended execution architecture: we want to translate and execute guest AArch64 instructions through dynamically generated native code. We intend to test through personal development signing and sideloading using AltStore or SideStore. App Store distribution is not a requirement. I've found Apple's documentation for: Allow Execution of Just-In-Time (JIT) Compiled Code Entitlement Porting Just-In-Time Compilers to Apple Silicon Alternative Browser Engines in the European Union However, the first two appear to concern the macOS Hardened Runtime context. Apple's alternative browser engine provisions also describe a specifically authorized exception, which does not describe our application. I'd appreciate clarification on what is supported for an ordinary third-party iOS app: Is there a documented iOS API or entitlement that allows a normally signed third-party app to allocate writable memory, generate machine code, and execute that code at runtime? Does iOS support MAP_JIT for ordinary third-party applications, or is it restricted to other Apple platforms or specially authorized applications? Is com.apple.security.cs.allow-jit exclusively a macOS Hardened Runtime entitlement, or does it have any application on iOS? Can an app using free Personal Team development signing execute JIT-generated code? Does paid Apple Developer Program membership change this? Do development, ad hoc, or other signing arrangements differ in their JIT permissions? Is there a documented process for an independent developer to request the necessary capability? Does installing an app through AltStore or SideStore change its OS-granted executable-memory permissions, or does it retain the permissions associated with its signed build? Are there any documented restrictions on using JIT-generated native code for CPU emulation or virtualization workloads? I understand that Apple's EU alternative-browser-engine authorization is a narrow exception for eligible browser applications. I'm not assuming it applies to Kairavox. The main question is whether an independent developer can build and test a JIT-based application on a stock iPhone using an officially supported signing and permission model. Thank you.
Replies
1
Boosts
0
Views
51
Activity
2d
Improve PTT System UI Visibility When Location Indicators Are Active
Observed Limitation When location services are active, the iOS location indicator may overlap with or hide the PTT blue button or system UI in the notch / Dynamic Island area. Requested Changes Ensure PTT controls remain visible and accessible when location indicators are displayed. Improve system UI positioning to prevent conflicts with other system indicators.
Replies
1
Boosts
0
Views
35
Activity
2d
Support Multiple PTT Applications on the Same iOS Device
Observed Limitation The PTT framework appears to restrict active usage to one PTT application per device. When another application is already registered or connected to a PTT channel, a second application may be unable to use the PTT service. Requested Changes Allow multiple PTT applications to coexist on the same device. Support independent registration and channel management for each application. Provide system-level coordination of PTT resources between applications.
Replies
1
Boosts
0
Views
31
Activity
2d
Can a restore replace a file in an App Group container while the app's process is alive?
For an iOS app that stores a SQLite database in its App Group container and has no extension targets, can iCloud restore, Finder or Apple Devices restore, or Quick Start replace a file in that container while the app's normal process remains alive, including while suspended? If iOS terminates the process first, can the app relaunch before all App Group files have finished restoring? Please identify any differences between these restore paths and any documented guarantee. Related: thread 845479 gave the general rule for the app's own container.
Replies
3
Boosts
0
Views
127
Activity
2d
Supported non-admin service identity for a macOS LaunchDaemon
I'm developing a private macOS application on an Apple-silicon Mac mini running macOS Golden Gate 27.2. I'm evaluating a system LaunchDaemon running under a dedicated, non-administrator identity that cannot log in interactively. A separate desktop application would communicate with the daemon through authenticated local IPC. Before implementing this architecture, I would like to establish the officially supported approach. My main question: What is the Apple-supported method for creating and maintaining a dedicated, non-administrator, non-interactive service identity for a system LaunchDaemon on macOS 27.2? In particular: Is there a documented procedure for creating, restricting, disabling, recovering and eventually removing this identity? Are dscl, sysadminctl or another account-management mechanism supported for this purpose? Can a LaunchDaemon run under this identity without an interactive user login, including when registered through SMAppService? Are there any secure-token, FileVault, volume-ownership or keychain restrictions that would affect this design? If a dedicated non-login service identity is not a supported architecture, what alternative does Apple recommend? I'd particularly appreciate links to official Apple documentation or guidance from Apple engineers. Thank you.
Replies
10
Boosts
0
Views
579
Activity
3d
Full Disk Access on macOS 27.3
I'm looking into the changes being implemented and I find this way of handling by Apple on short notice problematic. Now our customers (those that don't have MDM) will have to jump through hoops to enable FDA for our product, a security product that also uses Endpoint Security. We already have the entitlement for endpoint security, which requires FDA in order to work, so why make it so difficult instead of just allowing FDA for apps that have this entitlement? Why only backup applications are exempted?
Replies
2
Boosts
0
Views
130
Activity
3d
Access to related files outside Sandbox with NSFileCoordinator and NSFilePresenter does not work anymore in macOS 27.3 beta 2
In macOS 27.3 beta 2, it is no longer possible to use NSFileCoordinator with NSFilePresenter instances to open a SQLite file with related WAL and SHM files when a sandboxed app has access to the primary SQLite file. In macOS 27.3 beta 1 and previous macOS releases, the Related File Access API works as expected. This happens regardless where the files are located, so it seems to be unrelated to recent changes in Privacy & Security, although it could be an unexpected side effect of these changes. Instead of correctly registering NSFilePresenter instances, errors like the following are logged in the XCode console: NSFileSandboxingRequestRelatedItemExtension: Failed to issue extension for /Users/testuser/Desktop/Sample/Example.sqlite-wal because: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" (The related item is protected by a different storage class than the primary item) UserInfo={NSDebugDescription=The related item is protected by a different storage class than the primary item} +[NSFileCoordinator addFilePresenter:] could not get a sandbox extension. primaryPresentedItemURL: file:///Users/testuser/Desktop/Sample/Example.sqlite, presentedItemURL: file:///Users/testuser/Desktop/Sample/Example.sqlite-walThe mentioned Related File Access API is documented here. I have filed a Feedback, which includes a sample project: FB25625743 My question is: Is this a bug, or new intended behavior, or is there something else changed that should be dealed with when using this API in macOS 27.3 beta 2?
Replies
1
Boosts
0
Views
73
Activity
3d
Can macOS verify a worker’s effective sandbox policy before it runs?
I’m building a local app on an Apple silicon Mac. Before a worker or any of its child processes can run, I need to verify the worker’s effective filesystem and network restrictions, including inherited restrictions. I need to allow that same pending launch only if the policy matches, and deny it if verification fails or times out. I reviewed Apple’s App Sandbox guidance and the Endpoint Security documentation for exec authorization and entitlement metadata. I haven’t found documentation showing that these expose the complete effective policy for the pending launch. Is there a supported public macOS API that provides this guarantee? If so, which API and macOS versions support it? If not, is this outside what the public APIs can verify?
Replies
1
Boosts
0
Views
201
Activity
3d
Subject: Critical APFS Data Loss Bug & Error 1110 Loop during official Finder Update on iPhone 14 (A15)
Hello, I am requesting an engineering escalation regarding a critical bug in Apple's APFS update pipeline that trapped an iPhone 14 (A15, 128 GB) in recovery mode during an official Finder update from iOS 16.6 to iOS 18 (27.2.1, 24B156) on macOS 14.5. The device hardware is 100% healthy (Apple MRI diagnostics all green), the passcode is known, and 101,175 MB (341,967 files) of user data remain intact on the flash storage. However, the device cannot boot or complete an update due to a corruption caused by Apple's own restore tools. --- ### What Happened (Verified in Logs): 1. **Initial Full Storage State:** The device had ~105 GB utilized and was updated via Finder using "Update" (not Restore). 2. **Destructive fsck Behavior:** In pass 3, the restore ramdisk ran `/sbin/fsck_apfs -dy /dev/disk2`. On the nearly full container, fsck erroneously flagged 8,182 live omap mappings as "orphans" and deallocated them, causing extent-ref b-tree node `0x10bb3` to be zeroed out (TRIMmed by the flash controller). 3. **Split Failure:** In pass 4, the iOS 18 System volume installed and sealed, but `split_data_volume` failed in 4 seconds when `apfs_migrator` encountered block `0x10bb3` (`obj_read` checksum failure returning EILSEQ / error 92). 4. **False Error 1110 Loop:** Every subsequent attempt now halts immediately at `space_checks` with Error 1110. --- ### Reverse Engineering Proof: Disassembly of `restored_update` (arm64e, VA 0x10001afcc / 0x10001b0e8) confirms a major error-handling bug: When `splitter_dump` encounters the unreadable block `0x10bb3`, it fails with `EILSEQ` (92). Instead of handling this error, `restored_update` executes: `mov x19, #-1; mov x0, x19; ret` The caller receives `-1 bytes of free space`, logs: "Data volume requires splitting. Splitter will leave -1 bytes of free space after completion. Current free space on device: 6620069888 bytes. Insufficient space on device to run splitter" and aborts with **CHECKPOINT FAILURE:(FAILURE:1110)**. The device is NOT out of space (it has 6.3 GB free); it is blocked solely because `restored_update` misinterprets an EILSEQ filesystem error as negative free space. --- ### Current State & Request: - The encryption keys and SEP/gigalocker are intact (`gigalocker: ONLINE`). - In the restore ramdisk, `/dev/disk2s2` mounts cleanly as read-write on `/mnt2`. - Zero APFS snapshots remain on the volume, meaning the extent-ref tree is theoretically fully reconstructible from the valid fsroot inode tree. I am requesting assistance from CoreOS / APFS engineering: 1. Is there an engineering update ramdisk or build that can bypass the `splitter_dump` EILSEQ check, or rebuild the extent-ref tree, so the update can finalize? 2. Alternatively, can an engineering liaison facilitate a non-destructive extraction given that the volume mounts read-write and the user passcode is known? I can immediately provide full terminal transcripts, Finder updater logs (`iPhoneUpdater-*.log`), and disassembly details. Thank you, Samuel Journo
Replies
1
Boosts
0
Views
106
Activity
3d