Re: RIM/BlackBerry folk: please help
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 gtan...@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 m...@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 f...@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 gtan...@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 f...@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 timki...@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*
Re: RIM/BlackBerry folk: please help
Weird, it has been deploying for me. I have seen that black screen lag for a long time when I have done remote debugger + a remote starting page, which is not what you are describing. Any tips nukul? Sent from my iPhone On 2012-11-19, at 6:58 PM, Filip Maj f...@adobe.com wrote: I'm using the latest commit from cordova-blackberry and run the example app with as little changes as possible. My shell commands are (make sure there's no example directory with an app already present in the root of the repo): ./bin/create cd example edit project.properties with my BB10 SDK location, signing password, device ip and device password ant qnx debug-device Shell Output: fil-MacBookAir:example fil$ ant qnx debug-device Buildfile: /Users/fil/src/incubator-cordova-blackberry-webworks/example/build.xml qnx: debug-device: generate-cod-name: [echo] Generated name: cordovaExample.bar clean: package-app: [mkdir] Created dir: /Users/fil/src/incubator-cordova-blackberry-webworks/example/build/widget [copy] Copying 22 files to /Users/fil/src/incubator-cordova-blackberry-webworks/example/build/widget [copy] Copying 1 file to /Users/fil/src/incubator-cordova-blackberry-webworks/example/www/js [zip] Building zip: /Users/fil/src/incubator-cordova-blackberry-webworks/example/build/cordovaE xample.zip debug-device: [exec] Info: Debug token created. [exec] Info: Sending request: Install [exec] Info: Action: Install [exec] Info: File size: 2263 [exec] Info: Installing ... [exec] Info: Processing 2263 bytes [exec] actual_dname::debug.token.gYABgIVTqbRuktLyOHwoFTMiQyw [exec] actual_id::gYABgIVTqbRuktLyOHwoFTMiQyw [exec] actual_version::0.0.0.6 [exec] result::success [exec] [INFO]Populating application source [exec] [INFO]Parsing config.xml [exec] [WARN]Build ID set in config.xml [version], but no signing password was provided [-g]. Bar will be unsigned [exec] [WARN]Failed to find feature with id: org.apache.cordova [exec] [WARN]Failed to find feature with id: blackberry.find [exec] [WARN]Failed to find feature with id: blackberry.identity.phone [exec] [WARN]Failed to find feature with id: blackberry.pim.Address [exec] [WARN]Failed to find feature with id: blackberry.pim.Contact [exec] [WARN]Failed to find feature with id: blackberry.io.file [exec] [WARN]Failed to find feature with id: blackberry.utils [exec] [WARN]Failed to find feature with id: blackberry.io.dir [exec] [WARN]Failed to find feature with id: blackberry.app.event [exec] [WARN]Failed to find feature with id: blackberry.system.event [exec] [WARN]Failed to find feature with id: blackberry.widgetcache [exec] [WARN]Failed to find feature with id: blackberry.media.camera [exec] [WARN]Failed to find feature with id: blackberry.media.microphone [exec] [INFO]Generating output files [exec] [INFO]Info: Package created: /Users/fil/src/incubator-cordova-blackberry-webworks/example/build/simulato r/cordovaExample.bar [exec] [INFO]Info: Package created: /Users/fil/src/incubator-cordova-blackberry-webworks/example/build/device/c ordovaExample.bar [exec] [INFO]BAR packaging complete [exec] Info: Sending request: Install and Launch [exec] Info: Action: Install and Launch [exec] Info: File size: 948106 [exec] Info: Installing cordovaExample.testDev_dovaExamplee1922ce_... [exec] Info: Processing 948106 bytes [exec] Info: Progress 28%... [exec] Info: Progress 67%... [exec] Info: Progress 100%... [exec] actual_dname::cordovaExample.testDev_dovaExamplee1922ce_ [exec] actual_id::testDev_dovaExamplee1922ce_ [exec] actual_version::1.0.0.0 [exec] result::success [exec] Info: Launching cordovaExample.testDev_dovaExamplee1922ce_... [exec] result::11276465 [exec] Info: done BUILD SUCCESSFUL Total time: 25 seconds It loads an app called cordovaExample properly. It has no icon for some reason, and the only thing that I see when the app loads is a very dark screen with the BlackBerry logo. On 11/19/12 3:51 PM, Nukul Bhasin m...@nukulb.com wrote: Send us your app From: Filip Maj To: dev@cordova.apache.org Reply To: dev@cordova.apache.org *Re: RIM/BlackBerry folk: please help* 2012-11-19 6:46:11 PM 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 wrote: I updated the ant scripts for blackberry to support debug tokens when
Re: RIM/BlackBerry folk: please help
Also on another note we should be able to port the same debug token stuff to the playbook building as well Sent from my iPhone On 2012-11-19, at 6:58 PM, Filip Maj f...@adobe.com wrote: I'm using the latest commit from cordova-blackberry and run the example app with as little changes as possible. My shell commands are (make sure there's no example directory with an app already present in the root of the repo): ./bin/create cd example edit project.properties with my BB10 SDK location, signing password, device ip and device password ant qnx debug-device Shell Output: fil-MacBookAir:example fil$ ant qnx debug-device Buildfile: /Users/fil/src/incubator-cordova-blackberry-webworks/example/build.xml qnx: debug-device: generate-cod-name: [echo] Generated name: cordovaExample.bar clean: package-app: [mkdir] Created dir: /Users/fil/src/incubator-cordova-blackberry-webworks/example/build/widget [copy] Copying 22 files to /Users/fil/src/incubator-cordova-blackberry-webworks/example/build/widget [copy] Copying 1 file to /Users/fil/src/incubator-cordova-blackberry-webworks/example/www/js [zip] Building zip: /Users/fil/src/incubator-cordova-blackberry-webworks/example/build/cordovaE xample.zip debug-device: [exec] Info: Debug token created. [exec] Info: Sending request: Install [exec] Info: Action: Install [exec] Info: File size: 2263 [exec] Info: Installing ... [exec] Info: Processing 2263 bytes [exec] actual_dname::debug.token.gYABgIVTqbRuktLyOHwoFTMiQyw [exec] actual_id::gYABgIVTqbRuktLyOHwoFTMiQyw [exec] actual_version::0.0.0.6 [exec] result::success [exec] [INFO]Populating application source [exec] [INFO]Parsing config.xml [exec] [WARN]Build ID set in config.xml [version], but no signing password was provided [-g]. Bar will be unsigned [exec] [WARN]Failed to find feature with id: org.apache.cordova [exec] [WARN]Failed to find feature with id: blackberry.find [exec] [WARN]Failed to find feature with id: blackberry.identity.phone [exec] [WARN]Failed to find feature with id: blackberry.pim.Address [exec] [WARN]Failed to find feature with id: blackberry.pim.Contact [exec] [WARN]Failed to find feature with id: blackberry.io.file [exec] [WARN]Failed to find feature with id: blackberry.utils [exec] [WARN]Failed to find feature with id: blackberry.io.dir [exec] [WARN]Failed to find feature with id: blackberry.app.event [exec] [WARN]Failed to find feature with id: blackberry.system.event [exec] [WARN]Failed to find feature with id: blackberry.widgetcache [exec] [WARN]Failed to find feature with id: blackberry.media.camera [exec] [WARN]Failed to find feature with id: blackberry.media.microphone [exec] [INFO]Generating output files [exec] [INFO]Info: Package created: /Users/fil/src/incubator-cordova-blackberry-webworks/example/build/simulato r/cordovaExample.bar [exec] [INFO]Info: Package created: /Users/fil/src/incubator-cordova-blackberry-webworks/example/build/device/c ordovaExample.bar [exec] [INFO]BAR packaging complete [exec] Info: Sending request: Install and Launch [exec] Info: Action: Install and Launch [exec] Info: File size: 948106 [exec] Info: Installing cordovaExample.testDev_dovaExamplee1922ce_... [exec] Info: Processing 948106 bytes [exec] Info: Progress 28%... [exec] Info: Progress 67%... [exec] Info: Progress 100%... [exec] actual_dname::cordovaExample.testDev_dovaExamplee1922ce_ [exec] actual_id::testDev_dovaExamplee1922ce_ [exec] actual_version::1.0.0.0 [exec] result::success [exec] Info: Launching cordovaExample.testDev_dovaExamplee1922ce_... [exec] result::11276465 [exec] Info: done BUILD SUCCESSFUL Total time: 25 seconds It loads an app called cordovaExample properly. It has no icon for some reason, and the only thing that I see when the app loads is a very dark screen with the BlackBerry logo. On 11/19/12 3:51 PM, Nukul Bhasin m...@nukulb.com wrote: Send us your app From: Filip Maj To: dev@cordova.apache.org Reply To: dev@cordova.apache.org *Re: RIM/BlackBerry folk: please help* 2012-11-19 6:46:11 PM 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 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-we b
Re: RIM/BlackBerry folk: please help
Yeah, should be doable. In the end my CI stuff will have to mimic the ant file but not use it. Ant file is built under the assumption that one device is all you are deploying to. To do multiple devices in parallel is not possible atm.. On 11/19/12 5:14 PM, Gord Tanner gtan...@gmail.com wrote: Also on another note we should be able to port the same debug token stuff to the playbook building as well Sent from my iPhone On 2012-11-19, at 6:58 PM, Filip Maj f...@adobe.com wrote: I'm using the latest commit from cordova-blackberry and run the example app with as little changes as possible. My shell commands are (make sure there's no example directory with an app already present in the root of the repo): ./bin/create cd example edit project.properties with my BB10 SDK location, signing password, device ip and device password ant qnx debug-device Shell Output: fil-MacBookAir:example fil$ ant qnx debug-device Buildfile: /Users/fil/src/incubator-cordova-blackberry-webworks/example/build.xml qnx: debug-device: generate-cod-name: [echo] Generated name: cordovaExample.bar clean: package-app: [mkdir] Created dir: /Users/fil/src/incubator-cordova-blackberry-webworks/example/build/widget [copy] Copying 22 files to /Users/fil/src/incubator-cordova-blackberry-webworks/example/build/widget [copy] Copying 1 file to /Users/fil/src/incubator-cordova-blackberry-webworks/example/www/js [zip] Building zip: /Users/fil/src/incubator-cordova-blackberry-webworks/example/build/cordov aE xample.zip debug-device: [exec] Info: Debug token created. [exec] Info: Sending request: Install [exec] Info: Action: Install [exec] Info: File size: 2263 [exec] Info: Installing ... [exec] Info: Processing 2263 bytes [exec] actual_dname::debug.token.gYABgIVTqbRuktLyOHwoFTMiQyw [exec] actual_id::gYABgIVTqbRuktLyOHwoFTMiQyw [exec] actual_version::0.0.0.6 [exec] result::success [exec] [INFO]Populating application source [exec] [INFO]Parsing config.xml [exec] [WARN]Build ID set in config.xml [version], but no signing password was provided [-g]. Bar will be unsigned [exec] [WARN]Failed to find feature with id: org.apache.cordova [exec] [WARN]Failed to find feature with id: blackberry.find [exec] [WARN]Failed to find feature with id: blackberry.identity.phone [exec] [WARN]Failed to find feature with id: blackberry.pim.Address [exec] [WARN]Failed to find feature with id: blackberry.pim.Contact [exec] [WARN]Failed to find feature with id: blackberry.io.file [exec] [WARN]Failed to find feature with id: blackberry.utils [exec] [WARN]Failed to find feature with id: blackberry.io.dir [exec] [WARN]Failed to find feature with id: blackberry.app.event [exec] [WARN]Failed to find feature with id: blackberry.system.event [exec] [WARN]Failed to find feature with id: blackberry.widgetcache [exec] [WARN]Failed to find feature with id: blackberry.media.camera [exec] [WARN]Failed to find feature with id: blackberry.media.microphone [exec] [INFO]Generating output files [exec] [INFO]Info: Package created: /Users/fil/src/incubator-cordova-blackberry-webworks/example/build/simula to r/cordovaExample.bar [exec] [INFO]Info: Package created: /Users/fil/src/incubator-cordova-blackberry-webworks/example/build/device /c ordovaExample.bar [exec] [INFO]BAR packaging complete [exec] Info: Sending request: Install and Launch [exec] Info: Action: Install and Launch [exec] Info: File size: 948106 [exec] Info: Installing cordovaExample.testDev_dovaExamplee1922ce_... [exec] Info: Processing 948106 bytes [exec] Info: Progress 28%... [exec] Info: Progress 67%... [exec] Info: Progress 100%... [exec] actual_dname::cordovaExample.testDev_dovaExamplee1922ce_ [exec] actual_id::testDev_dovaExamplee1922ce_ [exec] actual_version::1.0.0.0 [exec] result::success [exec] Info: Launching cordovaExample.testDev_dovaExamplee1922ce_... [exec] result::11276465 [exec] Info: done BUILD SUCCESSFUL Total time: 25 seconds It loads an app called cordovaExample properly. It has no icon for some reason, and the only thing that I see when the app loads is a very dark screen with the BlackBerry logo. On 11/19/12 3:51 PM, Nukul Bhasin m...@nukulb.com wrote: Send us your app From: Filip Maj To: dev@cordova.apache.org Reply To: dev@cordova.apache.org *Re: RIM/BlackBerry folk: please help* 2012-11-19 6:46:11 PM 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
Re: RIM/BlackBerry folk: please help
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-webworks.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 m...@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 f...@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 gtan...@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 f...@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 timki...@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*
Re: RIM/BlackBerry folk: please help
Nice thanks Gord. I am hopefully integrating qnx this week into our ci
stuff so I will take a look and review then!
On 11/18/12 7:19 AM, Gord Tanner gtan...@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 m...@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 f...@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 gtan...@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 f...@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 timki...@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*
Re: RIM/BlackBerry folk: please help
So to reproduce I just shell execute ant qnx load-device via a node script? On Wed, Nov 14, 2012 at 3:20 PM, Filip Maj f...@adobe.com wrote: I am working on a continuous integration setup. Got android and iOS working. Now trying to get it working with playbook + BB10. I've tried many avenues to automate the compilation / signing / deployment / launching aspect. Using blackberry-deploy I can launch an app. Hooray! However, I can't sign the app when I shell out to the ant file (ant target build with code.sign=true). I get code signing failed as this package is already signed. If I run this command interactively from my command line it works fine. Perhaps some kind of permission issue with a node process shelling out to ant which in turn fires off to bbwp? Then I tried using the debug tokens instead of signing the app. This is a shitshow in itself. I keep getting author does not match or something along those lines. Tried the various solutions mentioned on the BB support forums [1] and none of them work, including: - Author tag in config.xml matches the debug token author - tablet-sdk/bbwp/bin/bbwp.properties points to the debug token I created and installed on the device I would also recommend reviewing this whole debug token process as it sucks and doesn't work. Echoing the questions in the thread, basically Why do I have to enter my company name in 20 different locations? Any insight into how to fix the author mismatch or automated signing would be helpful. [1] http://supportforums.blackberry.com/t5/Web-and-WebWorks-Development/Applica tion-author-does-not-match-debug-token-author/td-p/1471779
Re: RIM/BlackBerry folk: please help
I'm doing this with playbook. For signing, this works: Edit playbook.xml and set code.sign to true at the top. Then I run ant playbook build Note that it should say signing successful Then tablet-sdkbbwp/blackberry-tablet-sdk/bin/blackberry-deploy -installApp -launchApp -device ip -password device_password path to cordova-bb app/build/appname.bar :: this works and launches on the tablet But if I do the 'ant playbook build' in node via child_process I keep getting: Error: code signing request failed because this file has been previously signed. Note that I am creating a fresh cordova project every time with ./bin/create, and editing the right settings in project.properties. For both the node process and me working with the command line I am using the same generated project. Related: where the fuck did Sample Inc. come from in my app's author??? (when I do ./blackberry-nativepackager -listManifest path to my app.bar) My signing keys and my debug tokens have Adobe as the company name. I will reiterate that this whole debug token process is super annoying and not convenient for devs AT ALL. Way easier to just sign your shit and be on your way. Plus debug tokens expire and you can only be limited to x number of devices with it? Woo security win... On 11/14/12 12:26 PM, Gord Tanner gtan...@gmail.com wrote: So to reproduce I just shell execute ant qnx load-device via a node script? On Wed, Nov 14, 2012 at 3:20 PM, Filip Maj f...@adobe.com wrote: I am working on a continuous integration setup. Got android and iOS working. Now trying to get it working with playbook + BB10. I've tried many avenues to automate the compilation / signing / deployment / launching aspect. Using blackberry-deploy I can launch an app. Hooray! However, I can't sign the app when I shell out to the ant file (ant target build with code.sign=true). I get code signing failed as this package is already signed. If I run this command interactively from my command line it works fine. Perhaps some kind of permission issue with a node process shelling out to ant which in turn fires off to bbwp? Then I tried using the debug tokens instead of signing the app. This is a shitshow in itself. I keep getting author does not match or something along those lines. Tried the various solutions mentioned on the BB support forums [1] and none of them work, including: - Author tag in config.xml matches the debug token author - tablet-sdk/bbwp/bin/bbwp.properties points to the debug token I created and installed on the device I would also recommend reviewing this whole debug token process as it sucks and doesn't work. Echoing the questions in the thread, basically Why do I have to enter my company name in 20 different locations? Any insight into how to fix the author mismatch or automated signing would be helpful. [1] http://supportforums.blackberry.com/t5/Web-and-WebWorks-Development/Appli ca tion-author-does-not-match-debug-token-author/td-p/1471779
Re: RIM/BlackBerry folk: please help
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
