diff options
| author | 2022-04-21 17:58:12 +0100 | |
|---|---|---|
| committer | 2022-04-26 13:49:49 +0100 | |
| commit | 61cb9ddfac3591df9e75cd0989e80d5e5bbebc65 (patch) | |
| tree | 4f5acd102e7de82f39fa4235147b4b63098615fe /libs/androidfw/StringPool.cpp | |
| parent | 91787288b09cc2b04ad844e3598036852e39d379 (diff) | |
apk-in-apex-cache 1/n: Fix isCacheUpToDate for apk-in-apex
In case an APK resides on the APEX mount point it's mtime will always be
zero. This breaks the isCacheUpToDate check, which is based on comparing
the mtime of the apk to the mtime of the cache.
This cl fixes the issue by using the mtime of the APEX file backing the
/apex mount point the apk resides on.
Also noticed some inefficiencies in ApexManager and added TODO's to fix
them in the follow-up cls.
Bug: 225435110
Test: atest PackageParserTest
Test: atest ApexManagerTest
Change-Id: I8a0ab8952454652048076a26e81097b95991ae60
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions