Crash when add library ExoPlayer 2.17.0

[yohan002]

Environment:

• ExoMedia version: 4.3.0
• Device OS version: 10.0
• Device Manufacturer: Google

I recently create feature for video using ExoPlayer 2.17.0 , but in my older feature it suddenly crash using this library. Do you have any suggestion about this?, cuz im kinda struggling with it and don't know how to fix it, maybe this is a stupid question but if you can please help me.

[brianwernick]

The APIs being used by ExoMedia internally change frequently with ExoPlayer updates, because of this externally updating the ExoPlayer version is not recommended. I understand that you likely want some of the newer functionality added in more recent ExoPlayer versions (it's been quite some time since we last released ExoMedia), however I would recommend waiting a little longer for us to release the 5.0.0 version (we have 2 bugs left then testing).

With that said, it's possible the crash you are seeing can be worked around; if you post the logcat exception we may be able to find a short-term solution so that you aren't blocked until 5.0.0 is released.

As a head's up; ExoMedia 5.0.0 will be using the Media3 library for the ExoPlayer.

[brianwernick]

An update on this, we decided to publish a 5.0.0-beta01 release; please see the README for additional details

[yohan002]

okay thank you for replying my issue, really appreciate it

[yohan002]

java.lang.RuntimeException: Unable to start activity ComponentInfo{TranslateActivity}: android.view.InflateException: Binary XML file line #483 in layout/activity_translate: Binary XML file line #483 in layout/activity_translate: Error inflating class com.devbrackets.android.exomedia.ui.widget.VideoView

Caused by: android.view.InflateException: Binary XML file line #2 in layout/exomedia_default_exo_surface_video_view: Binary XML file line #2 in layout/exomedia_default_exo_surface_video_view: Error inflating class com.devbrackets.android.exomedia.core.video.exo.ExoSurfaceVideoView

here is the error message, but i actually have this issue solved by still using your library for my new feature.

[brianwernick]

Ah, glad that you were able to get it working.