Native-library page-size compatibility can affect operation on newer devices. Security SDKs belong in that review.
Evaluation approach
Check current Android requirements and supplier support matrices. Rebuilding the app does not automatically update old native binaries.
Application example
The protected release must launch and run critical checks under the relevant page-size conditions.
Limits and considerations
A compatibility failure is not a successful security detection.
What evidence should a supplier provide?
Ask for validation of the specific SDK version and target conditions. Repeat the test on your final package, including dependent native libraries.
Checks and decisions
- Read current requirements
- Inspect native binaries
- Test final artifacts
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.