if you do: Cordova build --release, The blackberry10 platform will generate a signed image...
On 10/6/14, 3:18 PM, "Andrew Grieve" <[email protected]> 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 <[email protected]> >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 >>
