dsym file

Thank you for the detailed information. To investigate this behavior thoroughly, could you please file a report using Feedback Assistant and include a sysdiagnose log? Part 1 How to File the Feedback Report Navigate to Feedback Assistant and log in with your Apple Developer account. Choose iOS & iPadOS for the product. For the report details, please include the detailed description and steps to reproduce from your post as well as the sysdiagnose. Part 2 Capture and Attach sysdiagnose Go to the Bug Reporting - Profiles and Logs page. Follow the instructions to install the necessary profiles for App Store issues. Once the profiles are installed, reproduce the purchase issue in your app and capture the sysdiagnose. Attach the resulting log file to your Feedback Assistant ticket. Part 3 Share the Feedback ID After you submit the report, please share the Feedback ID here to find your report and track its progress.

You can host the zip file into any sharing website or you can put the project files to any git provided website. Hope this helps Albert Pascual
  Worldwide Developer Relations.

Since my AppStore app works, I must oversee something little that has this big effect. I can't otherwise explain the negative result. I have setup a super simple Git project here: https://github.com/vrunkel/RelatedFileTest I took a look at your sample and I'm not sure what's going on here either. Can you file a bug on this and then post the bug number back here? __ Kevin Elliott DTS Engineer, CoreOS/Hardware

I've been using TM since Leopard, and I have tens of documents regularly open in a variety of applications, and I've never seen this error until I started using my own app. The app's role is an Editor, as it can modify and save files. So, I think there are actually two different issues at work here: I think TM is delaying the backup because it's been told your document has pending, unsaved changes. I'd start by checking the documentEdited property, which should be false (unless the document has been edited). The fact that you need to quit the app (not just close the document) implies that you're leaking a document reference of some kind, which is then extending the impact of #1 beyond the point when you closed the document. In terms of how you investigate this further, I would start with very focused testing to specifically validate the general theory above. A few ideas and suggestions: What open files does Activity Monitor show when your app is running and is that matching up properly with

Apologies I meant to ask about activity tracing as well (they are related to this topic but if we think another forum post is better I can do it too). At certain point this also became one of the directions we wanted to explore but we've only uncovered more questions. The related documentation stated something but very vaguely. https://developer.apple.com/documentation/os/generating-log-messages-from-your-code?language=objc#Choose-the-Appropriate-Log-Level-for-Each-Message If an activity object exists, the system captures information for the related process chain We had hoped that this would somewhat play into the speculative logging approach we had touched upon, in the sense that if we try to log an error or fault within an activity, then it helps to capture and persist other logs on the activity chain even though they are originally not meant to be. But unfortunately from our test it didn't seem to be behaving towards that understanding. Then our question is, if we may ask - what are the exact additional in

Thanks for mentioning me. The feedback report (FB15507372) @xmollv filed is still under the investigation of the SwiftData team, and we don't have anything ready to share yet. Sorry for no help :-(. Best, —— Ziqiao Chen  Worldwide Developer Relations.

I've been using TM since Leopard, and I have tens of documents regularly open in a variety of applications, and I've never seen this error until I started using my own app. The app's role is an Editor, as it can modify and save files. Nonetheless, TextEdit, Pages, BBEdit, and countless other apps that I use don't have this problem.

Filed under FB21862078

Thanks for the post, this is extremely interesting to me for metal, what version of macOS are you using in what computer that can’t find the slice? I think, the error message Unable to find intelgpu_kbl_gt2r0 slice or a compatible one strongly suggests that it is related to the performance of the app on your Mac running macOS 26.2. This is a specific slice or compilation target for Metal shaders. This file contains precompiled Metal shader code for various graphics hardware configurations. The error means the system couldn't find a version of a shader that's compatible with your specific Intel graphics processor in the precompiled resources? The error message you're seeing is a strong indicator of a graphics-related issue likely impacting performance on your Intel Mac. The specific version of macOS and the applications you are using will determine the scope of the impact and the appropriate troubleshooting steps. I’m not an expert in metal nor I know enough to figure it out. May I ask you to submit a

This sounds very similar to the issue discussed in https://developer.apple.com/forums/thread/700648. 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 this thread. Bug Reporting: How and Why? has tips on creating your bug report.

Any updates on this? We are facing the very same issue in our app and couldn't find a workaround for this. This issue is preventing us from migrating to Xcode 26. We have also filed the FB21327884 feedback in December.