dsym file

My first thought was some kind of cross-platform PDF code that wasn't doing file coordination properly. But what you're showing is basic NSDocument file reading. However, NSDocument can get very complicated when writing. You said you're writing a viewer app. Are you sure you've specified the role for PDF as Viewer? There would have to be some other kind of change, possibly to attributes or permissions, in order for Time Machine to balk. Reading a file should be a no-op in that respect.

You need the original dSYM file, and as part of general practice, you should always hold on to the Xcode archives that you upload to TestFlight or the App Store, for this reason. If we rewind a few steps, what are the steps in your build process that mean that you currently have the .symbols files, but not the original dSM file? — Ed Ford,  DTS Engineer

The last line of the message says: Please file a bug report against lldb reporting this failure log, and as many details as possible Let's start there — what is the FB of your report in Feedback Assistant? Further, make sure to include things like the Xcode version and the OS version you are debugging on, and to see if this reproduces with the latest Xcode version, currently Xcode 26.2. — Ed Ford,  DTS Engineer

Nope.. just two apps, I checked the headers and there is no crossover. I did copy and paste some items from the original project initially.. but I deleted those as the design matured. I think thats probably where the references are coming from. I did a grep on the project directory and the references don't occur in the project file for the app... no clue. I have cleaned the build, quit Xcode.. and they remain.

Hello @mike sldkcjnsdmhvbsdh Thank you for documenting and providing workarounds. I am able to reproduce this issue and would like you to file a Bug Report. After that, please reply with the FB number in this thread. I will make sure it is seen by the relevant engineering team. In the report, I recommend sending the project as an attachment, we often look for attachments, and feel free to also include the GitHub link as your documentation is beyond helpful to us in our investigation and others who may run into this issue. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Thank you!  Travis Trotto - DTS Engineer

The Apache logs tell you what the problem is: Error reading certificate file (../credentials/test_certificates.json): Error Domain=NSCocoaErrorDomain Code=260 The file doesn’t exist.UserInfo={NSUnderlyingError=Error Domain=NSPOSIXErrorDomain Code=2 No such file or directory, NSURL=../credentials/test_certificates.json -- file:///home/azuki/, NSFilePath=/home/credentials/test_certificates.json} It's expecting to find the credentials in /home/credentials/ but they are not there, which means Apache wasn't running with the environment variable FPS_CERT_PATH set. If you cannot figure out how to set this variable for Apache in your environment, you could copy the credentials folder into /home/credentials/.

Hi, I wanted to let you know that I made changes related to TLS so it matches the cipher suite Apple uses. I configured the access rules so nothing is being blocked, and I ran tests using PowerShell and OpenSSL—every result returns HTTP/1.1 200 OK. I also verified that the URL Apple says it will use to validate the file under /.well-known works correctly and it does display the contents of the file. However, when I try to verify the domain in Apple’s portal, I still get the same error: “Domain verification failed.” Could you please help us with an alternative solution or any additional verification steps we should perform? Thank you.

I've written an PDF viewing app, and there seems to be a correlation between files opened by the app and files that Time Machine says couldn't be backed up. Can you post the full contents of the error logging you're seeing? Also, are these files stored on your boot volume or somewhere else (particularly an HFS+ volume)? It's possible there's an edge case I'm overlooking, but Time Machine’s general backup flow is to: Snapshot the source volume. Backup the contents of the snapshot. (eventually) delete the backup. The major benefit of this is that it improves overall backup quality, as you're backing up a single moment in time, not a spread of time. However, it also means that your app’s own interactions with your files shouldn't really matter, as Time Machine isn't actually backing up the same file as the one you have open. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Hi @StudioNeueMuseen There's no supported way for you to query gaze enrollment status or receive a notification when it changes with the APIs currently available. If you'd like us to consider adding the necessary functionality, please file an enhancement request using Feedback Assistant. Once you file the request, please post the FB number here. If you're not familiar with how to file enhancement requests, take a look at Bug Reporting: How and Why?

Thanks for all the details and the funny anecdote. I'll ask the user to run the cp command, but they told me they have some other work to do at the moment and need a break. In the meantime, since you said it's a SMB issue, is there a way I can reproduce the Result too large myself? Yes. To start with here: Setting a large resource fork like mentioned in that StackOverflow post causes the mentioned error Argument list too long. Was this on your SMB target or on your local (APFS) volume? If this is happening on the local volume, then I think the problem is that you're hitting the max transfer size limitation of fsetxattr. You need to break the transfer up into smaller individual segments, as copyfile does here. As a side note here, there's an open question here as to how the problem file originally got to the SMB server. On modern systems, we primarily use the resource fork to store compressed data (as I described above), but we also got out of our way to NOT export that configuration out of the system

@ChristianBr if you are unable to resolve this problem by updating your certificates, please consider filing a bug report and opening a code level support request. If you open a support request, include the url of this forums thread and the feedback number so the request can be assigned to my attention. https://developer.apple.com/support/technical/ Bug Reporting: How and Why? has tips on creating your bug report.

Since this question isn't about a specific API and it is about some Apple application programs I recommend filing a bug report and switching back to using a non-beta system software release where this problem does not exist. Normally this is the sort of question you'd ask in the Apple Support Community (Though, I realize questions about beta releases are often referred from there to these developer forums). Bug Reporting: How and Why? has tips on creating your bug report.