Thi Doan
Thi Doan
Bazel strips the built target's binary (built by Bazel), where this is for the Swift standard libraries and imported dynamic frameworks. And it looks like it doesn't strip Swift symbols...
Update: Implemented the default features support.
I'll try to get back to this and finish it soon, hopefully within next week.
There was a discussion about this in the past, `expand_make_variables` is documented as deprecated but there's no replacement yet. Can we support both? https://github.com/bazelbuild/bazel/issues/5859
Related: https://github.com/bazelbuild/rules_apple/pull/1396 Maybe revert that first?
https://github.com/bazelbuild/rules_apple/pull/1619
Are you generating dSYMs for your debug builds?
Is there any reason for that? If you request dSYMs, the aspect build during the project generation would take almost as long as the normal build.
We can revert that if anyone has a use-case for it.
We're hitting this as well. Once in awhile the build failed which made developers have doubts about Bazel's reproducibility. It looks like the validation only checks if the `.xcassets` directory...