“file uri scheme”

An other, related issue with CGSetDisplayTransferByTable() - this is probably not the best place to note this, but since macOS Tahoe there is an inconsistency in how the API works. The 26.4 RC is also affected. Before macOS Tahoe CGSetDisplayTransferByTable() redefined the color table of the SDR range and clipped the HDR range (much like custom color profiles in macOS usually do the same). In macOS Tahoe it does the same thing for most displays – except for the built-in XDR displays, when auto brightness is enabled and the display is in EDR mode (meaning: there is some HDR content on screen). When this happens (XDR + auto brightness + EDR mode), the contents of the CGSetDisplayTransferByTable is being used to multiply the entire EDR (SDR+HDR) gamma range instead of overwriting the SDR range and clipping the HDR range. This might be a blessing in disguise for some apps (that use this feature for color adjustments or brightness upscaling like BetterDisplay - as this allows avoiding HDR clipping when a custom co

Can you file a bug on this and upload the full spindump there? I opened one last week. Case-ID: 18860388 ...this is almost CERTAINLY caused by your ES client. Yes. The question here isn't what revisiond is doing, it's who revisiond is waiting on. Some other thread locked that lock and is now stuck, which is the real issue you need to sort out. It definitely revisiond (well, APFS), that's holding the lock. There are dozens of threads where the shared lock points at revisiond [426] thread 0xc0616d), both for reading and writing. *940 apfs_vnop_getattr + 312 (apfs + 604336) [0xfffffe000beacff0] *940 IORWLockRead + 144 (kernel.release.t6000 + 496568) [0xfffffe00088e53b8] *940 ??? (kernel.release.t6000 + 497548) [0xfffffe00088e578c] *940 ??? (kernel.release.t6000 + 619452) [0xfffffe00089033bc] *940 ??? (kernel.release.t6000 + 624472) [0xfffffe0008904758] (suspended, blocked by krwlock for reading owned by revisiond [426] thread 0xc0616d) *940 apfs_vnop_read + 708 (apfs + 555972) [0xfffffe000bea1304] *940

This is actually possible, though it requires a different approach than the typical single-AVAudioEngine setup. The key insight is that iOS allows multiple AVCaptureSession instances to coexist under certain conditions. You can configure two separate audio routes: Use AVCaptureSession with the AirPods as the input device for your speech recognition pipeline. Set the audio session category to .playAndRecord with .allowBluetooth option. For video recording with the built-in mic, use a second AVCaptureSession (or the camera API you are already using). The built-in mic can be explicitly selected as the audio input for this session. The catch is you need to manage the audio session category carefully. The .mixWithOthers option is essential here — without it, one session will interrupt the other. Another approach that avoids the dual-session complexity: use a single AVCaptureSession that captures from the built-in mic for video, and run SFSpeechRecognizer (or the new SpeechAnalyzer on macOS 26 / iOS 26) on the same

AFAIK there’s no magic here. And I tried reproducing this on my main work Mac and didn’t have a problem. @DTS Engineer When I have this issue, it also comes with a prompt that appears offering to download the device support files, but this fails because the files aren't available from the software update server. Given that you're an Apple employee, is it possible that your work Mac has access to an internal software update server that offers the required device support files, but that the public software update server doesn't?

Yeah, that's probably a bug in the iOS Simulator runtime that incorrectly annotated some of the files within the data directory. I bet if you look in that directory, you'll see some leftover spotlight files. I think you can delete them manually with sudo rm -rf ~/Library/Developer/CoreSimulator/Devices/...

refiled it under the Developer technologies and SDKs topic mentioned in the how to file link posted above: FB22297047

Thanks for confirming and hope a fix will come soon. I did file a bug: FB22063128 As for the view hierarchy, I've since found that the amount of flicker seems to be dependent on the amount of pen strokes you do before you zoom. If you draw heavily on the entire paper before zooming you do eventually reach a state where the flickering doesn't stop and continues forever.

Enhancements to Xcode's functionality should be filed through Feedback Assistant so the appropriate teams can consider the request. It would be helpful to detail why you'd like Xcode to behave as you describe and how that would help your development workflows when you file that.

@ChiliDev05 Please file a code-level support request for assistance.

Thank you for the sample project and the video — both were very helpful. We were able to reproduce the flickering on iPad with Apple Pencil using your sample project. We tested several potential app-level workarounds (deferring contentInset updates, guarding against layout recalculation during active drawing, consolidating CATransaction blocks) but none of them resolved the issue. Based on our investigation, the flicker appears to be occurring within PKCanvasView's internal tile rendering when drawing at non-1x zoom scales, rather than being caused by anything in your app code. Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. I'll check the status next time I do a sweep of forums posts where I've suggested bug reports and post any information about changes I am able to share to

We're experiencing a deadlock on certains systems when our software is installed, which is causing side effects in our process (and likely others) such as blocked queues and increased memory usage. According to the spindump, revisiond appears to be holding an exclusive lock within the kernel. Can you file a bug on this and upload the full spindump there? That's the easiest way to transfer large data files and I may eventually want a sysdiagnose. Having said that... Our agent uses Endpoint Security Framework to monitor events, and provide anti-tamper functionality for installed components and processes. While several EndpointSecurity calls appear in the spindump stack traces, we don't have any evidence that any calls from revisiond were blocked. ...this is almost CERTAINLY caused by your ES client. What we'd really like to to understand what that lock is (appears to be decompressing an object on an APFS volume), what revisiond and APFS are doing with it, and what might cause it to deadlock. Y

@SeoulForest Did you file a bug for that? I do not see it on your post. Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert Pascual
  Worldwide Developer Relations.