fix: regenerate Android autolinking in warmed worktrees - #455
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Warming an Android worktree copies autolinking metadata that names native dependencies in the original checkout. When dependency checksums are unchanged, Gradle reuses those paths and can build against the original checkout's generated state.
Solution
Exclude
android/build/generated/autolinkingfrom warm copies, including nested apps, so Gradle regenerates paths for the destination. Other generated output and existing destination entries remain intact.Test plan
Regression tests fail on main and pass with the fix for root and nested apps, preserving sibling output and existing destination caches. The real Gradle autolinking task regenerated the checkout root and native dependency path inside the new worktree. All repository checks passed: 3,605 unit tests, 66 end-to-end tests, formatting, lint, build, types, and knip.
Fixes #445