-
-
Notifications
You must be signed in to change notification settings - Fork 613
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
Exception from ExoPlayer #29
Comments
The only thing I can think of is that it might not really be an mp3 file. Maybe you can try opening the file on your desktop or laptop using software that can show you the codec info. Once I know what format it is, I can try to enable that in ExoPlayer. |
Good catch. It was a wrong codec. I still need to be able to catch such exceptions and, ideally, prevent the player from crashing. Currently we cannot pre-validate every file that we play. Skipping files that ExoPlayer cannot play would be a good enough solution. |
After looking through the plugin code, it appears that there is no way out of AudioPlaybackState.connecting. No other method can be called from this state, making it a dead-end if a player is stuck in this state. |
I'll use #31 to track the exception reporting code. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs, or use StackOverflow if you need help with just_audio. |
I ran into one mp3 file which causes the following exception, when playing on Android:
The file actually starts playing and sounds normal. Unfortunately, the audio player becomes unresponsive - all further calls (setting a new file/URL) fail. The audio player appears to be permanently stuck in the .connecting state.
The same file plays with no problems on iPhone. I also ran a check to see if this is a valid mp3 file, and it is.
Any ideas why a file would play normal on iPhone (and in web browsers), but fail on Android?
Is there a way to catch such exceptions?
The text was updated successfully, but these errors were encountered: