-
Notifications
You must be signed in to change notification settings - Fork 6k
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
MPD.Location uri in relative format can't be resolved. #9939
Comments
@ojw28 /** |
Our plan is to solve the problem in |
#minor-release Issue: google/ExoPlayer#9939 PiperOrigin-RevId: 426394339
#minor-release Issue: #9939 PiperOrigin-RevId: 426394339
Thanks that's even better. Resolve the location immediately after it has been parsed. |
I also encountered this problem, have you solved it? |
#minor-release Issue: #9939 PiperOrigin-RevId: 426394339
#minor-release Issue: google/ExoPlayer#9939 PiperOrigin-RevId: 426394339
We have a DASH live stream, it's MPD manifest Location url is a relative url.
../another_path/manifest.mpd?device_profile=DASH_STB_NGRSSP_LIVE_SD
When using 2.16.1 demo application to play this stream, the following error has been throw by exoplayer.
2022-02-04 11:52:53.239 17085-17085/com.google.android.exoplayer2.demo E/EventLogger: internalError [eventTime=2.02, mediaPos=27.76, window=0, loadError
com.google.android.exoplayer2.upstream.FileDataSource$FileDataSourceException: uri has query and/or fragment, which are not supported. Did you call Uri.parse() on a string containing '?' or '#'? Use Uri.fromFile(new File(path)) to avoid this.
The expected behaviour
Exoplayer could resolve the relative path MPD.Location and use it for manifest refresh.
The actual behaviour
Exoplayer detect the MPD.Location as a local file path.
ExoPlayer version number
2.16.1
The text was updated successfully, but these errors were encountered: