You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
android {
dependenciesInfo {
// Disables dependency metadata when building APKs.
includeInApk =false// Disables dependency metadata when building Android App Bundles.
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.
Thanks in advance!
The text was updated successfully, but these errors were encountered:
@IzzySoft I have signed my app using debug key as I am not planning to release this on Play Store anytime. Another reason of using debug key is that it makes app upgrade easier and I don't need to maintain / store any private key. If anyone needs to sign the app, they can easily build and sign the APK themselves as the source code is available.
Thanks for your answer, @gauravssnl! But apps signed using debug keys are no longer allowed in my repo, where I was about to include your app. For background, please see e.g.
It seems your APKs are signed using a debug key:
Would it be possible to use a proper release key instead? Further:
can be easily avoided:
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.
Thanks in advance!
The text was updated successfully, but these errors were encountered: