Skip to content
Toggle navigation
P
Projects
G
Groups
S
Snippets
Help
SDK
/
exoplayer
This project
Loading...
Sign in
Toggle navigation
Go to a project
Project
Repository
Issues
0
Merge Requests
0
Pipelines
Wiki
Snippets
Settings
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Commit
d6a95482
authored
Jun 23, 2021
by
aquilescanta
Committed by
Oliver Woodman
Jun 30, 2021
Browse files
Options
_('Browse Files')
Download
Email Patches
Plain Diff
Add release notes for PlaybackException-related changes
PiperOrigin-RevId: 381021014
parent
116e50f3
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
14 additions
and
0 deletions
RELEASENOTES.md
RELEASENOTES.md
View file @
d6a95482
...
...
@@ -5,6 +5,20 @@
*
Core Library:
*
Add
`needsReconfiguration`
API to the
`MediaCodecAdapter`
interface.
*
Add
`fastForward`
and
`rewind`
methods to
`Player`
.
*
Make
`Player`
depend on the new
`PlaybackException`
class instead of
`ExoPlaybackException`
:
*
`Player.getPlayerError`
now returns a
`PlaybackException`
.
*
`Player.Listener.onPlayerError`
now receives a
`PlaybackException`
.
*
Add a new listener method
`Player.Listener.onPlayerErrorChanged`
,
which is equivalent to
`onPlayerError`
except that it is also called
when the player error becomes
`null`
.
*
`Player`
implementations like
`ExoPlayer`
may use
`PlaybackException`
subclasses (like
`ExoPlaybackException`
), so
users can downcast the
`PlaybackException`
instance to obtain
implementation-specific fields (like
`ExoPlaybackException.rendererIndex`
).
*
`PlaybackException`
introduces an
`errorCode`
which identifies the
cause of the failure in order to simplify error handling.
*
Remove deprecated symbols:
*
Remove
`Player.getPlaybackError`
. Use
`Player.getPlayerError`
instead.
*
Remove
`Player.getCurrentTag`
. Use
`Player.getCurrentMediaItem`
and
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment