diff options
| author | 2022-09-26 14:48:56 +0900 | |
|---|---|---|
| committer | 2023-04-19 16:52:54 +0900 | |
| commit | 038091ddea34971a3aacbe16e426c4f460671e22 (patch) | |
| tree | a6811a6bb6a0e338a8d75fafb02e0c9442ad2919 /java/sdk_library_test.go | |
| parent | 15fc2294389d8d1d8f6c2247a57425d299033d9c (diff) | |
Use PackedAdditionalOutputs when reading apk_set for canned_fs_config
When an app_set module is included in an APEX, we don't use its
`builtFile` which is the main APK, , but `PackedAdditionalOutputs()`
which is the zip file where all APK files (main + additional) files are
packed. We then unzip them into the corresponding directory inside the
APEX.
However, `buildFile` still has been used when constructing
canned_fs_config whose content should match with what are actually
included in the APEX. Fixing the bug by using
`PackedAdditionalOutputs()` instead.
Bug: 236299724
Bug: 254192829
Bug: 240449675
Test: m nothing (apex_test.go amended)
Test: follow https://buganizer.corp.google.com/issues/236299724#comment34
* mkdir for-236299724
* cd for-236299724
* repo init -u https://android.googlesource.com/platform/manifest -b
* master --partial-clone --clone-filter=blob:none
* repo sync -c -j8
* unzip -l ~/Downloads/mainline_t_2022_jun_t1004275.zip | cut -c31- | grep | xargs rm -f
* unzip ~/Downloads/mainline_t_2022_jun_t1004275.zip
* source build/envsetup.sh
* choosecombo 1 aosp_arm64 userdebug
* m com.android.extservices.gms
Merged-In: If9752c07748300dbb963568de4e879b041b0a206
Change-Id: If9752c07748300dbb963568de4e879b041b0a206
(cherry picked from commit e1b6914f58d61fb7279d704dbadc1193744315c3)
Diffstat (limited to 'java/sdk_library_test.go')
0 files changed, 0 insertions, 0 deletions