Repository navigation
|
My app was flagged or rejected on Google Play for this. Dynamic code loading at runtime. Which guideline is this, how do I find it in my project, and how do I fix it before I resubmit? |
Replies: 1 comment
|
Guideline. Device and Network Abuse (Google Play) Severity in the playbook. high What triggers it. 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. What to search your code for. How to fix it. Ship all code in the package. Server side changes must be data, not executable code. The guard reports this as This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
Guideline. Device and Network Abuse (Google Play)
Severity in the playbook. high
What triggers it. 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.
What to search your code for.
DexClassLoader,PathClassLoader,loadDex,createPackageContextHow to fix it. Ship all code in the package. Server side changes must be data, not executable code.
The guard reports this as
ANDROID-DYNAMIC-CODE-LOADING. The full pattern is in data/rejection-patterns.json.This is a maintainer FAQ for app-store-compliance, an open…