[CB-7665] Release process for Google Play has no documentation, requires guesswork!

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.5.0
• Fix Version/s: 3.5.0, 3.7.0
• Component/s: cordova-android, cordova-cli
• Labels: patch

Environment

Mac OS X Lion

• Assignee: Unassigned
• Reporter: Steve Husting
• Created: 29/Sep/14 22:08
• Updated: 23/Aug/18 06:52
• Resolved: 25/Oct/14 01:59

Description

I output my myApp version 12 project with: cordova build android --release

It was output as myApp/platforms/android/ant-build/myApp-release-unsigned.apk

I changed the name to the final apk name: myApp-release-unsigned.apk = myApp.apk

I copied the myApp.keystore file used on earlier myApps to the same folder.

Starting with that folder, I ran: jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore myApp.keystore myApp.apk myApp

I successfully verified it with: jarsigner -verify -verbose -certs myApp.apk

When I uploaded the myApp.apk to Google Play, it said that the file needed to be zipaligned.

The verbose output shows zipalign being done. So is there a bug when the apk is made via cordova build android --release?

Is there a step missing that I should be taking? Unfortunately, all the instructions for this on the Internet assume I'm not using Cordova.

Issue Links

• is related to: CB-7869 improve the doc regarding building release APKs for Android