IssueTracker

From b/324583507#comment10, this is because CronetDataSource compares their request object to the request object in the callback.

    public synchronized void onResponseStarted(UrlRequest request, UrlResponseInfo info) {
      if (request != currentUrlRequest) {
        return;
      }
      responseInfo = info;
      operation.open();
    }

The HttpEngineNativeProvider wraps the request in order to translate from org.chromium.net to android.net.http and vice versa. Hence, the equality check in exoplayer's callbacks fail because exoplayer's request is wrapped version of the request in the callback, leading to the timeout.

From issue 324583507 on 15/03/2024:

Project: chromium/src
Branch: main

commit 7f7c0e994c2234cfe6c78aaed156bac633f95bc6
Author: Chidera Olibie colibie@google.com
Date: Fri Mar 15 11:26:07 2024

[Cronet] Modify request/stream's equality check

While our documentation does not guarantee that the request/stream
passed to the callbacks will be the same as the one created by the
user, our users have assumed this is the case. Eg
https://github.com/google/ExoPlayer/blob/release-v2/extensions/cronet/src/main/java/com/google/android/exoplayer2/ext/cronet/CronetDataSource.java
compares the request objects in their callbacks.

This cl changes the equals method to, in addition to the original
equality check, consider two wrappers with same backend to be equal.

Bug: b/324583507
Change-Id: I266228a802b89778ae5a91d9be3e0c6e32a584b1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5307640
Reviewed-by: Etienne Dechamps edechamps@google.com
Reviewed-by: Stefano Duo stefanoduo@google.com
Commit-Queue: Chidera Olibie colibie@google.com
Cr-Commit-Position: refs/heads/main@{#1273331}

M components/cronet/android/BUILD.gn
M components/cronet/android/java/src/org/chromium/net/impl/AndroidBidirectionalStreamBuilderWrapper.java
M components/cronet/android/java/src/org/chromium/net/impl/AndroidBidirectionalStreamCallbackWrapper.java
M components/cronet/android/java/src/org/chromium/net/impl/AndroidBidirectionalStreamWrapper.java
M components/cronet/android/java/src/org/chromium/net/impl/AndroidHttpEngineWrapper.java
M components/cronet/android/java/src/org/chromium/net/impl/AndroidUrlRequestBuilderWrapper.java
M components/cronet/android/java/src/org/chromium/net/impl/AndroidUrlRequestCallbackWrapper.java
M components/cronet/android/java/src/org/chromium/net/impl/AndroidUrlRequestWrapper.java
M components/cronet/android/test/javatests/src/org/chromium/net/BidirectionalStreamTest.java
M components/cronet/android/test/javatests/src/org/chromium/net/CronetTestRule.java
M components/cronet/android/test/javatests/src/org/chromium/net/CronetUrlRequestTest.java
M components/cronet/android/test/javatests/src/org/chromium/net/TestBidirectionalStreamCallback.java
M components/cronet/android/test/javatests/src/org/chromium/net/TestUrlRequestCallback.java
A components/cronet/android/test/javatests/src/org/chromium/net/impl/AndroidBidirectionalStreamWrapperTest.java
A components/cronet/android/test/javatests/src/org/chromium/net/impl/AndroidUrlRequestWrapperTest.java

https://chromium-review.googlesource.com/5307640

From issue 324583507 on 15/03/2024:

fyi: This last paragraph of the cl description above is incorrect.

Correct:

This cl changes the callback wrappers to use the same request/stream object as the one created during build.