Sanju Naik

> Your prebuilt library is depending on a source-built library, but they're compiled with different compilers. This is not possible with Swift. You need to use the same version of...

@thii When I tried by manually removing `import GCDTimeManager` from .swiftinterface file, it did throw same duplicate symbol error as you shared, however same xcframework works fine on Xcode build...

I was trying this feature but it didn't work for me. I am able to produce a mergeable dynamic framework by passing `-make_mergeable` but merging it or reexporting in the...

> Ah yea I guess nothing today stops the rules from copying all dynamic frameworks in the dependency tree. You could add an ipa_post_processor to fix that but that's a...

Yeah when I inspected the binary using `otool -l /path/to/binary | grep REEXPORT`, it does show `cmd LC_REEXPORT_DYLIB` this means its loading the reexported binary. so this part is sorted....

The mergeable binary kept part of the `Frameworks` directory in the Bundle is of size 35 KB always [irrespective of module size] and mostly contains mergeable metadata I think, It...

Bumping this, Can someone please take a look at this? 🙏 Note - issue happens only when we add dependency as a `dynamic` framework & that too only when using...

Today when one of our jobs failed, I got this error log in the job. Does this help in any way to debug this issue? ``` ---8

> Also, I think the bazel-remote logs would be important to check here- are there any warnings or errors there? We are seeing these failures on our scheduled pipelines and...

Also we are still on version 2.3.9. Have we added any fixes related to Bazel 7 in the latest releases?