Skip to content

Conversation

@tomekzaw
Copy link
Member

@tomekzaw tomekzaw commented Jul 14, 2025

Summary

I managed to reproduce this linking error only once but I decided to submit this PR anyway.

Based on:

Test plan

@tomekzaw tomekzaw requested review from piaskowyk and tjzel July 14, 2025 10:44
@tomekzaw tomekzaw marked this pull request as draft July 14, 2025 10:51
@tomekzaw tomekzaw force-pushed the @tomekzaw/android-linking-error branch from b9c26b8 to 4dac618 Compare July 14, 2025 10:55
Copy link
Member

@piaskowyk piaskowyk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👏

@tomekzaw
Copy link
Member Author

Together with @lukmccall we noticed that this solution has one major drawback of actually building the native code for each Android architecture in both debug and release modes (8 combinations in total) the which can take several minutes and can be a bit cumbersome as developers expect Gradle sync to take as little time as possible (seconds), not to forget about React Native core team efforts on that matter.

Closing in favor of #7866.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants