Closed akug17 closed 3 years ago
it is due to using proguard this can be fixed using -keep class wseemann.media.{ ; } -keep class wseemann.media.FFmpegMediaMetadataRetriever { mNativeContext; }
in proguard-rules.pro file
it is due to using proguard this can be fixed using -keep class wseemann.media.{ ; } -keep class wseemann.media.FFmpegMediaMetadataRetriever { mNativeContext; }
in proguard-rules.pro file