commit 31b65f9aa193c26d54c55783edcaa9a09ce65c81
author Christopher Tate <ctate@google.com> Mon Sep 09 14:17:27 2013 -0700
committer Christopher Tate <ctate@google.com> Mon Sep 09 14:17:27 2013 -0700
tree cef49ddac34ed433c6a2bc357bd6133eda7bcc05
parent e6a01f37934340c9fce9dcd8ee98b02d9d635af6

Fix clearApplicationUserData() to allow a null observer

The services themselves already handle 'null' to mean "no observer";
it was just the non-AIDL marshalling code that wasn't doing the
right thing.

Bug 9588299

Change-Id: I99e26cd207f91e8060d9fc113aef90a106640b64

core/java/android/app/ActivityManagerNative.java

diff --git a/core/java/android/app/ActivityManagerNative.java b/core/java/android/app/ActivityManagerNative.java
index 6d72114..653559d 100644
--- a/core/java/android/app/ActivityManagerNative.java
+++ b/core/java/android/app/ActivityManagerNative.java
@@ -3377,7 +3377,7 @@
         Parcel reply = Parcel.obtain();
         data.writeInterfaceToken(IActivityManager.descriptor);
         data.writeString(packageName);
-        data.writeStrongBinder(observer.asBinder());
+        data.writeStrongBinder((observer != null) ? observer.asBinder() : null);
         data.writeInt(userId);
         mRemote.transact(CLEAR_APP_DATA_TRANSACTION, data, reply, 0);
         reply.readException();