This thread was migrated from an old forum. It may contain information that are no longer valid. For further assistance, please post a new question or open a support ticket from the Customer Support portal. |
This thread was migrated from an old forum. It may contain information that are no longer valid. For further assistance, please post a new question or open a support ticket from the Customer Support portal. |
@Joe Axwvhvm can you please look into this.
@Avvni Tewwy
Zipalign documentation doesn't mention any changes to be done to the command with respect to 64 bit APK , hence you still need to use 4 Byte boundary as you did with 32 bit.
https://developer.android.com/studio/command-line/zipalign
You can post a direct query on Google tracker links indicated below.
How ever, I would say you can do an experiment with 8 Byte boundary as argument for 64 bit apk and if installation of APK works and boots up properly you can post a query/doc bug on relevant Google issue tracker links below with your experimentation results.
As google/Android team is the right team to comment on the caveats of the zip align .
General bug Tracker:
https://issuetracker.google.com/issues/new
Doc bug:
https://issuetracker.google.com/issues/new?component=192697&template=845603
Android Bugs Tracker :
https://issuetracker.google.com/issues/new?component=190923&template=841312
Please share your observations for greater audience knowledge and the tracker link once you have created it.
@Joe Axwvhvm
Thank you for the fast response. I did experiment to upload multiple apk 32bit 4bytes and 64bit 8bytes, and I didn't get any errors or complains from google store.
The app also installed and run just fine on 32bit device and 64bit device.
Regards,