Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of fil@adobe.com designates
 64.18.1.233 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Date: Wed, 14 Nov 2012 14:38:05 -0800
Subject: Re: RIM/BlackBerry folk: please help
Thread-Topic: RIM/BlackBerry folk: please help
Thread-Index: Ac3CuLq8F0Bv7iNQTriPKEX8AT6GNg==
Message-ID: <CCC95D14.118D9%fil@adobe.com>
In-Reply-To: 
 <CACuXHJOFTXu-DEDffS9mayBUQ_V_mkP1r-Wwuxd-xZkcdZ3_Sg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.4.120824
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

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.
>
>--=20
>Timothy Kim