Call to UnityPlayer.UnitySendMessage from native code crashes in Android API 16

Unity Engine
,
1

Greetings

I have a problem where calls from native to UnityPlayer.UnitySendMessage crashes on devices with android 4.1.2 (API 16). It produces a NoClassDefFoundError: com.unity3d.player.UnityPlayer. It doesn’t crash on devices with older APIs and the method gets called in Unity.

The code also compiles with no errors.

Is this a known issue with android 4.1.2? Do I need to change something in the project?

Edit:
Forgot to add, I’m using Unity Pro version 3.5.2f2

2

Always make sure you run the latest unity version - in this case Unity 3.5.7. We constantly fix/workaround things which breaks due to new devices and/or new os releases made by google.

3

Is there any way to fix this problem without upgrading? Our app is currently live and using asset bundles, and upgrading the unity version would break a lot of stuff.

If we knew what was causing it maybe we could fix it with a hack.

4

Honestly I don’t recognize your particular problem which leads me to believe it is either an existing bug in 3.5.7 or it has been fixed as a side effect of something else. My suggestion; try to create a small repro case of the issue. See if it reproduce on both 3.5.2 and 3.5.7. Then file a bug report with unity, attaching the repro.

When you have done that, post your case number here so I can take a look at what is going on.

5

After reinstalling the the app, it now crashes with these messages instead:
Adreno200-EGL(25846): <qeglDrvAPI_eglGetConfigAttrib:481>: EGL_BAD_ATTRIBUTE
Adreno200-EGL(25846): <qeglDrvAPI_eglGetConfigAttrib:481>: EGL_BAD_ATTRIBUTE
Adreno200-EGL(25846): <qeglDrvAPI_eglGetConfigAttrib:481>: EGL_BAD_ATTRIBUTE
Adreno200-ES20(25846): <qgl2DrvAPI_glDeleteShader:191>: GL_INVALID_VALUE

Doing a clean install brings back the
java.lang.UnsatisfiedLinkError: Native method not found: com.unity3d.player.UnityPlayer.UnitySendMessage
error. Wierd.

I can’t seem to reproduce it in a small project. If all else fails, I’ll upgrade to 3.5.7 and just deal with what happens then. But if someone can tell me “Yeah, we fixed that in 3.5.7” then that would make it much easier on me.

And sorry for any confusion, but yeah, I’m the TS. I forgot I had registered this account way back and made a new one.