diff options
| author | Alan Stokes <alanstokes@google.com> | 2019-05-20 15:22:54 +0100 |
|---|---|---|
| committer | Alan Stokes <alanstokes@google.com> | 2019-05-20 15:58:17 +0100 |
| commit | 07389b6e184077006c771d6cbdff7649347492f3 (patch) | |
| tree | 7e3dce50d7476b967bc42e66700c9c9349c14025 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | e1bbd0b1d2dabf954e6e270832df90001df65aa6 (diff) | |
Don't block activity starts in permissive mode.
When activity starts have been enabled via developer options we
shouldn't block them. But we still want to show a toast to warn that
the start would have been blocked.
Scenarios where we were blocking when we shouldn't:
- Creating a new task from a background receiver (here the activity is
created but not brought to the front).
- Starting an activity while app switching protection is in force.
- Various cases when starting an activity in a new task or a task that
doesn't already have one of our activities in it.
Bug: 132919170
Bug: 132919170
Test: manual
Test: atest BackgroundActivityLaunchTest
Test: atest RootWindowContainerTests
Test: atest WmTests:ActivityStarterTests
Test: atest CtsWindowManagerDeviceTestCases:ActivityStarterTests
Test: atest CtsAppTestCases:.ServiceTest
Change-Id: I32d75d04ea93cb4883e93bbe74468755a708ca24
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions