diff options
| author | Jeff Chang <chengjeff@google.com> | 2021-01-14 16:38:02 +0800 |
|---|---|---|
| committer | Jeff Chang <chengjeff@google.com> | 2021-02-04 16:44:34 +0800 |
| commit | f714906c48119413fbf864b0bc00589e9088e523 (patch) | |
| tree | a7630579dfe525daa9397ccb3b3b29ec8470b455 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 82dd3e14f8ecdc6802a60af8b9636c71fadba75b (diff) | |
Avoid creating new instance when started for result with singleInstance/singleTask
The activity with launchMode "singleTask" and "singleInstance" can
exist in multiple instances. It contradicts with developers
documentation and breaks the purpose of these modes. The conditions
for searching the reusable tasks always ignore the start-for-result
case result in singleInstance/singleTask instances being created.
List the problems :
1. singleInstance activity stays in the caller’s task if it was
started via startActivityForResult(). The activity should
always get launched into its own task. It should always be
the single and only member of its task.
2. Multiple singleInstance/singleTask activities are created and stay
in the different tasks.
The CL updates the condition for searching the reusable task which
avoids the new instance being created.
Bug: 122967919
Bug: 148047668
Test: atest IntentTests
Change-Id: I721cfcaac0759327ae81f430d52d81f1c8145262
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions