Increase cts-app Test Stability
Bug 2639189
Many cts-app tests start LaunchpadActivity which in turn calls
startActivityForResult and expects onActivityResult to setResult
to SUCCESS. Other tests don't use startActivityForResult and are
coded to depend on onDestroy to send back a result which defaults
to cancelled! When ActivityManagerService decides to change the
configuration for some reason, onDestroy terminates and never
gets back the result. It ends up setting cancelled and causes
the tests to fail! Thus, fix LaunchpadActivity to ignore
configuration changes that ActivityManagerService to prevent
it from being destroyed.
Change-Id: Iea2944f66b4dd1ecdfccfcc4bcdc9354de2eb623
diff --git a/tests/AndroidManifest.xml b/tests/AndroidManifest.xml
index ddc6797..4bf8239 100644
--- a/tests/AndroidManifest.xml
+++ b/tests/AndroidManifest.xml
@@ -879,7 +879,9 @@
</service>
<service android:name="android.app.cts.IntentServiceStub"/>
- <activity android:name="android.app.cts.LaunchpadActivity" android:multiprocess="true">
+ <activity android:name="android.app.cts.LaunchpadActivity"
+ android:configChanges="keyboardHidden|orientation"
+ android:multiprocess="true">
</activity>
<service android:name="android.content.cts.MockSyncAdapterService" android:exported="true">
