Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of gtanner@gmail.com designates
 209.85.219.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CCC95D14.118D9%fil@adobe.com>
References: 
 <CACuXHJOFTXu-DEDffS9mayBUQ_V_mkP1r-Wwuxd-xZkcdZ3_Sg@mail.gmail.com>
 <CCC95D14.118D9%fil@adobe.com>
From: Gord Tanner <gtanner@gmail.com>
Date: Wed, 14 Nov 2012 18:18:59 -0500
Message-ID: 
 <CAESi+49G2qwJPfD8P787nv0ZWeN3sZyUs2ASxM1dxqRMz_=vmw@mail.gmail.com>
Subject: Re: RIM/BlackBerry folk: please help
To: dev@cordova.apache.org
Content-Type: multipart/alternative; boundary=e89a8fb1f21692c5a304ce7cc33f

--e89a8fb1f21692c5a304ce7cc33f
Content-Type: text/plain; charset=ISO-8859-1

Signing worked for me with my super epic script:

var sys = require('sys')
var exec = require('child_process').exec;

exec("ant qnx load-device", function (error, stdout, stderr) {
    sys.print('stdout: ' + stdout);
    sys.print('stderr: ' + stderr);
    if (error !== null) {
        console.log('exec error: ' + error);
    }
});

I think your main issue is the version number and buildId hackery for
signing.


On Wed, Nov 14, 2012 at 5:38 PM, Filip Maj <fil@adobe.com> wrote:

> That's not what happens though.
>
> When I create a fresh project, the name and version are always the same.
>
> When I run the signing via node, it fails.
>
> Then I'll CD into this exact same project folder and run the signing
> manually. It works.
>
> I'll also create a new project manually with that same version and app
> name. If I sign it via command line it works. If I do it via my node
> script it fails.
>
> On 11/14/12 2:32 PM, "Tim Kim" <timkim85@gmail.com> wrote:
>
> >The reason why you keep getting signing failures even with a fresh project
> >is that you already did it once. ie, in your config.xml, the widget
> >version
> >is set to "1.0.0.0" and the name attribute is "cordovaExample". So the
> >first time should work, but every new fresh project there after will have
> >the same values.
> >
> >I would recommend updating the version number every time you deploy and
> >not
> >worry about that debug-token business -  I've never used it.
> >
> >--
> >Timothy Kim
>
>

--e89a8fb1f21692c5a304ce7cc33f--