Repository navigation
fix(bindings): validate native packages and Java requirements - #1103
Merged
Merged
Conversation
andiwand
force-pushed
the
review/84-jni-test-concision
branch
from
October 5, 2026 20:45
2c45eea to
702b59f
Compare
andiwand
force-pushed
the
review/85-android-native-packaging
branch
from
October 5, 2026 20:49
55a9d20 to
70fe43e
Compare
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.
🤖 Generated with Claude Code
Android's
checkNativenow requires nonemptylibodr_jni.soandlibc++_shared.sofiles in every supplied ABI directory. Previously an empty directory passed, allowing a broken AAR to reach consumers. Prebuilt single-ABI trees remain supported for emulator builds. JNI jar configuration also requires JDK 17, matching--release 17.Validation: the real Gradle task rejects an empty ABI directory, a missing runtime and an empty runtime, and accepts a complete nonempty pair. CMake configures successfully with the installed JDK. This checks package contents, not ELF validity or an Android runtime.