Metadata

[IzzySoft]

As it got pretty silent here during the last year, I thought I better ask before opening a PR: would you accept a PR shipping the app metadata (description + graphics) from IzzyOnDroid, using fastlane structures, so you can keep them updated and they get synchronized here whenever a new release is being pulled in, @VishalNehra / @VishnuSanal ? It would help us with our current repo reorg as well. Thanks in advance!

[VishnuSanal]

As it got pretty silent here during the last year, I thought I better ask before opening a PR: would you accept a PR shipping the app metadata (description + graphics) from IzzyOnDroid, using fastlane structures, so you can keep them updated and they get synchronized here whenever a new release is being pulled in, @VishalNehra / @VishnuSanal ? It would help us with our current repo reorg as well. Thanks in advance!

@IzzySoft please! :)

[IzzySoft]

There you go 🤗

Btw: while integrating the Fastlane tree, I've stumbled upon an older Triple-T one. It serves similar purposes, but is no longer developed (Triple-T is "in maintenance mode"). You might wish to remove that (or at least the "overlapping parts", see app/src/main/play/* – what Fastlane covers, is in the listings/ subdir.

While F-Droid supports Triple-T, at IzzyOnDroid we did not add support for it. For one, only very few projects use it (less than 10 out of the currently 1.3k+ apps in our repo) – and for the other, as it is no longer developed anyhow, so few new projects would go for it.

Thought it would be fair to mention this along – and hope you'll still accept the now opened PR 😜

[IzzySoft]

Btw, just a side note, @VishalNehra / @VishnuSanal – your website certificate expired in April, in case you missed that. And our APK scanner reports

signing blob(s): 0x504b4453 (DEPENDENCY_INFO_BLOCK; GOOGLE).

So if you could add a few lines to your build.gradle for the next release(s):

android {
    dependenciesInfo {
        // Disables dependency metadata when building APKs (for IzzyOnDroid/F-Droid)
        includeInApk = false
        // Disables dependency metadata when building Android App Bundles (for Google Play)
        includeInBundle = false
    }
}

For some background: that BLOB is supposed to be just a binary representation of your app's dependency tree. But as it's encrypted with a public key belonging to Google, only Google can read it – and nobody else can even verify what it really contains. More details can be found e.g. in our documentation on Signing Block Checks at our website, and in our blog article Ramping up security: additional APK checks are in place with the IzzyOnDroid repo.

Thanks!