diff options
| author | Suprabh Shukla <suprabh@google.com> | 2016-08-04 16:24:45 -0700 |
|---|---|---|
| committer | Suprabh Shukla <suprabh@google.com> | 2016-08-04 17:05:12 -0700 |
| commit | 9704e409dfe1c1fc582d98837f2a315886a1cd61 (patch) | |
| tree | 65fd362509401e00fb6ce1c0970b6f616608d484 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 29cc1b693937ece2a110057713d07b3194a2f8a5 (diff) | |
Not trying to remove admins already being removed
If someone calls removeActiveAdminLocked more than once, it is possible
for the device policy data to end up with more than one copy of an admin
in the list mRemovingAdmins. Due to extra entries, once the admin
component is removed, it is not being allowed to be set as an admin again,
until the device reboots or mRemovingAdmins is cleared from the memory
due to some other reason. Fixing this by making sure we do not add
duplicate entries to mRemovingAdmins
Bug: 30369197
Change-Id: I1d53c41312171425bbd6e6e4153148276f1b098d
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions