Assigned
Status Update
Comments
fl...@obfusk.net <fl...@obfusk.net> #2
We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.
ju...@google.com <ju...@google.com>
fl...@obfusk.net <fl...@obfusk.net> #4
fl...@obfusk.net <fl...@obfusk.net> #5
Please provide an update
fl...@obfusk.net <fl...@obfusk.net> #6
Hi Fiona, are you able to route this bug for an update? There are multiple partners asking about this. Appreciate your help.
je...@google.com <je...@google.com>
fl...@obfusk.net <fl...@obfusk.net> #7
Hi Fiona,
Any update on this?
Any update on this?
Description
DESCRIBE THE ISSUE IN DETAIL
I've seen at least 5 different apps fail to build reproducibly because one build was done on Windows (usually with Android Studio) and the other on Linux (usually with
./gradlew assembleRelease
) and some files in the APK built on Windows have CRLF line endings whereas the same files have LF line endings in the build on Debian (but are otherwise 100% identical).Most commonly affected are files in
META-INF/services/
, but I've also seen HTML/CSS/JS files inassets/
with the same issue.Whilst there is a workaround it would be preferable if APKs built on different operating systems were always identical.
STEPS TO REPRODUCE
./gradlew assembleRelease
on DebianEXPECTED RESULT
Identical APKs (apart from the signature in the case of signed APKs).
ACTUAL RESULT
Non-identical APKs because of line ending differences (as described above).
VERSION INFO