Repository navigation
build.gradle: set android.dependenciesInfo.includeInApk = false - #3069
Open
SomberNight wants to merge 1 commit into
Open
SomberNight wants to merge 1 commit into
SomberNight wants to merge 1 commit into
Conversation
This was requested by f-droid devs to publish an app. ref https://gitlab.com/fdroid/fdroiddata/-/merge_requests/15858#note_2150822234 - see https://android.izzysoft.de/articles/named/iod-scan-apkchecks#blobs > BLOBs in APK signing blocks > APK signing blocks are where signing details are stored in. > [...] > DEPENDENCY_INFO_BLOCK: This is supposed to be a binary representation of build dependencies inserted by Google itself, or also by Android Studio and IntelliJ IDEA (plus probably also some other development tools), when an APK is being signed. But it is also encrypted using a public key owned by Google, so one cannot really verify what else might have been placed there. This means when found (which is very often) I reach out to the corresponding developers, suggesting them to use apksigner for signing instead, which does not add this block – or to make sure Android Studio resp. IntelliJ IDEA will not include them (see below). Apkverifier includes a short comment in its code, a.o. „The data is compressed, encrypted by a Google Play signing key...“ (source) > So this in essence is a „blob“ without transparency. As it’s encrypted using a Google Play public key, it cannot be decrypted without the corresponding private key – so except for Google, no one can say for sure which other bits might have been added along.
f321x
added a commit
to f321x/spesmilo-python-for-android-fork-fork
that referenced
this pull request
Oct 14, 2026
p4a normalises the archives it builds itself (make_tar sorts entries and zeroes mtime and ownership, the gzip stream gets mtime=0), but sets nothing on the Gradle side, so any Zip/Jar/Tar task records file mtimes and walks directories in filesystem order. With AGP 8.11 this changes no shipped artifact: the apk and aab come from PackageAndroidArtifact and PackageBundleTask, which do not descend from AbstractArchiveTask, and the BundleAar tasks on the service_library path already get both flags from AGP. What it buys is that an archive task added later, by a future AGP or by a plugin pulled in through --gradle-dependency, cannot bake in timestamps or filesystem order. Refs kivy#3066, kivy#3069. Upstreamed from https://github.com/spesmilo/python-for-android
f321x
added a commit
to f321x/spesmilo-python-for-android-fork-fork
that referenced
this pull request
Oct 14, 2026
p4a normalises the archives it builds itself (make_tar sorts entries and zeroes mtime and ownership, the gzip stream gets mtime=0), but sets nothing on the Gradle side, so any Zip/Jar/Tar task records file mtimes and walks directories in filesystem order. With AGP 8.11 this changes no shipped artifact: the apk and aab come from PackageAndroidArtifact and PackageBundleTask, which do not descend from AbstractArchiveTask, and the BundleAar tasks on the service_library path already get both flags from AGP. What it buys is that an archive task added later, by a future AGP or by a plugin pulled in through --gradle-dependency, cannot bake in timestamps or filesystem order. Refs kivy#3066, kivy#3069. Upstreamed from https://github.com/spesmilo/python-for-android
f321x
added a commit
to f321x/spesmilo-python-for-android-fork-fork
that referenced
this pull request
Oct 14, 2026
Gradle's Zip, Jar and Tar tasks store file mtimes and use filesystem order, so their output differs between builds. p4a normalises the tars it writes itself, but sets nothing on the gradle side. Under AGP 8.11 no shipped artifact changes: the apk and aab are not built by archive tasks, and the service_library aar task already gets both flags from AGP. The point is the default, so an archive task added later by a newer AGP or by a plugin from --gradle-dependency is reproducible too. Refs kivy#3066, kivy#3069. Upstreamed from https://github.com/spesmilo/python-for-android
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This was requested by f-droid devs to publish an app.
ref https://gitlab.com/fdroid/fdroiddata/-/merge_requests/15858#note_2150822234
see https://android.izzysoft.de/articles/named/iod-scan-apkchecks#blobs