I upgraded my two Macs to Xcode 26.0 RC today and now get the following error at the very end of the tuist cache command:
Creating XCFramework for …
Storing binaries to speed up workflows
Error parsing the log: Unexpected attachment identifier com.apple.dt.ActivityLogSectionAttachment.BuildOperationMetrics
This error occurs in several of my projects, but not all. I haven’t been able to reproduce it in a minimal example yet. Before I start dismantling projects to find the root cause, any suggestions to help narrow down the issue would be appreciated. Thank you!
This error is most likely coming from the XCLogParser that we depend on.
I believe the only place where we use it as part of tuist cache is here to gather the build time metrics.
Ideally, we add support for this new attachment identifier in XCLogParser. We could also, temporarily, silently fail on parsing the .xcactivitylog as part of tuist cache since it’s there only for analytics purposes. But if we do that, then errors like this will go unnoticed, making those metrics way less reliable.
If you could produce a reproducible sample, that would help a ton, so that we can add support for the new attachment in XCActivityLogParser (_or_ feel free to add such support yourself of course )
Thank you for your reply, @marekfort! I will try to reproduce the issue in a sample project. I’m currently preparing my apps for the new iOS release but should have time to work on this next week. I’ll keep you updated.
Thanks @FelixLisczyk! We’re certainly committed to fixing this, but without a sample, it’s difficult to add support for these things. Keep us in the loop
I’m getting the same with 26.0 RC, Tuist 4.71.0. I think being able to disable this in the short-term would be great. I can see if I can come up with a minimally reproducible sample as well.
I created a sample project from one of my app templates. Reproducing the issue was a bit tricky: it only occurred after I added a framework target and my custom Tuist plugin to the project.
You should be able to see the error by cloning the following repository and running:
tuist install && tuist cache
Please let me know if you have any questions or cannot reproduce the error.