From b1eaa1752eeef669b3fb0cbbddc99c04b3ff0e55 Mon Sep 17 00:00:00 2001
From: vadimt <vadimt@google.com>
Date: Mon, 2 Mar 2020 18:34:34 -0800
Subject: [PATCH] Fixing activity being referred after destroying.

This is perhaps not a leak, but it conflicts with how StrictMode
activity leak detection works.

Bug: 139137636
Change-Id: I1608e348d8b238142c42ed81ae125fd07ef6b673
---
 .../src/com/android/launcher3/util/rule/SimpleActivityRule.java  | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tests/src/com/android/launcher3/util/rule/SimpleActivityRule.java b/tests/src/com/android/launcher3/util/rule/SimpleActivityRule.java
index 33a6cf9766..1dbba6a1f6 100644
--- a/tests/src/com/android/launcher3/util/rule/SimpleActivityRule.java
+++ b/tests/src/com/android/launcher3/util/rule/SimpleActivityRule.java
@@ -64,6 +64,7 @@ public class SimpleActivityRule<T extends Activity> implements TestRule {
                 mBase.evaluate();
             } finally {
                 app.unregisterActivityLifecycleCallbacks(this);
+                mActivity = null;
             }
         }