AttachmentMediaActivity crashes when opening .m4a files: ClassCastException between com.google.android.exoplayer2 and androidx.media3

[nabeelismail30]

Describe the bug
When opening an .m4a attachment in the Stream Chat SDK’s AttachmentMediaActivity, the app crashes with an InflateException and a ClassCastException.
The crash occurs because androidx.media3.ui.PlayerView attempts to cast com.google.android.exoplayer2.ui.AspectRatioFrameLayout (from the old ExoPlayer package) to androidx.media3.ui.AspectRatioFrameLayout.
This indicates a dependency conflict between the legacy ExoPlayer (com.google.android.exoplayer2) and Media3 (androidx.media3) libraries used internally by the SDK.

Caused by: java.lang.ClassCastException: com.google.android.exoplayer2.ui.AspectRatioFrameLayout cannot be cast to androidx.media3.ui.AspectRatioFrameLayout

SDK version

• "6.24.0" - Android SDK

To Reproduce
Steps to reproduce the behavior:

1. Launch the chat and open a message with an .m4a audio attachment or upload any m4a file in the chat message.
2. Tap on the audio to open the gallery/media viewer (AttachmentMediaActivity).
3. The app crashes during layout inflation of stream_ui_activity_attachment_media.

Expected behavior
The media viewer should open and play the .m4a audio file normally without crashing.

Device:
Vendor and model: Samsung Galaxy A52, Google Pixel 8a
Android version: Android 14, Android 15

[VelikovPetar]

Hi @nabeelismail30 ,

Thanks for the report, we will investigate this.
Can you confirm that this happens also for different types of video formats? Based on the exception I would expect that this happens for any video file, not just .m4a.

Best regards,
Petar

[nabeelismail30]

hey @VelikovPetar,
it is happening for .m4a audio files and other formats seems working fine for now on I am not able to reproduce it for other formats

yes, you're right, ClassCastException explaining it all.

Best regards,
Nabeel

[nabeelismail30]

hey @VelikovPetar,
Update any on this?

Best regards,
Nabeel

[VelikovPetar]

Hi @nabeelismail30,

Apologies, we didn't have the time to work on this issue. I will try to work on it this week, and possibly include it in the upcoming release.

Regards,
Petar