CODEWITHSUNDEEP
androidmonoxamarin.androidmonodevelopxamarin
Surya2089
Surya2089

Reputation: 269

Error: JNI ERROR (app bug): accessed stale global reference

I am getting this error JNI ERROR (app bug): accessed stale global reference When I run my app in Android OS v4, But when I run the same application in Android v2.3 I don't get this error.

This error occurs at the point where I call AsyncTask class, where I pass a string array as argument

Could Anyone Help me??

Upvotes: 15

Views: 17400

Answers (4)

Knight Forked
Knight Forked

Reputation: 1619

This applies to kotlin:

To add to what @krys has already mentioned, make sure that signatures on Kotlin side match exactly what you have in the JNI code. Even a simple Void (avoid explicit Void at the end of function signatures that return void on the JNI side) signature at the end of kotlin reference may fail and would make your debugging extremely frustrating.

Upvotes: 0

Crossle Song
Crossle Song

Reputation: 10174

JNI Local Reference Changes in ICS

Upvotes: 1

Thuan Bui
Thuan Bui

Reputation: 41

This error occurs when you call a method with an incorrect parameter type.

Addition, in this case you may be register the native method on Java code different from the native code. The difference can be you declare more or less parameters between the Java code and native code.

Upvotes: 3

Krys Jurgowski
Krys Jurgowski

Reputation: 2911

This error occurs when you call a method with an incorrect parameter type.

Make sure your method signature matches exactly what you are passing. For a string array:

jmethodID mid = env->GetMethodID(cls, methodName, "([Ljava/lang/String;)V");

If you are creating it yourself, it would look something like this:

jclass stringCls = env->FindClass("java/lang/String");
jobjectArray mStringArray = env->NewObjectArray( mSize, stringCls, NULL);

In your specific case, you are most likely not seeing the crash on Android 2.3 because you are calling AsyncTask.execute() which wasn't available until API 11 (Android 3.0) and your jmethodID is null. (It's a good idea to always check jclass and jmethodID for null after getting them)

Upvotes: 15

Related Questions