Skip to content
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

JNI install task should always takes place if NDK build enabled #323

Merged
merged 1 commit into from
Oct 13, 2020

Conversation

fractalwrench
Copy link
Contributor

Goal

In v4 of the plugin the BugsnagInstallJniLibsTask always ran if the NDK build was active, as users may need to copy bugsnag's SO files to their build directory so that they can link against them. v5 introduced a bug where this was gated behind the uploadNdkMappings flag - this changeset corrects this change so that the user's project is always able to link against the

Testing

Manually verified in an example app that the task runs regardless of the value of uploadNdkMappings. E2E tests were not considered practical as there aren't any existing steps to address this, and the functionality of copying SO files will soon be superseded by improvements to AGP's support for external native dependencies (PLAT-3171)

@fractalwrench fractalwrench changed the base branch from master to next October 13, 2020 09:25
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.

None yet

2 participants