commit b1eaa1752eeef669b3fb0cbbddc99c04b3ff0e55
author vadimt <vadimt@google.com> Mon Mar 02 18:34:34 2020 -0800
committer vadimt <vadimt@google.com> Mon Mar 02 18:36:01 2020 -0800
tree 3104ba7999ab143a0055c570ddba1489000d1451
parent d7ac763b9869d0980da45f833877ae354ef1d516

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

tests/src/com/android/launcher3/util/rule/SimpleActivityRule.java

diff --git a/tests/src/com/android/launcher3/util/rule/SimpleActivityRule.java b/tests/src/com/android/launcher3/util/rule/SimpleActivityRule.java
index 33a6cf9..1dbba6a 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 @@
                 mBase.evaluate();
             } finally {
                 app.unregisterActivityLifecycleCallbacks(this);
+                mActivity = null;
             }
         }