summaryrefslogtreecommitdiff
path: root/tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp
diff options
context:
space:
mode:
authorAndrii Kulian <akulian@google.com>2018-12-13 18:18:54 -0800
committerAndrii Kulian <akulian@google.com>2018-12-18 15:07:04 -0800
commit2eb84b28779b35da8e410564db33a8aab1f3fbcb (patch)
tree9a02c1fcbae1ea3cfe38dde1a901b5e6726f30ee /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp
parent009bd1bfe357418d993a93f3b28adb56d8ea01e5 (diff)
Add API to check if activity can be started on a display
Some activity launch restrictions apply to virtual displays, which are not communicated to apps. Currently there is no way to check this in advance before starting an activity. This means that an app get an unexpected SecurityException after calling startActivity and therefore cannot know when to show in their UI a possible option to launch on a secondary display. This CL gives adds a public API to check the possibility of launch on a specific display. Test: ActivityManagerMultiDisplayTests Bug: 119575501 Change-Id: Ieb70f0bb79b1a88b7284a19af2efeeb1fcb90f75
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions