summaryrefslogtreecommitdiff
path: root/scripts/gen-java-current-api-files.sh
diff options
context:
space:
mode:
author Jiyong Park <jiyong@google.com> 2022-09-26 14:48:56 +0900
committer Jiyong Park <jiyong@google.com> 2022-09-26 14:55:35 +0900
commite1b6914f58d61fb7279d704dbadc1193744315c3 (patch)
tree870102c90491f1a1b4e6104bc5892b62c82ecd18 /scripts/gen-java-current-api-files.sh
parent600815596013cb604981247eaaf2ef475a2d1811 (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 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 Change-Id: If9752c07748300dbb963568de4e879b041b0a206
Diffstat (limited to 'scripts/gen-java-current-api-files.sh')
0 files changed, 0 insertions, 0 deletions