summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator_test.cpp
diff options
context:
space:
mode:
authorYohei Yukawa <yukawa@google.com>2019-04-09 23:20:12 -0700
committerYohei Yukawa <yukawa@google.com>2019-04-09 23:20:12 -0700
commit3d3abd2c7b3e503f9ca65d7d27f4f00f611749b0 (patch)
tree9f13c90b190271269fe03773e8437ba2d5a86a91 /tools/aapt2/java/JavaClassGenerator_test.cpp
parent10f383b32c204e21b849aaf51ebc3ae0828b2a40 (diff)
Avoid exception from 'adb shell ime enable/disable'
This is a preparation to introduce CTS for per-profile IME. Currently adb shell ime enable <ime id> and adb shell ime disable <ime id> can throw IllegalArgumentException when <ime id> is not recognized by the system. This makes some sense, but if we start supporting '-u all' option it'd make more sense if it just shows an error message rather than letting the command crash with throing an exception. This behavior change also removes a limitation that developers cannot use adb shell ime disable <ime id> command to remove an IME ID from Settings.Secure.ENABLED_INPUT_METHODS if that IME is not currently installed. Bug: 120784635 Test: Manually verified as follows. 1. Build aosp_blueline-userdebug and flash it 2. adb shell ime enable com.example.android.softkeyboard/.SoftKeyboard -> "Unknown input method <IME ID here> cannot be enabled" 3. adb shell ime disable com.example.android.softkeyboard/.SoftKeyboard -> "Input method <IME ID here>: already disabled" Change-Id: Ib9be7700557f2f606c90d62f79ec3afca2f82c40
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions