Wowza Community

Error while generating signed APK with Wowza Go-Coder SDK

I am using Wowza-Go-Coder SDK.

Facing issues after signing Android APK for release.

Here is log for crash after signed APK.

 JNI DETECTED ERROR IN APPLICATION: JNI SetIntField called with pending exception java.lang.NoSuchFieldError: no "I" field "mVerificationResult" in class "Lcom/wowza/gocoder/sdk/support/licensing/LicenseManager;" or its superclasses
   at void, java.lang.String, (:-2)
   at, java.lang.String) (:51)
   at void c.d.a.a.c.a.a(java.lang.String, java.lang.String) (:64)
   at void c.d.a.a.c.b.a.a(java.lang.String, java.lang.String) (:39)
   at c.d.a.a.b.c c.d.a.a.b.c.b(android.content.Context, java.lang.String) (:172)
   at void XXX.XXX.XXX.XXX.XXXActivity.onCreate(android.os.Bundle) (:147)
   at void (
   at void, android.os.Bundle) (
   at$ActivityClientRecord, android.content.Intent) (
   at void$ActivityClientRecord, android.content.Intent) (
   at void,$ActivityClientRecord, android.content.Intent) (
   at void$H.handleMessage(android.os.Message) (
   at void android.os.Handler.dispatchMessage(android.os.Message) (
   at void android.os.Looper.loop() (
   at void[]) (
   at java.lang.Object java.lang.reflect.Method.invoke!(java.lang.Object, java.lang.Object[]) (
   at void$ (
   at void[]) (

Did you get this fixed? It could be an error with how you entered the license key. Your license key and bundle identifier must match exactly as we have it in our SDK welcome email to you from Wowza.

Also, what Android OS are you using this with? What device?

Thanks for reply, Not yet fixed, Stuck with same issue from last week.

I have generated my licence key for my app bundle id and entered licence key same way shown in Sample code. And it working fine. But problem in generating Signed APK to publish on play store.

I am using minSdkVersion as 23(Marshmallow).

What Device? => I want to create general Signed APK that will run on all device and i am getting this problem while generating same.

Thank you for your responses @Bhavesh Desai. This error generates on the Android side. Some users have had success when skipping the minify option when building in android.

There are several posts on this error and issue on Stack Overflow with code samples on how you can correct this:

Advising turning ProGuard off is a bad practice. It is a library creators responsibility to ship correct ProGuard configuration inside AAR.

And no, error is not on the Android side. The error log above is pretty clear and must be delivered to developers team.

Sorry for late response on this. I did pass your feedback on to the SDK developer team that week you posted. Thank you @Alexander Fastovets.