cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tommy-carlos williams <to...@devgeeks.org>
Subject Re: Build signed archives using CLI
Date Tue, 07 Oct 2014 22:44:27 GMT
Frederico’s workflow is the same as ours. I would love to see something happen To improve
this, the less time I spend in Xcode, the happier I am ;)



On 7 October 2014 at 8:48:40, Frederico Galvão (frederico.galvao@pontoget.com.br) wrote:

I can already get the ultimate .apk through "cordova build android  
--release", but I already have the required .properties properly configured  
in my platform/android folder, specifying the path and name to my  
keystores. The "cordova build android --release" already gives me the  
signed and ready .apk, all I have to do is upload it to play.google.com.  

I have never, however, used cordova's CLI to build the final artifact for  
iOS (IPA) for iTunes. All I do is run "cordova prepare", and use xCode from  
then on to build, package, sign, and upload.  

2014-10-06 16:52 GMT-03:00 Parashuram Narasimhan (MS OPEN TECH) <  
panarasi@microsoft.com>:  

> How about a "cordova package" command, that would be for packaging the app  
> for the store? Note that different platforms may have different  
> requirements for certs, signing etc. So it may make sense to promote this  
> to a different command and let each command take care of packaging the app  
> for the store. This command will also mean that developers don’t have to go  
> over to the native projects when they finally want to publish their apps to  
> the store.  
>  
> -----Original Message-----  
> From: Josh Soref [mailto:jsoref@blackberry.com]  
> Sent: Monday, October 6, 2014 12:46 PM  
> To: dev  
> Subject: Re: Build signed archives using CLI  
>  
> if you do:  
> Cordova build --release,  
> The blackberry10 platform will generate a signed image...  
>  
> On 10/6/14, 3:18 PM, "Andrew Grieve" <agrieve@chromium.org> wrote:  
>  
> >AFAIK, I don't think there's any technical roadblocks. Just need a  
> >proposal for how it should look, and then a patch & docs to add it!  
> >  
> >For Android's hot-off-the-press gradle support, you can set an  
> >environment variable that points to a .properties file for signing  
> >builds. This shows one way to go about it, but I'm not in love with the  
> .properties idea.  
> >  
> >On Mon, Oct 6, 2014 at 2:48 PM, Victor Sosa <sosah.victor@gmail.com>  
> >wrote:  
> >  
> >> Hi community.  
> >>  
> >> Been looking at this topic and wondering why the build command does  
> >>not create signed archives. Digging a little bit found a lot of  
> >>differences in the platforms to create these archives.  
> >>  
> >> For instance, in Android you need to  
> >> 1. Export your APK in release mode (--release flag) 2. Sign your APK  
> >> (you already need a RSA key)  
> >>  
> >> In iOS, you need to:  
> >> 1. Export your APP using --device flag (--release seems to export for  
> >>emulator only) 2. Either use XCode (UI-based) and sign the archive or  
> >>use xcrun (headless  
> >> process)  
> >>  
> >> Besides these differences, what is preventing Cordova from providing  
> >> a generic one-way to build these signed, ready-to-publish archives?  
> >>  
> >> Perhaps I'm missing something here...? I really appreciate your  
> >>insights on this topic  
> >>  
> >> Thanks!  
> >>  
> >> --  
> >> Victor Adrian Sosa Herrera  
> >> IBM Software Engineer  
> >> Guadalajara, Jalisco  
> >>  
>  
>  
> ---------------------------------------------------------------------  
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org  
> For additional commands, e-mail: dev-help@cordova.apache.org  
>  



--  

*Frederico Galvão*  

Diretor de Tecnologia  

PontoGet Inovação Web  


( +55(62) 8131-5720  

* www.pontoget.com.br <http://www.pontoget.com/>  

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message