cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Sullivan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CB-7665) Release process for Google Play has no documentation, requires guesswork!
Date Mon, 13 Oct 2014 22:22:34 GMT

    [ https://issues.apache.org/jira/browse/CB-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170107#comment-14170107
] 

Patrick Sullivan commented on CB-7665:
--------------------------------------

Using cordova 3.6.3 this almost works. In general I followed the steps here: http://intown.biz/2014/07/15/signing-your-cordova-android-app/

In particular:
in confix.xml 'widget version="1.2.3"' it automatically sets 'android:versionCode="10203"
android:versionName="1.2.3"'.

and the local.properties needs these two settings:
key.store=c:\\dev\\ncamobile\\nca.keystore
key.alias=ncamobile

then just type: cordova build android --release
and pay attention to the output.  The path to the signed APK is higher up in the build (it
mistakenly lists the unisigned APK as the final build output).

I'd love to help update the documentation, but I'm not familiar with Apache and not sure where
to start.

> 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)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org


Mime
View raw message