-
Notifications
You must be signed in to change notification settings - Fork 279
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Loading status checks…
Propagate
AppleFrameworkImportInfo
from iOS extensions (#2633)
I am attempting to cover for a seemingly specific edge-case. Maybe misguided, but it can be validated with the tests on this PR. Here goes: Given an `ios_extension` that depends on an `apple_dynamic_xcframework_import` (I assume this also affects `apple_dynamic_framework_import` but have not tested it), and given an `ios_application` that bundles this extension but **does not depend on the imported framework**, then the Mach-O load command is added to the extension binary, but the framework is not bundled in `$BUNDLE_ROOT/Frameworks`. This causes the extension to crash at launch. [Slack thread for additional context.](https://bazelbuild.slack.com/archives/CD3QY5C2X/p1737049459227449) Based on my read of the code in `ios_rules.bzl`, this feels like an oversight, given that [this line](https://github.com/bazelbuild/rules_apple/blob/master/apple/internal/ios_rules.bzl#L361) takes `ctx.attr.extensions` and attempts to load `AppleFrameworkImportInfo` providers on [this line](https://github.com/bazelbuild/rules_apple/blob/master/apple/internal/partials/framework_import.bzl#L63-L68), but without this PR that doesn't seem as though it will never happen based on [this line](https://github.com/bazelbuild/rules_apple/blob/master/apple/internal/ios_rules.bzl#L1398-L1415). Happy to discuss if my interpretation is off-base!
Showing
3 changed files
with
152 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters