[
https://issues.apache.org/jira/browse/CB-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153357#comment-14153357
]
Joe Bowser commented on CB-7665:
--------------------------------
So, when you follow the steps here:
http://developer.android.com/tools/building/building-cmdline.html#ReleaseMode,
it doesn't work. The fact is that it needs to be signed before it's
zipaligned. This is something that I do so rarely that I usually have to
consult the guide. I think you would be better off running ant, and running
ant release here, since that's what our scripts do for the most part.
> Release process for Google Play has no documentation, requires guesswork!
> --------------------------------------------------------------------------
>
> Key: CB-7665
> URL: https://issues.apache.org/jira/browse/CB-7665
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Android, CLI, Docs
> Affects Versions: 3.5.0
> Environment: Mac OS X Lion
> Reporter: Steve Husting
> Labels: patch
> Fix For: 3.5.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
