SDK / exoplayer

ParserException's constructor methods are deprecated.

#minor-release

PiperOrigin-RevId: 376150191

The docs on setLicenseUri say it's optional, and it has been since
https://github.com/google/ExoPlayer/commit/379cd8a04f0bf44a9422a08440223581b2657d74
(which should have changed this javadoc too)

#minor-release

PiperOrigin-RevId: 376139158

ParserException's constructor methods are deprecated.

#minor-release

PiperOrigin-RevId: 376127494

PiperOrigin-RevId: 376126959

Authentication sequence in RTSP:

- Server replies "Unauthorized" to our DESCRIBE request, and includes the
  necessary information (i.e. realm, digest nonce, etc) in WWW-Authenticate
  header

- After `RtspClient` receives the response, we

  - Parse the WWW-Authenticate header, stores the auth info. The info is saved
    for all further RTSP requests (that all need to carry authorization headers)
  - send the second DESCRIBE request with the Authorization header.

#minor-release

PiperOrigin-RevId: 376116302

PiperOrigin-RevId: 376005620

PiperOrigin-RevId: 375992816

PiperOrigin-RevId: 375992627

PiperOrigin-RevId: 375979170

PiperOrigin-RevId: 375919564

Issue: #8985
#minor-release
PiperOrigin-RevId: 375913914

The method openSocket in RtspMessageChannel does not actually open a socket.
The 'open' term refers more to opening the message channel.

#minor-release

PiperOrigin-RevId: 375908999

The callbacks received RTSP messages and RTSP sending errors are now invoked
directly from RtspMessageChannel's internal threads. It's up to the handler
implementation to decide which thread to handle the messages.

#minor-release

PiperOrigin-RevId: 375908282

Previously, RTSP interleaved binary data is posted onto the playback thread
for handling, the playback thread then adds the received data to a queue.
A loader thread will later dequeue the data and process it.

In this CL, the binary data is sent through a separate listener, on
RtspMessageChannel's RTSP receiving thread.

#minor-release

PiperOrigin-RevId: 375907609

Some RTSP servers will offer multiple WWW-Authenticate options. We wanted to
be able to pick them up.

#minor-release

PiperOrigin-RevId: 375907276

Currently acquireSession() fails with an NPE from
checkNotNull(exoMediaDrm). A follow-up change will result in exoMediaDrm
sometimes being non-null while prepareCount==0 (and in this case we
still want acquireSession() to fail).

preacquireSession() doesn't currently fail in a way the caller can
observe - the same NPE is thrown, but asynchronously and it doesn't
propagate out of the background thread. Throwing directly seems
preferable since it's a clear bug to be trying to preacquire sessions
from an unprepared/released manager.

PiperOrigin-RevId: 375906450

PiperOrigin-RevId: 375883879

PiperOrigin-RevId: 375830765

PiperOrigin-RevId: 375719035

PiperOrigin-RevId: 375705247

PiperOrigin-RevId: 375686596

#minor-release

PiperOrigin-RevId: 375674759

PiperOrigin-RevId: 375515685

PiperOrigin-RevId: 375514509

PiperOrigin-RevId: 375484765

Without this the Cue isn't deeply immutable, which can be a bit
surprising.

PiperOrigin-RevId: 375477571

This reduces the null-checking required in a follow-up change.

PiperOrigin-RevId: 375468504

#minor-release

PiperOrigin-RevId: 375436117

#minor-release

PiperOrigin-RevId: 375435339

PiperOrigin-RevId: 375133184

#minor-release

PiperOrigin-RevId: 375097412

Unlike Assertions, the introduced method cannot be disabled and throws
a ParserException instead. This method is meant to replace regular
assertions (which throw RuntimeExceptions) which check input in the
parsing code.

PiperOrigin-RevId: 375085160

Its absence seems to have caused
https://github.com/google/ExoPlayer/issues/8969.

#minor-release

PiperOrigin-RevId: 375058222

PiperOrigin-RevId: 375054051

We need to avoid reading and skipping into preload chunks as they
may need to be discarded. The current code iterates over all chunks,
but this can be simplified by just checking the last chunk knowing
that the preload chunk must always be the last one.

As a result, we avoid calling getFirstSampleIndex on all chunks. This
is a bug since the method is not allowed to be called for chunks
that have been spliced in. This still leaves the smaller issue of
potentially calling this method for spliced-in preload chunks, which
will be solved separately.

Issue: #8937

#minor-release

PiperOrigin-RevId: 375053638

Tweak the way directories are passed

PiperOrigin-RevId: 374912886

PiperOrigin-RevId: 374885599

PiperOrigin-RevId: 374880929

PiperOrigin-RevId: 374874272

Preload chunks may still need to be discarded. However, we don't
currently support discarding spliced-in chunks. Thus, we need to
avoid loadng a preload chunk that needs to be spliced-in.

Issue: #8937

#minor-release

PiperOrigin-RevId: 374851661