Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When producing an Android build the android documentation states that you should zipalign only after you have signed.
But isn’t the whole purpose of signing to make sure that your archive is unmodified?
I don’t understand how you can sign something, then modify it and it can still be in a signed state.
zipalign differs from modifying. It aligns zip header bytes so when your app runs on a device, it starts (unzips in memory) faster and takes less memory comparing to a none-aligned zip. It does not modify files in the archive, so sign would be valid after it.