Chirag Ramani

cc: @aciidb0mb3r

Hey @erikolofsson, I see that you have a PR that talks about Parallel Incremental Builds (https://github.com/apple/swift-llbuild/pull/832). Can you confirm if it's related to the above issue?

Hey @erikolofsson, can you share the setup that you are using to run this in Xcode? I will be interested in debugging the issue that you described. cc: @dmbryson if...

@dmbryson any updates/workarounds related to this issue?

Does it work when you try this Flipper implementation instead - https://github.com/chiragramani/FlipperLite or https://github.com/chiragramani/SwiftFlipper?

> @chiragramani Do you have time to finish this PR up? If not, I could look at finishing any remaining work. Thank you! Hey, I'm back from medical leave and...

Looks like this code path is being executed, https://github.com/bazelbuild/rules_apple/blob/master/apple/internal/outputs.bzl#L51, where the action declaration makes use of the bundle name and hence the conflict. (since the bundle names are the same)....

> Does this change work for you too @chiragramani? We have a slightly different implementation, but I think the root cause you highlighted would also fix our case. I will...

Thanks for reporting. I can repro this issue. I think codesigning these dylibs will fix this issue. (Vanilla Xcode projects do codesign these dylibs when building for device) ``` '/private/var/containers/****/AddressSanitizerApp.app/Frameworks/libclang_rt.asan_ios_dynamic.dylib'...

my understanding might not be fully correct, so created this issue with a repro https://github.com/apple/swift/issues/67212 to understand this better as it's not something specific to rules_xcodeproj.