From fea75f2e4287c2cc12fb0ae07551768c5581570c Mon Sep 17 00:00:00 2001
From: aquilescanta <aquilescanta@google.com>
Date: Tue, 6 Feb 2018 05:47:07 -0800
Subject: [PATCH] Prevent "unexpected read attempt" illegal state exception

When using cronet data source, calling read after the end of input has
been read will trigger this.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=184667794
---
 .../google/android/exoplayer2/ext/cronet/CronetDataSource.java   | 1 +
 1 file changed, 1 insertion(+)

diff --git a/extensions/cronet/src/main/java/com/google/android/exoplayer2/ext/cronet/CronetDataSource.java b/extensions/cronet/src/main/java/com/google/android/exoplayer2/ext/cronet/CronetDataSource.java
index 536155a70f..29bc874cd8 100644
--- a/extensions/cronet/src/main/java/com/google/android/exoplayer2/ext/cronet/CronetDataSource.java
+++ b/extensions/cronet/src/main/java/com/google/android/exoplayer2/ext/cronet/CronetDataSource.java
@@ -369,6 +369,7 @@ public class CronetDataSource extends UrlRequest.Callback implements HttpDataSou
         throw new HttpDataSourceException(exception, currentDataSpec,
             HttpDataSourceException.TYPE_READ);
       } else if (finished) {
+        bytesRemaining = 0;
         return C.RESULT_END_OF_INPUT;
       } else {
         // The operation didn't time out, fail or finish, and therefore data must have been read.