You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Gord Tanner <gt...@gmail.com> on 2012/11/22 20:37:21 UTC
Attempting to add debug token support for building on PlayBook
I added debug token support to working on BB10 for cordova and would like
to do the same with playbook but I have the following problem:
Output of cordova build script when running 'ant playbook debug-device'
[exec] Info: Debug token created.
[exec] Info: Sending request: Install and Launch
[exec] Info: Action: Install and Launch
[exec] Info: File size: 2269
[exec] Info: Installing debug.token.gYABgBzNRmtRA7cXnit_yEsmdx4...
[exec] Info: Processing 2269 bytes
[exec] actual_dname::debug.token.gYABgBzNRmtRA7cXnit_yEsmdx4
[exec] actual_id::gYABgBzNRmtRA7cXnit_yEsmdx4
[exec] actual_version::0.0.0.48
[exec] result::success
[exec] Info: Launching debug.token.gYABgBzNRmtRA7cXnit_yEsmdx4...
[exec] result::Invalid
[exec] Info: done
[exec] [INFO] Parsing command line options
[exec] [INFO] Parsing bbwp.properties
[exec] [INFO] Validating WebWorks archive
[exec] [INFO] Parsing config.xml
[exec] [INFO] Populating application source
[exec] [INFO] Compiling WebWorks application
[exec] [INFO] Packaging the bar file
[exec] [INFO] Bar packaging complete
[exec] [INFO] WebWorks application packaging complete
[exec] Info: Sending request: Install and Launch
[exec] Info: Action: Install and Launch
[exec] Info: File size: 510530
[exec] Info: Installing
cordovaExample66daa65d5ab3c8ba4e3a9403c3a28a7.testDev_9403c3a28a75887c750...
[exec] Info: Processing 510530 bytes
[exec] actual_dname::
[exec] actual_id::
[exec] actual_version::
[exec] result::failure 881 application author does not match debug
token author
The value in my config.xml <author> tag is Gord Tanner, which is the same
displayed for the debug token author shown on the playbook.
The ant script I am using is:
<!-- install debug token" -->
+ <macrodef name="generate-debug-token">
+ <sequential>
+ <exec executable="${blackberry-debugtokenrequest}" dir="."
failonerror="true">
+ <arg value="-storepass" />
+ <arg value="${properties.playbook.sigtool.csk.password}" />
+ <arg value="-deviceID" />
+ <arg value="0x${properties.qnx.device.pin}" />
+ <arg file="${properties.qnx.bbwp.dir}/debugtoken.bar" />
+ </exec>
+
+ <exec executable="${blackberry-deploy}" dir="."
failonerror="true">
+ <arg value="-installApp" />
+ <arg value="-launchApp" />
+ <arg value="-device" />
+ <arg value="${properties.playbook.device.ip}" />
+ <arg value="-password" />
+ <arg value="${properties.playbook.device.password}" />
+ <arg value="-package" />
+ <arg file="${properties.qnx.bbwp.dir}/debugtoken.bar" />
+ </exec>
+ </sequential>
+ </macrodef>
Has anyone come across this before?
Re: Attempting to add debug token support for building on PlayBook
Posted by Gord Tanner <gt...@gmail.com>.
Note:
I have since fixed the properties.qnx.bbwp.dir reference for the debugtoken
and it still doesn't work
On Thu, Nov 22, 2012 at 2:37 PM, Gord Tanner <gt...@gmail.com> wrote:
> I added debug token support to working on BB10 for cordova and would like
> to do the same with playbook but I have the following problem:
>
> Output of cordova build script when running 'ant playbook debug-device'
>
> [exec] Info: Debug token created.
> [exec] Info: Sending request: Install and Launch
> [exec] Info: Action: Install and Launch
> [exec] Info: File size: 2269
> [exec] Info: Installing debug.token.gYABgBzNRmtRA7cXnit_yEsmdx4...
> [exec] Info: Processing 2269 bytes
> [exec] actual_dname::debug.token.gYABgBzNRmtRA7cXnit_yEsmdx4
> [exec] actual_id::gYABgBzNRmtRA7cXnit_yEsmdx4
> [exec] actual_version::0.0.0.48
> [exec] result::success
> [exec] Info: Launching debug.token.gYABgBzNRmtRA7cXnit_yEsmdx4...
> [exec] result::Invalid
> [exec] Info: done
> [exec] [INFO] Parsing command line options
> [exec] [INFO] Parsing bbwp.properties
> [exec] [INFO] Validating WebWorks archive
> [exec] [INFO] Parsing config.xml
> [exec] [INFO] Populating application source
> [exec] [INFO] Compiling WebWorks application
> [exec] [INFO] Packaging the bar file
> [exec] [INFO] Bar packaging complete
> [exec] [INFO] WebWorks application packaging complete
> [exec] Info: Sending request: Install and Launch
> [exec] Info: Action: Install and Launch
> [exec] Info: File size: 510530
> [exec] Info: Installing
> cordovaExample66daa65d5ab3c8ba4e3a9403c3a28a7.testDev_9403c3a28a75887c750...
> [exec] Info: Processing 510530 bytes
> [exec] actual_dname::
> [exec] actual_id::
> [exec] actual_version::
> [exec] result::failure 881 application author does not match debug
> token author
>
> The value in my config.xml <author> tag is Gord Tanner, which is the same
> displayed for the debug token author shown on the playbook.
>
> The ant script I am using is:
>
> <!-- install debug token" -->
> + <macrodef name="generate-debug-token">
> + <sequential>
> + <exec executable="${blackberry-debugtokenrequest}" dir="."
> failonerror="true">
> + <arg value="-storepass" />
> + <arg value="${properties.playbook.sigtool.csk.password}"
> />
> + <arg value="-deviceID" />
> + <arg value="0x${properties.qnx.device.pin}" />
> + <arg file="${properties.qnx.bbwp.dir}/debugtoken.bar" />
> + </exec>
> +
> + <exec executable="${blackberry-deploy}" dir="."
> failonerror="true">
> + <arg value="-installApp" />
> + <arg value="-launchApp" />
> + <arg value="-device" />
> + <arg value="${properties.playbook.device.ip}" />
> + <arg value="-password" />
> + <arg value="${properties.playbook.device.password}" />
> + <arg value="-package" />
> + <arg file="${properties.qnx.bbwp.dir}/debugtoken.bar" />
> + </exec>
> + </sequential>
> + </macrodef>
>
> Has anyone come across this before?
>
Re: Attempting to add debug token support for building on PlayBook
Posted by Al Harding <al...@gmail.com>.
On Thu, Nov 22, 2012 at 12:07 PM, Gord Tanner <gt...@gmail.com> wrote:
> wow, so yeah that works.
Schooled! :)
not the best way to do it now ;)
>
> I should be able to automate this in the playbook.xml so our users don't
> have to deal with it.
>
>
>
>
> On Thu, Nov 22, 2012 at 2:46 PM, Filip Maj <fi...@adobe.com> wrote:
>
> > O HELL YEAH I HAVE. Let me, an Adobe employee, give you, a RIM employee,
> > the awesome run down of how to fix this. This is gonna be fun and I get
> to
> > vent a bit too! :D
> >
> > 1. Locate your debug token.
> > 2. Extract the .bar of the debug token with an archive app
> > 3. There will be a META-INF folder
> > 4. Open up META-INF/MANIFEST.MF
> > 5. In there you will see Package-Author and Package-Author-ID. Note down
> > those values.
> > 6. Locate your playbook sdk install dir
> > 7. Go to <sdk>/bbwp/AirAppTemplates/src
> > 8. Edit blackberry-tablet.xml
> > 9. Make sure blackberry-tablet.xml has the following XML elements that
> > match the values in your MANIFEST.MF file of your debug token:
> > - <publisher> should match Package-Author
> > - <author> should match Package-Author
> > - <authorId> should match Package-Author-Id
> > 10. You may have to add some of these elements if they are missing. Yeah.
> > Try figuring that out.
> >
> > I highly recommend RIM fix this as this process is FKN HORSESHIT.
> >
> > That is all. I'm done :)
> >
> > On 11/22/12 11:37 AM, "Gord Tanner" <gt...@gmail.com> wrote:
> >
> > >I added debug token support to working on BB10 for cordova and would
> like
> > >to do the same with playbook but I have the following problem:
> > >
> > >Output of cordova build script when running 'ant playbook debug-device'
> > >
> > >[exec] Info: Debug token created.
> > > [exec] Info: Sending request: Install and Launch
> > > [exec] Info: Action: Install and Launch
> > > [exec] Info: File size: 2269
> > > [exec] Info: Installing debug.token.gYABgBzNRmtRA7cXnit_yEsmdx4...
> > > [exec] Info: Processing 2269 bytes
> > > [exec] actual_dname::debug.token.gYABgBzNRmtRA7cXnit_yEsmdx4
> > > [exec] actual_id::gYABgBzNRmtRA7cXnit_yEsmdx4
> > > [exec] actual_version::0.0.0.48
> > > [exec] result::success
> > > [exec] Info: Launching debug.token.gYABgBzNRmtRA7cXnit_yEsmdx4...
> > > [exec] result::Invalid
> > > [exec] Info: done
> > > [exec] [INFO] Parsing command line options
> > > [exec] [INFO] Parsing bbwp.properties
> > > [exec] [INFO] Validating WebWorks archive
> > > [exec] [INFO] Parsing config.xml
> > > [exec] [INFO] Populating application source
> > > [exec] [INFO] Compiling WebWorks application
> > > [exec] [INFO] Packaging the bar file
> > > [exec] [INFO] Bar packaging complete
> > > [exec] [INFO] WebWorks application packaging complete
> > > [exec] Info: Sending request: Install and Launch
> > > [exec] Info: Action: Install and Launch
> > > [exec] Info: File size: 510530
> > > [exec] Info: Installing
> >
> >cordovaExample66daa65d5ab3c8ba4e3a9403c3a28a7.testDev_9403c3a28a75887c750.
> > >..
> > > [exec] Info: Processing 510530 bytes
> > > [exec] actual_dname::
> > > [exec] actual_id::
> > > [exec] actual_version::
> > > [exec] result::failure 881 application author does not match debug
> > >token author
> > >
> > >The value in my config.xml <author> tag is Gord Tanner, which is the
> same
> > >displayed for the debug token author shown on the playbook.
> > >
> > >The ant script I am using is:
> > >
> > ><!-- install debug token" -->
> > >+ <macrodef name="generate-debug-token">
> > >+ <sequential>
> > >+ <exec executable="${blackberry-debugtokenrequest}" dir="."
> > >failonerror="true">
> > >+ <arg value="-storepass" />
> > >+ <arg
> value="${properties.playbook.sigtool.csk.password}"
> > >/>
> > >+ <arg value="-deviceID" />
> > >+ <arg value="0x${properties.qnx.device.pin}" />
> > >+ <arg file="${properties.qnx.bbwp.dir}/debugtoken.bar"
> />
> > >+ </exec>
> > >+
> > >+ <exec executable="${blackberry-deploy}" dir="."
> > >failonerror="true">
> > >+ <arg value="-installApp" />
> > >+ <arg value="-launchApp" />
> > >+ <arg value="-device" />
> > >+ <arg value="${properties.playbook.device.ip}" />
> > >+ <arg value="-password" />
> > >+ <arg value="${properties.playbook.device.password}" />
> > >+ <arg value="-package" />
> > >+ <arg file="${properties.qnx.bbwp.dir}/debugtoken.bar"
> />
> > >+ </exec>
> > >+ </sequential>
> > >+ </macrodef>
> > >
> > >Has anyone come across this before?
> >
> >
>
Re: Attempting to add debug token support for building on PlayBook
Posted by Tim Kim <ti...@gmail.com>.
Sure, I'll give it a shot.
On 26 November 2012 07:05, Gord Tanner <gt...@gmail.com> wrote:
> Did this work for you Fil?
>
> Tim, could you give this a try on a playbook. I am getting strong "but it
> works on my machine" vibes and I don't want to mark this as done without at
> least one other person verifying that it works.
>
>
> On Fri, Nov 23, 2012 at 12:07 PM, Gord Tanner <gt...@gmail.com> wrote:
>
> > seems to work for me (just double checked to make sure my
> > blackberry-tablet.xml wasn't updated)
> >
> >
> >
> > On Fri, Nov 23, 2012 at 12:03 PM, Filip Maj <fi...@adobe.com> wrote:
> >
> >> I tried the path thing initially but it didn't work..
> >>
> >> On 11/23/12 8:35 AM, "Gord Tanner" <gt...@gmail.com> wrote:
> >>
> >> >Ok,
> >> >
> >> >debug token support added to playbook:
> >> >
> >>
> https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;a=commitd
> >> >iff;h=ef16d935bf08e0baaa8c1d875edd5af76c856f1f
> >> >
> >> >Let us never speak of this again.
> >> >
> >> >This should make the CI stuff for Fil suck a whole lot less.
> >> >
> >> >
> >> >On Fri, Nov 23, 2012 at 10:43 AM, Gord Tanner <gt...@gmail.com>
> wrote:
> >> >
> >> >> So I found out it doesn't suck as bad as we all thought ;)
> >> >>
> >> >> From:
> >> >>
> >> >>
> >> >>
> >>
> https://developer.blackberry.com/html5/documentation/runnning_unsigned_ap
> >> >>ps_using_a_debug_token_1866987_11.html
> >> >>
> >> >> It looks like all we need to do is provide the path to the debug
> token
> >> >>in
> >> >> the bbwp.properties file.
> >> >>
> >> >> I tested this on my playbook and was able to deploy to it. This is a
> >> lot
> >> >> easier to automate in the build script then the Rube Goldburg machine
> >> >> mentioned above.
> >> >>
> >> >>
> >> >> From the link:
> >> >>
> >> >>
> >> >> 1. In the BlackBerry WebWorks SDK for BlackBerry Tablet
> >> >> OS installation folder, navigate to the*bbwp\bin* folder.
> >> >> 2. Using a text editor, open the bbwp.properties file.
> >> >> 3. Add the path to the debug token file by using <debug_token>
> tags.
> >> >>
> >> >>
> >> >> <debug_token>path to debug token file</debug_token>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> On Thu, Nov 22, 2012 at 3:51 PM, Josh Soref <js...@rim.com> wrote:
> >> >>
> >> >>> Gord wrote:
> >> >>> > not the best way to do it now ;)
> >> >>> >
> >> >>> > I should be able to automate this in the playbook.xml so our users
> >> >>>don't
> >> >>> > have to deal with it.
> >> >>>
> >> >>> The way I'm told is to just remove those items from the PlayBook.xml
> >> >>>file
> >> >>> entirely and just rely on the packager/debugtoken to magically set
> >> >>>them or
> >> >>> somehow make it work.
> >> >>>
> >> >>> (this was advice I got from non-RIM people, to me,...)
> >> >>>
> >> >>>
> ---------------------------------------------------------------------
> >> >>> This transmission (including any attachments) may contain
> confidential
> >> >>> information, privileged material (including material protected by
> the
> >> >>> solicitor-client or other applicable privileges), or constitute
> >> >>>non-public
> >> >>> information. Any use of this information by anyone other than the
> >> >>>intended
> >> >>> recipient is prohibited. If you have received this transmission in
> >> >>>error,
> >> >>> please immediately reply to the sender and delete this information
> >> from
> >> >>> your system. Use, dissemination, distribution, or reproduction of
> this
> >> >>> transmission by unintended recipients is not authorized and may be
> >> >>>unlawful.
> >> >>>
> >> >>
> >> >>
> >>
> >>
> >
>
--
Timothy Kim
Re: Attempting to add debug token support for building on PlayBook
Posted by Gord Tanner <gt...@gmail.com>.
Did this work for you Fil?
Tim, could you give this a try on a playbook. I am getting strong "but it
works on my machine" vibes and I don't want to mark this as done without at
least one other person verifying that it works.
On Fri, Nov 23, 2012 at 12:07 PM, Gord Tanner <gt...@gmail.com> wrote:
> seems to work for me (just double checked to make sure my
> blackberry-tablet.xml wasn't updated)
>
>
>
> On Fri, Nov 23, 2012 at 12:03 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> I tried the path thing initially but it didn't work..
>>
>> On 11/23/12 8:35 AM, "Gord Tanner" <gt...@gmail.com> wrote:
>>
>> >Ok,
>> >
>> >debug token support added to playbook:
>> >
>> https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;a=commitd
>> >iff;h=ef16d935bf08e0baaa8c1d875edd5af76c856f1f
>> >
>> >Let us never speak of this again.
>> >
>> >This should make the CI stuff for Fil suck a whole lot less.
>> >
>> >
>> >On Fri, Nov 23, 2012 at 10:43 AM, Gord Tanner <gt...@gmail.com> wrote:
>> >
>> >> So I found out it doesn't suck as bad as we all thought ;)
>> >>
>> >> From:
>> >>
>> >>
>> >>
>> https://developer.blackberry.com/html5/documentation/runnning_unsigned_ap
>> >>ps_using_a_debug_token_1866987_11.html
>> >>
>> >> It looks like all we need to do is provide the path to the debug token
>> >>in
>> >> the bbwp.properties file.
>> >>
>> >> I tested this on my playbook and was able to deploy to it. This is a
>> lot
>> >> easier to automate in the build script then the Rube Goldburg machine
>> >> mentioned above.
>> >>
>> >>
>> >> From the link:
>> >>
>> >>
>> >> 1. In the BlackBerry WebWorks SDK for BlackBerry Tablet
>> >> OS installation folder, navigate to the*bbwp\bin* folder.
>> >> 2. Using a text editor, open the bbwp.properties file.
>> >> 3. Add the path to the debug token file by using <debug_token> tags.
>> >>
>> >>
>> >> <debug_token>path to debug token file</debug_token>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> On Thu, Nov 22, 2012 at 3:51 PM, Josh Soref <js...@rim.com> wrote:
>> >>
>> >>> Gord wrote:
>> >>> > not the best way to do it now ;)
>> >>> >
>> >>> > I should be able to automate this in the playbook.xml so our users
>> >>>don't
>> >>> > have to deal with it.
>> >>>
>> >>> The way I'm told is to just remove those items from the PlayBook.xml
>> >>>file
>> >>> entirely and just rely on the packager/debugtoken to magically set
>> >>>them or
>> >>> somehow make it work.
>> >>>
>> >>> (this was advice I got from non-RIM people, to me,...)
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> This transmission (including any attachments) may contain confidential
>> >>> information, privileged material (including material protected by the
>> >>> solicitor-client or other applicable privileges), or constitute
>> >>>non-public
>> >>> information. Any use of this information by anyone other than the
>> >>>intended
>> >>> recipient is prohibited. If you have received this transmission in
>> >>>error,
>> >>> please immediately reply to the sender and delete this information
>> from
>> >>> your system. Use, dissemination, distribution, or reproduction of this
>> >>> transmission by unintended recipients is not authorized and may be
>> >>>unlawful.
>> >>>
>> >>
>> >>
>>
>>
>
Re: Attempting to add debug token support for building on PlayBook
Posted by Gord Tanner <gt...@gmail.com>.
seems to work for me (just double checked to make sure my
blackberry-tablet.xml wasn't updated)
On Fri, Nov 23, 2012 at 12:03 PM, Filip Maj <fi...@adobe.com> wrote:
> I tried the path thing initially but it didn't work..
>
> On 11/23/12 8:35 AM, "Gord Tanner" <gt...@gmail.com> wrote:
>
> >Ok,
> >
> >debug token support added to playbook:
> >
> https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;a=commitd
> >iff;h=ef16d935bf08e0baaa8c1d875edd5af76c856f1f
> >
> >Let us never speak of this again.
> >
> >This should make the CI stuff for Fil suck a whole lot less.
> >
> >
> >On Fri, Nov 23, 2012 at 10:43 AM, Gord Tanner <gt...@gmail.com> wrote:
> >
> >> So I found out it doesn't suck as bad as we all thought ;)
> >>
> >> From:
> >>
> >>
> >>
> https://developer.blackberry.com/html5/documentation/runnning_unsigned_ap
> >>ps_using_a_debug_token_1866987_11.html
> >>
> >> It looks like all we need to do is provide the path to the debug token
> >>in
> >> the bbwp.properties file.
> >>
> >> I tested this on my playbook and was able to deploy to it. This is a lot
> >> easier to automate in the build script then the Rube Goldburg machine
> >> mentioned above.
> >>
> >>
> >> From the link:
> >>
> >>
> >> 1. In the BlackBerry WebWorks SDK for BlackBerry Tablet
> >> OS installation folder, navigate to the*bbwp\bin* folder.
> >> 2. Using a text editor, open the bbwp.properties file.
> >> 3. Add the path to the debug token file by using <debug_token> tags.
> >>
> >>
> >> <debug_token>path to debug token file</debug_token>
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Thu, Nov 22, 2012 at 3:51 PM, Josh Soref <js...@rim.com> wrote:
> >>
> >>> Gord wrote:
> >>> > not the best way to do it now ;)
> >>> >
> >>> > I should be able to automate this in the playbook.xml so our users
> >>>don't
> >>> > have to deal with it.
> >>>
> >>> The way I'm told is to just remove those items from the PlayBook.xml
> >>>file
> >>> entirely and just rely on the packager/debugtoken to magically set
> >>>them or
> >>> somehow make it work.
> >>>
> >>> (this was advice I got from non-RIM people, to me,...)
> >>>
> >>> ---------------------------------------------------------------------
> >>> This transmission (including any attachments) may contain confidential
> >>> information, privileged material (including material protected by the
> >>> solicitor-client or other applicable privileges), or constitute
> >>>non-public
> >>> information. Any use of this information by anyone other than the
> >>>intended
> >>> recipient is prohibited. If you have received this transmission in
> >>>error,
> >>> please immediately reply to the sender and delete this information from
> >>> your system. Use, dissemination, distribution, or reproduction of this
> >>> transmission by unintended recipients is not authorized and may be
> >>>unlawful.
> >>>
> >>
> >>
>
>
Re: Attempting to add debug token support for building on PlayBook
Posted by Filip Maj <fi...@adobe.com>.
I tried the path thing initially but it didn't work..
On 11/23/12 8:35 AM, "Gord Tanner" <gt...@gmail.com> wrote:
>Ok,
>
>debug token support added to playbook:
>https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;a=commitd
>iff;h=ef16d935bf08e0baaa8c1d875edd5af76c856f1f
>
>Let us never speak of this again.
>
>This should make the CI stuff for Fil suck a whole lot less.
>
>
>On Fri, Nov 23, 2012 at 10:43 AM, Gord Tanner <gt...@gmail.com> wrote:
>
>> So I found out it doesn't suck as bad as we all thought ;)
>>
>> From:
>>
>>
>>https://developer.blackberry.com/html5/documentation/runnning_unsigned_ap
>>ps_using_a_debug_token_1866987_11.html
>>
>> It looks like all we need to do is provide the path to the debug token
>>in
>> the bbwp.properties file.
>>
>> I tested this on my playbook and was able to deploy to it. This is a lot
>> easier to automate in the build script then the Rube Goldburg machine
>> mentioned above.
>>
>>
>> From the link:
>>
>>
>> 1. In the BlackBerry WebWorks SDK for BlackBerry Tablet
>> OS installation folder, navigate to the*bbwp\bin* folder.
>> 2. Using a text editor, open the bbwp.properties file.
>> 3. Add the path to the debug token file by using <debug_token> tags.
>>
>>
>> <debug_token>path to debug token file</debug_token>
>>
>>
>>
>>
>>
>>
>> On Thu, Nov 22, 2012 at 3:51 PM, Josh Soref <js...@rim.com> wrote:
>>
>>> Gord wrote:
>>> > not the best way to do it now ;)
>>> >
>>> > I should be able to automate this in the playbook.xml so our users
>>>don't
>>> > have to deal with it.
>>>
>>> The way I'm told is to just remove those items from the PlayBook.xml
>>>file
>>> entirely and just rely on the packager/debugtoken to magically set
>>>them or
>>> somehow make it work.
>>>
>>> (this was advice I got from non-RIM people, to me,...)
>>>
>>> ---------------------------------------------------------------------
>>> This transmission (including any attachments) may contain confidential
>>> information, privileged material (including material protected by the
>>> solicitor-client or other applicable privileges), or constitute
>>>non-public
>>> information. Any use of this information by anyone other than the
>>>intended
>>> recipient is prohibited. If you have received this transmission in
>>>error,
>>> please immediately reply to the sender and delete this information from
>>> your system. Use, dissemination, distribution, or reproduction of this
>>> transmission by unintended recipients is not authorized and may be
>>>unlawful.
>>>
>>
>>
Re: Attempting to add debug token support for building on PlayBook
Posted by Gord Tanner <gt...@gmail.com>.
Ok,
debug token support added to playbook:
https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;a=commitdiff;h=ef16d935bf08e0baaa8c1d875edd5af76c856f1f
Let us never speak of this again.
This should make the CI stuff for Fil suck a whole lot less.
On Fri, Nov 23, 2012 at 10:43 AM, Gord Tanner <gt...@gmail.com> wrote:
> So I found out it doesn't suck as bad as we all thought ;)
>
> From:
>
> https://developer.blackberry.com/html5/documentation/runnning_unsigned_apps_using_a_debug_token_1866987_11.html
>
> It looks like all we need to do is provide the path to the debug token in
> the bbwp.properties file.
>
> I tested this on my playbook and was able to deploy to it. This is a lot
> easier to automate in the build script then the Rube Goldburg machine
> mentioned above.
>
>
> From the link:
>
>
> 1. In the BlackBerry WebWorks SDK for BlackBerry Tablet
> OS installation folder, navigate to the*bbwp\bin* folder.
> 2. Using a text editor, open the bbwp.properties file.
> 3. Add the path to the debug token file by using <debug_token> tags.
>
>
> <debug_token>path to debug token file</debug_token>
>
>
>
>
>
>
> On Thu, Nov 22, 2012 at 3:51 PM, Josh Soref <js...@rim.com> wrote:
>
>> Gord wrote:
>> > not the best way to do it now ;)
>> >
>> > I should be able to automate this in the playbook.xml so our users don't
>> > have to deal with it.
>>
>> The way I'm told is to just remove those items from the PlayBook.xml file
>> entirely and just rely on the packager/debugtoken to magically set them or
>> somehow make it work.
>>
>> (this was advice I got from non-RIM people, to me,...)
>>
>> ---------------------------------------------------------------------
>> This transmission (including any attachments) may contain confidential
>> information, privileged material (including material protected by the
>> solicitor-client or other applicable privileges), or constitute non-public
>> information. Any use of this information by anyone other than the intended
>> recipient is prohibited. If you have received this transmission in error,
>> please immediately reply to the sender and delete this information from
>> your system. Use, dissemination, distribution, or reproduction of this
>> transmission by unintended recipients is not authorized and may be unlawful.
>>
>
>
Re: Attempting to add debug token support for building on PlayBook
Posted by Gord Tanner <gt...@gmail.com>.
So I found out it doesn't suck as bad as we all thought ;)
From:
https://developer.blackberry.com/html5/documentation/runnning_unsigned_apps_using_a_debug_token_1866987_11.html
It looks like all we need to do is provide the path to the debug token in
the bbwp.properties file.
I tested this on my playbook and was able to deploy to it. This is a lot
easier to automate in the build script then the Rube Goldburg machine
mentioned above.
>From the link:
1. In the BlackBerry WebWorks SDK for BlackBerry Tablet OS installation
folder, navigate to the*bbwp\bin* folder.
2. Using a text editor, open the bbwp.properties file.
3. Add the path to the debug token file by using <debug_token> tags.
<debug_token>path to debug token file</debug_token>
On Thu, Nov 22, 2012 at 3:51 PM, Josh Soref <js...@rim.com> wrote:
> Gord wrote:
> > not the best way to do it now ;)
> >
> > I should be able to automate this in the playbook.xml so our users don't
> > have to deal with it.
>
> The way I'm told is to just remove those items from the PlayBook.xml file
> entirely and just rely on the packager/debugtoken to magically set them or
> somehow make it work.
>
> (this was advice I got from non-RIM people, to me,...)
>
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-public
> information. Any use of this information by anyone other than the intended
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be unlawful.
>
RE: Attempting to add debug token support for building on PlayBook
Posted by Josh Soref <js...@rim.com>.
Gord wrote:
> not the best way to do it now ;)
>
> I should be able to automate this in the playbook.xml so our users don't
> have to deal with it.
The way I'm told is to just remove those items from the PlayBook.xml file entirely and just rely on the packager/debugtoken to magically set them or somehow make it work.
(this was advice I got from non-RIM people, to me,...)
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Re: Attempting to add debug token support for building on PlayBook
Posted by Gord Tanner <gt...@gmail.com>.
wow, so yeah that works.
not the best way to do it now ;)
I should be able to automate this in the playbook.xml so our users don't
have to deal with it.
On Thu, Nov 22, 2012 at 2:46 PM, Filip Maj <fi...@adobe.com> wrote:
> O HELL YEAH I HAVE. Let me, an Adobe employee, give you, a RIM employee,
> the awesome run down of how to fix this. This is gonna be fun and I get to
> vent a bit too! :D
>
> 1. Locate your debug token.
> 2. Extract the .bar of the debug token with an archive app
> 3. There will be a META-INF folder
> 4. Open up META-INF/MANIFEST.MF
> 5. In there you will see Package-Author and Package-Author-ID. Note down
> those values.
> 6. Locate your playbook sdk install dir
> 7. Go to <sdk>/bbwp/AirAppTemplates/src
> 8. Edit blackberry-tablet.xml
> 9. Make sure blackberry-tablet.xml has the following XML elements that
> match the values in your MANIFEST.MF file of your debug token:
> - <publisher> should match Package-Author
> - <author> should match Package-Author
> - <authorId> should match Package-Author-Id
> 10. You may have to add some of these elements if they are missing. Yeah.
> Try figuring that out.
>
> I highly recommend RIM fix this as this process is FKN HORSESHIT.
>
> That is all. I'm done :)
>
> On 11/22/12 11:37 AM, "Gord Tanner" <gt...@gmail.com> wrote:
>
> >I added debug token support to working on BB10 for cordova and would like
> >to do the same with playbook but I have the following problem:
> >
> >Output of cordova build script when running 'ant playbook debug-device'
> >
> >[exec] Info: Debug token created.
> > [exec] Info: Sending request: Install and Launch
> > [exec] Info: Action: Install and Launch
> > [exec] Info: File size: 2269
> > [exec] Info: Installing debug.token.gYABgBzNRmtRA7cXnit_yEsmdx4...
> > [exec] Info: Processing 2269 bytes
> > [exec] actual_dname::debug.token.gYABgBzNRmtRA7cXnit_yEsmdx4
> > [exec] actual_id::gYABgBzNRmtRA7cXnit_yEsmdx4
> > [exec] actual_version::0.0.0.48
> > [exec] result::success
> > [exec] Info: Launching debug.token.gYABgBzNRmtRA7cXnit_yEsmdx4...
> > [exec] result::Invalid
> > [exec] Info: done
> > [exec] [INFO] Parsing command line options
> > [exec] [INFO] Parsing bbwp.properties
> > [exec] [INFO] Validating WebWorks archive
> > [exec] [INFO] Parsing config.xml
> > [exec] [INFO] Populating application source
> > [exec] [INFO] Compiling WebWorks application
> > [exec] [INFO] Packaging the bar file
> > [exec] [INFO] Bar packaging complete
> > [exec] [INFO] WebWorks application packaging complete
> > [exec] Info: Sending request: Install and Launch
> > [exec] Info: Action: Install and Launch
> > [exec] Info: File size: 510530
> > [exec] Info: Installing
> >cordovaExample66daa65d5ab3c8ba4e3a9403c3a28a7.testDev_9403c3a28a75887c750.
> >..
> > [exec] Info: Processing 510530 bytes
> > [exec] actual_dname::
> > [exec] actual_id::
> > [exec] actual_version::
> > [exec] result::failure 881 application author does not match debug
> >token author
> >
> >The value in my config.xml <author> tag is Gord Tanner, which is the same
> >displayed for the debug token author shown on the playbook.
> >
> >The ant script I am using is:
> >
> ><!-- install debug token" -->
> >+ <macrodef name="generate-debug-token">
> >+ <sequential>
> >+ <exec executable="${blackberry-debugtokenrequest}" dir="."
> >failonerror="true">
> >+ <arg value="-storepass" />
> >+ <arg value="${properties.playbook.sigtool.csk.password}"
> >/>
> >+ <arg value="-deviceID" />
> >+ <arg value="0x${properties.qnx.device.pin}" />
> >+ <arg file="${properties.qnx.bbwp.dir}/debugtoken.bar" />
> >+ </exec>
> >+
> >+ <exec executable="${blackberry-deploy}" dir="."
> >failonerror="true">
> >+ <arg value="-installApp" />
> >+ <arg value="-launchApp" />
> >+ <arg value="-device" />
> >+ <arg value="${properties.playbook.device.ip}" />
> >+ <arg value="-password" />
> >+ <arg value="${properties.playbook.device.password}" />
> >+ <arg value="-package" />
> >+ <arg file="${properties.qnx.bbwp.dir}/debugtoken.bar" />
> >+ </exec>
> >+ </sequential>
> >+ </macrodef>
> >
> >Has anyone come across this before?
>
>
Re: Attempting to add debug token support for building on PlayBook
Posted by Filip Maj <fi...@adobe.com>.
O HELL YEAH I HAVE. Let me, an Adobe employee, give you, a RIM employee,
the awesome run down of how to fix this. This is gonna be fun and I get to
vent a bit too! :D
1. Locate your debug token.
2. Extract the .bar of the debug token with an archive app
3. There will be a META-INF folder
4. Open up META-INF/MANIFEST.MF
5. In there you will see Package-Author and Package-Author-ID. Note down
those values.
6. Locate your playbook sdk install dir
7. Go to <sdk>/bbwp/AirAppTemplates/src
8. Edit blackberry-tablet.xml
9. Make sure blackberry-tablet.xml has the following XML elements that
match the values in your MANIFEST.MF file of your debug token:
- <publisher> should match Package-Author
- <author> should match Package-Author
- <authorId> should match Package-Author-Id
10. You may have to add some of these elements if they are missing. Yeah.
Try figuring that out.
I highly recommend RIM fix this as this process is FKN HORSESHIT.
That is all. I'm done :)
On 11/22/12 11:37 AM, "Gord Tanner" <gt...@gmail.com> wrote:
>I added debug token support to working on BB10 for cordova and would like
>to do the same with playbook but I have the following problem:
>
>Output of cordova build script when running 'ant playbook debug-device'
>
>[exec] Info: Debug token created.
> [exec] Info: Sending request: Install and Launch
> [exec] Info: Action: Install and Launch
> [exec] Info: File size: 2269
> [exec] Info: Installing debug.token.gYABgBzNRmtRA7cXnit_yEsmdx4...
> [exec] Info: Processing 2269 bytes
> [exec] actual_dname::debug.token.gYABgBzNRmtRA7cXnit_yEsmdx4
> [exec] actual_id::gYABgBzNRmtRA7cXnit_yEsmdx4
> [exec] actual_version::0.0.0.48
> [exec] result::success
> [exec] Info: Launching debug.token.gYABgBzNRmtRA7cXnit_yEsmdx4...
> [exec] result::Invalid
> [exec] Info: done
> [exec] [INFO] Parsing command line options
> [exec] [INFO] Parsing bbwp.properties
> [exec] [INFO] Validating WebWorks archive
> [exec] [INFO] Parsing config.xml
> [exec] [INFO] Populating application source
> [exec] [INFO] Compiling WebWorks application
> [exec] [INFO] Packaging the bar file
> [exec] [INFO] Bar packaging complete
> [exec] [INFO] WebWorks application packaging complete
> [exec] Info: Sending request: Install and Launch
> [exec] Info: Action: Install and Launch
> [exec] Info: File size: 510530
> [exec] Info: Installing
>cordovaExample66daa65d5ab3c8ba4e3a9403c3a28a7.testDev_9403c3a28a75887c750.
>..
> [exec] Info: Processing 510530 bytes
> [exec] actual_dname::
> [exec] actual_id::
> [exec] actual_version::
> [exec] result::failure 881 application author does not match debug
>token author
>
>The value in my config.xml <author> tag is Gord Tanner, which is the same
>displayed for the debug token author shown on the playbook.
>
>The ant script I am using is:
>
><!-- install debug token" -->
>+ <macrodef name="generate-debug-token">
>+ <sequential>
>+ <exec executable="${blackberry-debugtokenrequest}" dir="."
>failonerror="true">
>+ <arg value="-storepass" />
>+ <arg value="${properties.playbook.sigtool.csk.password}"
>/>
>+ <arg value="-deviceID" />
>+ <arg value="0x${properties.qnx.device.pin}" />
>+ <arg file="${properties.qnx.bbwp.dir}/debugtoken.bar" />
>+ </exec>
>+
>+ <exec executable="${blackberry-deploy}" dir="."
>failonerror="true">
>+ <arg value="-installApp" />
>+ <arg value="-launchApp" />
>+ <arg value="-device" />
>+ <arg value="${properties.playbook.device.ip}" />
>+ <arg value="-password" />
>+ <arg value="${properties.playbook.device.password}" />
>+ <arg value="-package" />
>+ <arg file="${properties.qnx.bbwp.dir}/debugtoken.bar" />
>+ </exec>
>+ </sequential>
>+ </macrodef>
>
>Has anyone come across this before?