David Harris

Might be best to just consider Linux compatibility when addressing https://github.com/tuist/xcodeproj/issues/369 and that could replace some of the problematic code. @CognitiveDisson I put up a draft PR at https://github.com/tuist/xcodeproj/pull/370 if...

I looked into this a bit. It's pretty doable for the current state, and given that SPM only supports Analytics and Crashes right now in general and there are already...

I'm having a look at fixing this, doesn't seem super involved, but the one detail I could use some help on how relative paths are built here relative to the...

Hey! I haven't really been able to look into this as I've had to cover mostly internal projects. Especially given Dependencies.swift work this is probably necessary, and I think Xcode...

> Please pay attention to the PR title as it will end up in the changelog, I have changed it 🚀 Been away from contributing for a bit, was trying...

Looks like the "breaking" change here is that these are targets that are not passing any explicit target device to build to, and then it's failing because it can't infer...

Picking this back up. The issue is that the framework targets included are buildable for Mac Catalyst, so when the destination isn't specified with `tuist build` it ends up choosing...

`tuist build` is going to need logic to take in some additional parameters around targeted devices, but it seems to be different than what `tuist test` has coded currently.

Should be updated now, since these tests pass device now it gets handled appropriately with no changes it seems

> The last one, TestTargetID is a target reference that is local to each project so that wouldn't support setting cross project targets. From your description however, seems like only...