file uri scheme

Thank you, Yes, I have filed a bug report FB21249476.

This is not legal advice, nor a statement from Apple. I will share what I'm going to do in my apps and recommend to others. How I interpret 121.056 (B) (1) is basically, use the signals when they're available. If they're not available, you can't use them. You can't do the impossible. So if you have an app update that supports iOS 26, implement it there, and < 26 you simply can't. As a developer, it is impossible to use the age signals provided by the App Store if they don't exist. If you're not comfortable with this approach, file feedback asking for support on devices < 26. Hypothetically, if Apple were to add support to, say iOS 18, it would still be something like iOS 18.8.x or higher. I am closely following the OS Usage page and waiting for an update to show the adoption of 26. https://developer.apple.com/support/app-store/ For my specific usage, I'm moving my apps to 26+ for my updates. However, I have apps that include watch extensions, and an Apple Vision Pro target. This presents its ow

Hi Kevin, I have filed the bug report as requested. The Feedback ID is FB21256805. I've included the IORegistry dumps showing the missing keys when using the standard API versus the successful injection using the SetProperties workaround. To answer your specific question: Are you sure you're setting all of the required key set, particularly 'kIOMaximumSegmentByteCountWriteKey'? Yes. We confirmed that kIOMaximumSegmentByteCountWriteKey was correctly set to 65536 (64 KB), and kIOMaximumSegmentCountWriteKey was set to 129. Thanks again for your help in narrowing this down. Best Regards, Charles

Hi @DTS Engineer and thanks :) I hope that your boss will get you a iPhone 17 😅 I'm trying to attach the ips-file again. I added the.txt extension to make it possible to attach it. I hope it will not screw up and make it an inline text-box when I git 'Reply' 😬 Looking at the ips-file I found that it does not show the finding that Xcode show, e.g., Thread X: Use of deallocated memory but it then misses Memory allocated by Thread 1 and Memory deallocated by Thread 1, so I am not sure the ips-file is that useful for MTE :( CrashReport-2025-11-28-141148.ips.txt

This is tricky. My best guess is that translationTask(_:action:) is missing all the magic concurrency decorations required to make this work nicely. To get this to build right now you can mark the closure as sendable, like so: .translationTask(configuration) { @Sendable session in do { try await session.prepareTranslation() } catch { // Handle any errors. } } This compiles in Xcode 26.1 using the Swift 6 language mode and: Approachable Concurrency enabled Default Actor Isolation set to MainActor Note I’m using prepareTranslation() in my examples because it’s simpler, and that makes it easier to focus on the core issue. The drawback to this is that you can no longer access main-actor-isolated state from the closure. You can work around that using MainActor.run(…): try await session.prepareTranslation() … no isolation … await MainActor.run { … main-actor isolated … } Clearly this is less than ideal and I encourage you to file a bug against… actually, I think it’d be best to file a bug against

None of this strikes me as particularly surprising. The packet path is extremely ‘hot’, so adding any work to it is costly. The best thing you can do to improve performance is to avoid the .delay verdict, but your test code is already doing that. Before I send you off to file a bug about this, I have a couple of things for you to check: Make sure you reproduce this on a ‘clean’ machine. I often see weird problems being reported by folks only for us to track it down to some enterprise security setup affecting their main work Mac. If you have any additional network debug logging enabled — see the various instructions on our Bug Reporting > Profiles and Logs page — make sure to disable that during your tests. Usually I test NE stuff on a VM, but in this case you’ll want to run your tests on real hardware. VMs are great, but one place where they differ from real machines is performance. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='809205021, vtsang2025, /thread/809205, /profile/vtsang2025'] Is it an expected behaviour or a bug in the Release Candidate? [/quote] I don’t think that actually matters, in that it’s still fundamentally the wrong behaviour )-: Please do file a bug about this. I’d appreciate you posting your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Indeed. While this is a long-standing issue, I was kinda surprised that we don’t have existing bug report for it, or at least not one that I could find. So thanks for filing FB21252859. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I recommend that you report this officially by filing a bug. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for filing FB21121092, and also for the neat shout out regarding how MetricKit aided your investigation here. As to FB21121092, your report made it into the iOS 26.2 RC Release Notes as an acknowledgement of this issue and how it affects developers using the DeclaredAgeRange APIs. There isn't anything that I can share here about the state of our investigation right now, but it is progressing, and I'll provide an update here for the community once I have more information to share. — Ed Ford,  DTS Engineer

@DTS Engineer Thank you for the detailed reply! It may take me a while to respond to all of your points, but here is a start: Yes, the issue here is that nothing (no app launch and/or document open) is happening. The target app is a copy of BBEdit in my ~/Applications folder. Using the open command to open the same text file with the same copy of BBEdit works fine. Regarding How did your app get that file URL? Is your app able to open the file? And is the file already downloaded or is it still dataless? The file is downloaded. My app gets the URL by drag and drop from the Finder. My app does not attempt to open the file on its own, it just forwards the URL to be opened by another app, BBEdit in this case, somewhat like what the Dock does. Dang, now all of a sudden it's working. Obviously I need to do a lot more testing.

One thing that may be happening here is that your app is launching without the debugger attached, which is where Quinn's points about the system log come in. You can use the macOS Console app to look for your logs once you're using OSLog. Something I like to do in addition to that is configure LLDB to wait to attach until your process is launched. That way, when you use Siri to launch the app, the logs you're expecting will be picked up in the LLDB console. You can configure this in your Xcode scheme, under the Run options. With that configuration set, if you press the Run button in Xcode, the system starts LLDB, but not your app like usual when you press the Run button. You can then launch your app through Shortcuts or Siri, LLDB will now attach automatically, and record all of your OSLog statements inside of Xcode for that launch sequence. — Ed Ford,  DTS Engineer

When I pass a file path URL of a file in iCloud Drive to -[NSWorkspace openURLs:withApplicationAtURL:configuration:completionHandler:], it fails. A few different suggestions/questions: Have you tried this with different apps and, ideally, using a dedicated test app as the target? Related to that point, what happens if you use open (which basically does exactly what you're doing) to do the same thing? Note that I'm NOT suggesting you use open instead of NSWorkspace, just trying to clarify if the failure is specific to your app or not: open -a How did your app get that file URL? Is your app able to open the file? And is the file already downloaded or is it still dataless? Is the target path in /Applications/ or somewhere else? If it's not in /Applications/, does your app have access to the location it's located at? Covering a few details: There is no exception, and the completion handler isn't called. I'd have to look at the code, but I suspect the completion handl