SecurityException: Session rejected the connection request.

[diego-escribano]

Version

Media3 1.4.0

More version details

No response

Devices that reproduce the issue

All versions of Android, but mostly Android 13 and 14.

15% Elink - Harman
12% Skyth-tek - Windriver
11% Hena - FIH Foxconn
10% AoGo
9% Cubot - FIH Foxconn
5% Hena - FIH Foxconn
4% Hena - FIH Foxconn
3% Worldchip - FIH Foxconn
2% Elink - FIH Foxconn
2% Pegatron
2% Deejoy - FIH Foxconn
2% BND - Windriver
1% Deejoy - FIH Foxconn
1% Elink - FIH Foxconn
1% Elink - Harman
1% Elink - FIH Foxconn
1% Deejoy - FIH Foxconn
1% Blackview - Windriver
1% BND - Windriver
1% Symphony Teleca
1% BND - Windriver
1% Along - Windriver
<1% Deejoy - FIH Foxconn
<1% Along - Windriver
<1% Hena - Harman
<1% Deejoy - FIH Foxconn
<1% Incar - FIH Foxconn
<1% Elink - FIH Foxconn
<1% Huawei
<1% Samsung
<1% Deejoy - FIH Foxconn
<1% Peicheng
<1% Transsion
<1% Deejoy - Windriver
<1% Hena - FIH Foxconn
<1% Deejoy - FIH Foxconn
<1% Rebecco
<1% Along - Windriver
<1% SkyDevices - FIH Foxconn
<1% Hena - FIH Foxconn
<1% BND - Windriver
<1% Elink - FIH Foxconn
<1% Deejoy - FIH Foxconn

Devices that do not reproduce the issue

No response

Reproducible in the demo app?

Not tested

Reproduction steps

We cannot reproduce it.

Expected result

The app does not crash

Actual result

App crashes

Media

Context: Our app can play on demand audio and live stream on the Android device
Problem: Every since we migrated to Media3 we have a consisent crash that happens only when the app is on the background, but only on certain devices, mainly low cost kids tablets. We cannot reproduce the crash.

I have attached the Playback Service, the MediaPlayerProvider where we create the SessionToken and the crash logs.

MediaPlayerProvider.txt

PlaybackService.txt

crash_report.txt

Bug Report

• You will email the zip file produced by adb bugreport to android-media-github@google.com after filing this issue.

[tonihei]

Thanks for reporting the issue!

The set of affected devices is a very specific and slightly unusual subset of devices, so it's likely related to something that is happening on these devices.

The main reasons why the connection can be rejected are:

• The session explicitly rejects the connection. This is not the case here based on your provided PlaybackService.
• The session is already released by the time the controller attempts its connection. This may be not be applicable because it looks like the controller connection happens inside Service.onCreate(), attempting to create a controller connecting to the session running in the same service.
• The request may be malformed. This sounds also unlikely given it only happens on some devices.
• The service binding from the controller is not possible or was rejected by the system. This sounds like the most likely explanation. You mentioned it happens mostly when the app is in the background, so I wonder if these devices impose some additional restrictions on service bindings that are not present on most other devices.

Given the controller in MediaPlayerProvider is connecting to a session that is just being created, is there a way you can use session.getToken() to create this MediaController instead of creating a SessionToken with a ComponentName? This would avoid the service binding path entirely and could confirm the hypothesis above.

Independent of that, a MediaController.Builder.buildAsync() call is allowed to fail in general. So instead of accessing it blindly and crashing the app if the ListenableFuture failed to resolve, it's generally better to handle the error case more gracefully (that is, controllerFuture.await() may throw and there should be code to handle this).