Why ZipEntry shows incorrect compilation time of APK file?

Question

Im using this code to show App compilation date:

ApplicationInfo ai = a.getPackageManager().getApplicationInfo(a.getPackageName(), 0);
        ZipFile zf = new ZipFile(ai.sourceDir);
        ZipEntry ze = zf.getEntry("META-INF/MANIFEST.MF");
        long time = ze.getTime() + (3600000 * 2);
        Log.i("date", new SimpleDateFormat("HH:mm:ss dd.MM.yyyy").format(new Date(time)));
        zf.close();

Yesterday everything was fine but today (after Android Studio upgrade ???) everytime It shows

02:00:00 30.11.1979

??? I have already Cleaned and Rebuilt project. What is wrong here?

Why are you adding `3600000 * 2` to the time? 83.3333 days? And since when is the manifest date the compilation date? — user207421, Sep 21 '16 at 10:26
I was using: http://stackoverflow.com/questions/22979806/display-the-android-application-apk-creation-date-in-application — MattiahIT, Sep 21 '16 at 11:20
There is nothing there about either using the manifest date as the compilation date or adding `3600000 * 2` to the time. — user207421, Sep 21 '16 at 11:57

score 1 · Answer 1 · edited May 23 '17 at 10:34

1

Ok I have an answer from: How to write build time stamp into apk

Best option is using Timestamp in Gradle

android {
defaultConfig {
    buildConfigField "long", "TIMESTAMP", System.currentTimeMillis() + "L"
}

}

Date buildDate = new Date(BuildConfig.TIMESTAMP);

Thanks :)

edited May 23 '17 at 10:34

Community

1
1

answered Sep 21 '16 at 11:28

MattiahIT

87
9

score 1 · Answer 2 · answered Aug 14 '18 at 12:58

According to response #3 on this Google Issue, the ZipFile method of obtaining the build date can still be used as long as "android.keepTimestampsInApk = true" is set in Gradle properties.

Gradle intentionally zeroes out the build timestamps unless that property is set.

Why ZipEntry shows incorrect compilation time of APK file?

2 Answers2