Brentley Jones

Since this file is created based on this check: https://github.com/buildbuddy-io/rules_xcodeproj/blob/main/tools/generator/src/Generator/CreateFilesAndGroups.swift#L600, it would seem there is a bug here, or calling it: https://github.com/buildbuddy-io/rules_xcodeproj/blob/7ee46ec29bb4365f2c81525200a078b80bf5ca4a/tools/generator/src/Generator/AddBazelDependenciesTarget.swift#L5-L19

@thii Have you run into this since?

I'm going to close this for now then.

Ahh, yeah, not sure we can do anything about that. Hopefully people aren't switching modes in the day to day (cc: @erikkerber).

Does this still fail in Xcode 14? Also, which version of swift-composable-architecture are you using? Since this is a Swift compiler crash 😬 I will need a full reproducer instead...

I'm going to close this for now. If you can provide self-contained reproduction project then I can reopen this and debug it. Recent releases, and even `main`, have improved SwiftUI...

I don't believe this should block 1.0.

Is the module in question a sibling module to the test target? That was one of the things supposedly fixed by [this overlay](https://github.com/buildbuddy-io/rules_xcodeproj/blob/f201b91014dbc2090cb383f26aa21726a93d9373/xcodeproj/internal/bazel_integration_files/bazel_build.sh#L145-L149), as it's supposed to map `/Users/me/Library/Developer/Xcode/DerivedData/ProjectName-gycnzekyazbslbeaqlxvvzaelfei/Index/Build/Products/bazel-out/` to...

Got a lead offline. Believe that the overlay only starts to work once the main project is built, since the full directory doesn't exist and the fallback behavior kicks in.

I'm not sure I can fix this for BwB, though BwBvP might be able to: - The compiler is still looking in `$BUILD_DIR`, even though we remapped it, because the...