History

tonihei 2fd4aac310 Do not require package visibility when connecting to a Media3 session

When we currently call SessionToken.createSessionToken with a legacy
token, we call the package manager to get the process UID. This
requires visiblity to the target package, which may not be available
unless the target runs a service known to the controller app.

However, when connecting to a Media3, this UID doesn't have to be
known, so we can move the call closer to where it's needed to
avoid the unncessary visibility check.

In addition, a legacy session may reply with unknown result code
to the session token request, which we should handle as well.

One of the constructor can be removed since it was only used from
a test.

PiperOrigin-RevId: 489917706

2022-11-22 10:08:08 +00:00

src

Do not require package visibility when connecting to a Media3 session

2022-11-22 10:08:08 +00:00

build.gradle

Load bitmaps for MediaMetadataCompat and handle the metadata updates.

2022-11-08 11:19:04 +00:00

README.md

Update to androidx.media3

2021-10-27 09:12:46 +01:00

README.md

Session test module

Tests cross-process use of the session module. To run the tests:

Prepare a device (either an emulator or a real device) to run the tests on.
Run ./gradlew :test-session-current:cAT