cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filip Maj <...@adobe.com>
Subject Re: RIM/BlackBerry folk: please help
Date Mon, 19 Nov 2012 23:45:02 GMT
Hey Gord,

This is awesome! Thank you. Indeed this is exactly what I wanted. Now for
the CI setup I no longer have to worry about debug tokens expiring.

Unfortunately no matter how I package my webworks app, when I launch the
app a black BlackBerry loading screen comes up on my dev alpha A device
and doesn't go any further :(

Any debugging approach you can recommend ?

On 11/18/12 7:19 AM, "Gord Tanner" <gtanner@gmail.com> wrote:

> I updated the ant scripts for blackberry to support debug tokens when
>debugging on a device:
>
>https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-blackberry-web
>works.git;a=commitdiff;h=9c1edccf60b48e1914f4b7093cf00d477908a05d
>
>If you fill in the qnx.device.pin value in project.properties it will now
>create and load a debug token on your device and load unsigned when using
>the debug-device command.
>
>I hope this is a little closer for your CI stuff.
>
>
>On Thu, Nov 15, 2012 at 8:49 AM, Nukul Bhasin <me@nukulb.com> wrote:
>
>> I agree with Gord's evaluation of the problem,
>> The error you are getting is often because of buildId not getting
>> incrementing
>>
>> Setting up debug tokens can really suck, but its the reality of where we
>> are today. If you use QNX momentics (NDK tooling) it will hide all the
>> ugliness for you.
>> Command Line tools are lagging in bringing the same experience but
>>Signing
>> improvements are on the roadmap, no landing date yet though but its
>>being
>> re-thought completely.
>>
>>
>> On Wed, Nov 14, 2012 at 6:26 PM, Filip Maj <fil@adobe.com> wrote:
>>
>> > Whatever. I gave up and used debug tokens. IT was fucking difficult to
>> get
>> > working but am now at a barely-workable level.
>> >
>> > On 11/14/12 3:18 PM, "Gord Tanner" <gtanner@gmail.com> wrote:
>> >
>> > >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
>> > >>
>> > >>
>> >
>> >
>>
>>
>> --
>> *Nukul Bhasin*
>> *Computer Engineer, B.Eng*
>> *10 Queens Quay W, suite#1710*
>> *Toronto, ON, Canada*
>> *Ph: 416 508 3157*
>>


Mime
View raw message