diff options
| author | Jeff Sharkey <jsharkey@android.com> | 2019-05-14 14:55:13 -0600 |
|---|---|---|
| committer | Jeff Sharkey <jsharkey@android.com> | 2019-05-14 14:55:15 -0600 |
| commit | 3f704637b47bb7bc1f8d0004213fa3e803c21c58 (patch) | |
| tree | 3f457e28f03cac1b5c2250dbc42b524b8aa99b7b /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 3dc28cb1dcd4d3c8f1e48912cf5d2d8f65815985 (diff) | |
Explicitly request clearing of external storage.
Similar to how we target DE and CE storage areas, callers need to
specifically ask to work with EXTERNAL storage. This is because
external storage often lives on a separate device from where internal
DE and CE data lives.
As one specific example, if we're moving an app between two
"internal" storage devices, we don't want to clean up the data
for that package on external storage, since it's not being moved.
This change also expands to all mounted external storage devices,
not just the storage backed by the incoming UUID.
Bug: 113277754
Test: atest android.appsecurity.cts.StorageHostTest
Test: atest android.appsecurity.cts.ExternalStorageHostTest
Test: atest --test-mapping frameworks/base/services/core/java/com/android/server/pm/
Change-Id: Ie125303726dd757ee45bd373f53addb35569c2f7
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions