-
Notifications
You must be signed in to change notification settings - Fork 6k
Closed
Labels
Description
[REQUIRED] Searched documentation and issues
Didn't find anything on the exoplayer.dev web site
[REQUIRED] Question
I see an IllegalArgumentException reported to Firebase/Crashlytics and wonder if I am supposed to do player.release() within a try/catch block ... ? This is with ExoPlayer 2.12, and the exception seems to be that the SimpleExoPlayer, in its release() method, calls streamVolumeManager.release(), and the Context object claims the manager's BroadcastReceiver isn't registered. I think this is completely under ExoPlayer's control, not mine.
Is this happening if one calls release() twice on a player object? (I don't think so).
Here's the stack trace:
android.app.LoadedApk.forgetReceiverDispatcher (LoadedApk.java:1499)
android.app.ContextImpl.unregisterReceiver (ContextImpl.java:1605)
android.content.ContextWrapper.unregisterReceiver (ContextWrapper.java:678)
com.google.android.exoplayer2.StreamVolumeManager.release (StreamVolumeManager.java:165)
com.google.android.exoplayer2.SimpleExoPlayer.release (SimpleExoPlayer.java:1706)
A full bug report captured from the device
Will be emailed.
Link to test content
N/A. The exception is seen in Firebase, but I have no further details about it.
Reactions are currently unavailable