Encountered NoClassDefFoundError on Android platform about react-native-nami-sdk

[namidan]

@sleepym09

In your android/app/build.gradle you will need something like this in the dependencies section:

implementation "com.namiml:sdk-android:3.1.16"

(Please check the release notes for the version of the RN SDK and the native Android dependency it uses here: https://github.com/namiml/react-native-nami-sdk/wiki/Nami-SDK-Stable-Releases)

[sleepym09]

Hi @namidan, I add the dependencies and encounter another issue.
The android sdk looks like it depends on exoplayer 2.18.2, but my project already relies on exoplayer 2.12.
Here is the error log of build.

#1
Cannot access class 'ControlDispatcher'. Check your module classpath for missing or conflicting dependencies

#2
Type mismatch: inferred type is PlayerConnector.PlayerControlDispatcher but ControlDispatcher! was expected

There are some api changes in these two versions.

Can i force the exoplayer version to 2.12.0?, like this:
force "'com.google.android.exoplayer:exoplayer:2.12.0'"

[namidan]

@sleepym09

You can try that. Let me know how it goes.

[sleepym09]

I tried force the version by using force "com.google.android.exoplayer:exoplayer:2.12.0", but i got another error

Execution failed for AsmClassesTransform: /Users/zx/.gradle/caches/modules-2/files-2.1/com.squareup.moshi/moshi/1.13.0/da685586facab9eb5c4fb630ce248be14e7da21b/moshi-1.13.0.jar.
         > Record requires ASM8

I found the pom file of the nami android sdk, and it shows a dependency on moshi(1.3.0) and exoplayer(2.18.0).

This is the solution provided by moshi, But my application can't remove the firebase-perf dependency. Do you have any idea with this?
(By the way, force version is not a good idea, Once the nami sdk is upgraded with exoplayer, this can lead to some unknown errors.)

[namidan]

@sleepym09

Send us a note to [email protected]
and we can work through a solution.