From 4be84bb10cf0bd998f33d9e5a7ca42cf8e072ad7 Mon Sep 17 00:00:00 2001
From: Adam Powell <adamp@google.com>
Date: Wed, 27 Apr 2016 13:45:38 -0700
Subject: [PATCH] Don't lose content change during rollback for loader already
 started

Framework edition

If a loader is already started when we try to rollback a content
change, force a new load instead of simply setting the flag to refresh
next time.

Bug 28406183

https://code.google.com/p/android/issues/detail?id=208278

Change-Id: If11d79088d30dd2dc48cf1b3d2882f3712b6cddb
---
 core/java/android/content/Loader.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/core/java/android/content/Loader.java b/core/java/android/content/Loader.java
index e9d82afe87579..c5e0ea7278692 100644
--- a/core/java/android/content/Loader.java
+++ b/core/java/android/content/Loader.java
@@ -484,7 +484,7 @@ public class Loader<D> {
      */
     public void rollbackContentChanged() {
         if (mProcessingChange) {
-            mContentChanged = true;
+            onContentChanged();
         }
     }