Repository navigation
Share Android JNI version state and honor DEX capacity limits - #1345
Merged
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
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.
Android JNI callers could not read Build.VERSION, and valid explicit DEX classpaths hit unrelated 64 KiB JSON and 16-class limits before execution. Add an API 28 scalar version projection owned by the shared Dalvik Program/Runtime and sourced from the explicit Android property snapshot. JNI and DEX reads retain one field and heap identity; unsupported fields, writes and platform replacements remain explicit failures.
Keep the existing 64 KiB metadata limit while allowing the already documented 1 MiB DEX payload as hex, and separate the 16-image ceiling from a bounded 4096-class aggregate inventory. Preserve byte, memory, checksum and execution budgets. Synthetic fixtures exercise single/split classpaths, bounds, duplicate classes and malformed containers; no application inputs are included.
Validation:
This is a bounded version-state projection, not a boot framework, application context, class-loader or RegisterNatives implementation. Unknown application classes remain unsupported rather than being invented or assumed absent.