Repository navigation
|
How can a team catch Dynamic code loading at runtime automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rn 'DexClassLoader\|PathClassLoader\|loadDex\|createPackageContext' --include='*.kt' --include='*.java' .Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. DexClassLoader, PathClassLoader from a downloaded file, or downloading and executing code at runtime. For apps targeting API 37, every native library loaded with System.load() must be read-only or the system throws UnsatisfiedLinkError. The fix. Ship all code in the package. Server side changes must be data, not executable code. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
ANDROID-DYNAMIC-CODE-LOADINGwith a coverage line and a proper exit code.What the hit means. DexClassLoader, PathClassLoader from a downloaded file, or downloading and executing code at runtime. For apps targeting API 37, every native library loaded with System.load() must be re…