Tencent/tinker · error · TinkerRuntimeException
libName or context is null!
Error message
libName or context is null!
What it means
Error "libName or context is null!" thrown in Tencent/tinker.
Source
Thrown at tinker-android/tinker-android-lib-no-op/src/main/java/com/tencent/tinker/lib/tinker/TinkerApplicationHelper.java:84
public static HashMap<String, String> getPackageConfigs(ApplicationLike applicationLike) {
return null;
}
public static String getCurrentVersion(ApplicationLike applicationLike) {
return null;
}
public static void cleanPatch(ApplicationLike applicationLike) {
ShareTinkerLog.e(TAG, "[-] Ignore this invocation since I'm no-op version.");
}
public static void loadArmV7aLibrary(ApplicationLike applicationLike, String libName) {
System.loadLibrary(libName);
}
public static void loadArmLibrary(ApplicationLike applicationLike, String libName) {
if (libName == null || libName.isEmpty() || applicationLike == null) {
throw new TinkerRuntimeException("libName or context is null!");
}
System.loadLibrary(libName);
}
public static boolean loadLibraryFromTinker(ApplicationLike applicationLike, String relativePath, String libname) throws UnsatisfiedLinkError {
return false;
}
}
View on GitHub (pinned to 1b7ea02c23)
Solutions
- Ensure both the library name and a valid Context are passed to TinkerApplicationHelper.loadArmV7aLibrary/loadLibrary before calling.
- Obtain a non-null Context (e.g. application context) before invoking the helper.
When it happens
Trigger: Thrown at tinker-android/tinker-android-lib-no-op/src/main/java/com/tencent/tinker/lib/tinker/TinkerApplicationHelper.java:84 when the library encounters an invalid state.
Common situations: Thrown from TinkerApplicationHelper library loading when libName or context is null. Common when the helper is called before the application context is available.
AI-assisted analysis of Tencent/tinker@1b7ea02c23 (2026-08-14).
Data as JSON: /api/errors/d634068a1f791e05.
Report an issue: GitHub.