Uploading duplicate Android releases do not update existing release on app distribution about fastlane-plugin-firebase_app_distribution HOT 5 CLOSED

So a binary compare is done to determine uniqueness for releases?

We're actually comparing a fingerprint of the CRC-32 checksums for Android APKs and call that "instance identifier". For AABs we simply use the SHA-1 hash of the entire binary.

If two uploads have the same "instance identifier", version, and build number, then no new release is created.

For iOS iOS we only use the UUIDs for the executable(s) (a.k.a. CFBundleExecutable) inside the IPAs to determine the "instance identifier". We exclude things like the "provisioning profile" which allows iOS developers to add additional tester device UDIDs and upload an updated binary without creating a new release.

from fastlane-plugin-firebase_app_distribution.

Hi @eddiecubed !

It appears that the APKs that you are uploading are slightly different. Try comparing the output of unzip -v file.apk for your builds - especially the CRC-32.

You'll probably notice that files like classes*.dex and/or META_INF/{CERT.SF,CERT.RSA,MANIFEST.MF} differ between builds.

P.S.: If you didn't keep a copy of the APKs you can download them from the Firebase console.

from fastlane-plugin-firebase_app_distribution.

FYI: Stackoverflow has some information about reproducible builds.

from fastlane-plugin-firebase_app_distribution.

So a binary compare is done to determine uniqueness for releases?

Thank you for the timely response.

from fastlane-plugin-firebase_app_distribution.

Same thing happening for me, iOS is working fine

from fastlane-plugin-firebase_app_distribution.