dsym file

[quote='875131022, IHadToChooseAUserNameAndIdidntWantTo, /thread/809959?answerId=875131022#875131022, /profile/IHadToChooseAUserNameAndIdidntWantTo'] Are there public APIs to assess notarization? [/quote] That’s tricky, because it depends on your definition of API. The codesign tool has a --check-notarization operation that does that. See Testing a Notarised Product and the codesign man page. While that’s documented, I’m not a fan of using command-line tools as APIs. The code signing requirement language has the notarized constraint. That’s not documented where it should be but it’s debatable whether that’s just because the parent document is stuck in the Documentation Archive. Annoyingly, an equivalent constraint has not been added to the LightweightCodeRequirements framework. If you think that’d be useful, I encourage you to file an enhancement request for it. And if you do, please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple

I wanted to shared a quick update on FB21858319. I figured you’d appreciate that given all the work you put in to help isolate it (-: My experience is that Apple is pretty good about fixing local network privacy problems like this one. The critical factor is reproducing the problem, which is why I’ve been so happy to get your cooperation here on this thread. Based on our preliminary analysis of your bug, we think we know what’s going on here. I’m going to offer a little insight into that below, but first I want to set some expectations. Understanding the problem isn’t the same as fixing it. I can’t offer any concrete timeline as to when a fix for this problem will be released. However, when we start seeding a beta release that contains the fix, you should be notified via Feedback Assistant [1]. As to what’s actually happening here, lemme explain a bit about how local network privacy works. As described in TN3179, the local network privacy state on macOS is per user. However, macOS’s networking stack is global

I have a standard spiel about this which I’ve included at the end of this reply. Please read it through first. With that in mind, let’s come back to your specific questions: [quote='814841021, Jackson_Hsieh, /thread/814841, /profile/Jackson_Hsieh'] Is it expected behavior for notarization submissions to remain in “In Progress” for such a long period without logs? [/quote] Yes, assuming you’ve hit the “in-depth analysis” path. [quote='814841021, Jackson_Hsieh, /thread/814841, /profile/Jackson_Hsieh'] Is client-side timeout and re-submission the recommended handling for CI workflows? [/quote] I see two common patterns reported here on the forums: Developers hit this on their first notarisation attempt, or otherwise very early in their Mac development ‘journey’. Developers have been happily notarising for a while and then suddenly bump into this. In the first case my advice is to simply wait. That’s the focus of the boilerplate text that I included at the end of this reply. My understanding is that you fall into

I filed FB21890081 about missing API to distinguish between a BGContinuedProcessingTask expiring from user interaction vs the system.

Hi Kevin, filed bug number is FB21888307. I provide partial code on bug. Reply to your question: That address should have come from your driver, so how did it exceed 32 bits? All of our APIs for retrieving a bus address should either provide an address that meets your specification or fail entirely. More to the point, even if they some how did return a larger address, why/how would your driver have written a larger address when it was only prepared to handle a 32 bit address? Yes, address comes from my driver by gen64IOVMSegments API. And at the beginning, I didn't know that the address allocated through the API were always >32 bit, so when I received an address >32 bit, I didn't directly return, but continued to use it, resulting in a kernel panic. Next, the big question is how much memory are you actually trying to map? And have you done any experimentation with smaller mappings? I trying to map 20 KB memory, I have already tried 1 Byte or 4 KB, still get 64-bit address. And maximum DMA data

Hello! That definitely looks like a problem! I think that you’re encountering two separate issues: one with download cancellation and another with internal analytics. For the former issue, we’ll try to reproduce it on our side. It would be super helpful if you could file a feedback report in Feedback Assistant, making sure to attach sysdiagnose logs from the device on which asset-pack cancellation failed soon after reproducing the behavior. Plus, filing a feedback report ensures that you’ll be automatically notified when we fix the issue. We’ll let you know if we figure out a workaround before the fix is available. Thanks! The fact that version 0 of the asset pack with the ID X-XXXXXX-XXX finished being downloaded couldn't be reported: Error Domain=NSCocoaErrorDomain Code=3851 Property list invalid for format: 200 (property lists cannot contain objects of type 'CFError') That error message concerns the latter issue. If you installed the app from TestFlight, then the system collects data abou

Please file a Feedback on this, with a minimal sample project.

XcodeRead - Read files from the project XcodeWrite - Write files to the project XcodeUpdate - Edit files with str_replace-style patches XcodeGlob - Find files by pattern XcodeGrep - Search file contents XcodeLS - List directory contents XcodeMakeDir - Create directories XcodeRM - Remove files XcodeMV - Move/rename files BuildProject - Build the Xcode project GetBuildLog - Get build output RunAllTests - Run all tests RunSomeTests - Run specific tests GetTestList - List available tests XcodeListNavigatorIssues - Get Xcode issues/errors XcodeRefreshCodeIssuesInFile - Get live diagnostics ExecuteSnippet - Run code in a REPL-like environment RenderPreview - Render SwiftUI previews as images DocumentationSearch - Search Apple docs and WWDC videos XcodeListWindows - List open Xcode windows The above is a list of MCPTools exposed by Xcode. Im am interested in the DocumentationSearch Tool . Here Xcode is able to search only Apple Docs. Lets say i am using

It seems that the DMA request address initiated by FPGA exceeded 32 bits, which was intercepted by PCIe root port and resulted in a kernel panic.This is also the case on macOS (M2). Please file a bug on this, upload the full panic report there, and then post the bug number back her. I'd like to get a clearer picture of what actually failed. I'm also a bit confused by this point: It seems that the DMA request address initiated by FPGA exceeded 32 bits, That address should have come from your driver, so how did it exceed 32 bits? All of our APIs for retrieving a bus address should either provide an address that meets your specification or fail entirely. More to the point, even if they some how did return a larger address, why/how would your driver have written a larger address when it was only prepared to handle a 32 bit address? Next, the big question is how much memory are you actually trying to map? And have you done any experimentation with smaller mappings? __ Kevin Elliott DTS Engineer, CoreOS/Ha

This doesn't make sense to me... In brief, compressed files were implemented by: Compressing the file’s contents. Storing that data in the resource fork. Adding a file flag (UF_COMPRESSED) which tells the VFS layer this file is compressed. The VFS layer then checks for files with the UF_COMPRESSED flag. When it sees that flag: It hides the resource fork from most/some API layers. When the file is opened, it decompresses the contents returning them as if it were a normal file. That last point means that a copy engine that's unaware that a file is compressed: cp decompressed the file, which ended up stripping the xattrs …ends up automatically decompressing it. Reordering things a bit: That I can only reproduce it when at the other end of the SMB connection there is a Mac, or if the volume at the other end is formatted APFS? Yes and no. The problem here is that the full range of SMB servers is EXTREMELY large and diverse. Similarly,

Thanks for the post, can you provide more information about what you are trying to accomplish? Guessing to create your own documentation files? There are many 3rd party solutions for creating documentation out there, Xcode’s built-in documentation viewer and support are primarily tailored to Apple’s own frameworks. 
I believe that if your SDK includes HTML documentation stored locally or hosted on a server, you can add a custom entry in Xcode → Preferences → Locations → Documentation to point to your documentation URL. This won’t integrate with Quick Help but will allow you to browse the docs via Xcode’s browser view? But I am not completely positive how to do that in latest versions of Xcode. Any HTML documentation can be browsed using a local browser. Xcode does not currently expose public APIs to connect to custom MCP (Web Service Discovery) servers for API documentation. The Claude settings you mentioned are unrelated to Xcode’s documentation capabilities and cannot be used to modify how Xcode in