-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
player-accessed-on-wrong-thread #2966
Comments
can it be reproduced on master branch ? |
I can confirm this is replicable 6.0.0-alpha.6 at least, though in rare circumstances. I have only 1 Sentry report of this Redmi Note 10 Pro |
@kyle-ssg can you provide the callstack please? |
This issue will be fixed in 6.0.0-alpha.9 Let me know if you have other crash reposted by crashlytics, it is always interesting ! |
hey, this crash happens to me in release mode, mostly on android 13/14 devices. version: 6.2.0. stacktrace:
|
Bug
below is error reported on playstore console
Exception java.lang.IllegalStateException: Player is accessed on the wrong thread. See https://exoplayer.dev/issues/player-accessed-on-wrong-thread
at com.google.android.exoplayer2.SimpleExoPlayer.verifyApplicationThread (SimpleExoPlayer.java)
at com.google.android.exoplayer2.SimpleExoPlayer.getPlayWhenReady (SimpleExoPlayer.java)
at com.brentvatne.exoplayer.ReactExoplayerView.pausePlayback (ReactExoplayerView.java)
at com.brentvatne.exoplayer.ReactExoplayerView.onAudioFocusChange (ReactExoplayerView.java)
at android.media.AudioManager$ServiceEventHandlerDelegate$1.handleMessage (AudioManager.java:3017)
at android.os.Handler.dispatchMessage (Handler.java:106)
at android.os.Looper.loop (Looper.java:246)
at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run (MessageQueueThreadImpl.java)
at java.lang.Thread.run (Thread.java:923)
Platform
android
Which player are you experiencing the problem on:
Environment info
react-version 0.70.6
Library version: 5.2.1
The text was updated successfully, but these errors were encountered: