fix: make android library evaluation depends on expo #141
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.
Summary
This PR fixes an edge case where in an expo project, if the consumer android library has the name starting before
expo
then it gets evaluated afterexpo
, hence the expo libraries are not linked with the android library. To fix that behavior, we add a dependency onexpo
evaluation and then the consumer android library gets evaluated. This ensures that the expo libraries will be present and linked correctly with the android library when it is evaluated.Issue fixed: #135
Test plan
a | b | c | d | e
for eg,:brownlibrary | :expobrownfieldlibrary
e
, for eg::mylibrary
Screen.Recording.2025-09-20.at.4.35.22.PM.mov