Fix JNI error

Replace CallStaticVoidMethod with CallStaticObjectMethod.

Bug: 192290163
Test: build & boot

Signed-off-by: Taesu Lee <taesu82.lee@samsung.com>

(cherry picked from commit 07e04b69a5)
Merged-In: I02980e58bfd9bb334f1aa50c9e51a8ce4ae5e059
Change-Id: I1ae548e31722675b90be5447aa84e8f5e207cc98
This commit is contained in:
Taesu Lee
2021-06-29 14:15:43 +09:00
committed by Orion Hodson
parent 91c4f415e3
commit c57fb648e4

View File

@@ -1620,7 +1620,7 @@ static void SpecializeCommon(JNIEnv* env, uid_t uid, gid_t gid, jintArray gids,
if (is_system_server) {
// Prefetch the classloader for the system server. This is done early to
// allow a tie-down of the proper system server selinux domain.
env->CallStaticVoidMethod(gZygoteInitClass, gGetOrCreateSystemServerClassLoader);
env->CallStaticObjectMethod(gZygoteInitClass, gGetOrCreateSystemServerClassLoader);
if (env->ExceptionCheck()) {
// Be robust here. The Java code will attempt to create the classloader
// at a later point (but may not have rights to use AoT artifacts).