-
-
Notifications
You must be signed in to change notification settings - Fork 37
Fix package exclusion by moving App Clip target to top level #84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
trentrand
wants to merge
4
commits into
bndkt:main
Choose a base branch
from
trentrand:fix-package-exclusion
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
4a62048
Fix package exclusion with sibling targets and xcconfig flag stripping
trentrand 43715ec
Add documentation about `excludedPackages` option
trentrand c7b44cc
Remove post_install xcconfig stripping (unnecessary after target un-n…
trentrand 11ccf63
Append target to end of Podfile without anchor
trentrand File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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 hidden or 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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clip_commandnow callscliPlugin.run(..., []), which preventscliPlugin.tsfrom deleting excluded packages from the autolinking config (it deletes keys based on theexcludearray). This looks like a regression:excludedPackageswill no longer be excluded fromuse_native_modules!resolution for the App Clip target. Pass the actual excluded package list through to the CLI plugin again (and ensure it stays in sync withexcludedPackages).Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Passing the exclude list to cliPlugin is what originally caused #79 — when excluded from
use_native_modules!, Codegen does not generate spec headers for those packages, but the pod source files still #import them (e.g. NativeNfcManagerSpec.h), causing a compile failure under New Architecture. The[]is intentional: we keep packages in the autolinking config so Codegen generates their specs, then strip them from the linker inpost_install. This is the two-pronged approach described in the PR.