dSYMs imported with dynamic xcframeworks are not part of the dsyms output group

[aaronsky]

I've been investigating this for a little over a week, to try and understand the issue as fully as I can. Let me do my best to explain.

In my application I use PSPDFKit and Sentry. They are each provided as dynamic xcframeworks; containing a dSYMs path under each slice's directory and adjacent to the .framework, and a corresponding DebugSymbolsPath value in the xcframework Info.plist. As I understand it, this is a fairly typical arrangement when using -debug-symbols with xcodebuild -create-xcframework (especially when using Carthage as the builder).

In my Bazel project, these xcframeworks are imported using apple_dynamic_xcframework_import (from a repo created with http_archive, but I have confirmed this does not matter). When I go to build my application with the flags --apple_generate_dsym --output_groups=+dsyms, I see dSYMs from my ios_application, ios_extension, and ios_framework targets, but none from these apple_dynamic_xcframework_import targets. This appears to be called out explicitly in apple_xcframework_tests.bzl, though I am not versed enough in the ruleset to say how complex it would be to address.

Finally, this is reproducible in a rules_apple example – I tested with HelloWorldSwift importing Sentry and confirmed the dSYMs are not present in the outputs. Placing the xcframework in the same repo as the target does not change the behavior.

Any guidance on how to proceed would be appreciated!

[vakhidbetrakhmadov]

+1, running into this issue as well