This topic lists frequently asked questions about integrating and using hotpatch.
Android client
Apache HTTP-related crashes occur on RPC calls after hotpatch
Android 6.0 (Marshmallow) removed built-in Apache HTTP Client support. When hotpatch loads classes, importing the Apache HTTP Client as a JAR file or as a Gradle implementation/compile dependency causes a class-loading conflict that crashes the app.
To resolve this, avoid importing the Apache HTTP Client as a JAR file or Gradle dependency. For details, see Removal of Apache HTTP Client Support.
Hotpatch whitelisted inner classes
Hotpatch requires class references to use fully qualified names. Inner classes referenced without a fully qualified name fail to load at patch time.
Reference inner classes by their fully qualified name. To patch an inner class directly, decompile it into smali — the smali filename corresponds to the inner class name.
RPC calls
If your app throws an exception during an RPC resource call, the Security Guard component returns a result code that identifies the cause. Look up the result code in Security Guard result code description to identify and resolve the issue.