Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Adobe AIR Development

Reply
Developer
lrrm
Posts: 306
Registered: ‎03-01-2011
My Device: Playbook (sim)
Accepted Solution

DevAlpha and CodeSigning Issues (the same procedure as every year)

Hi,

 

I'm developing an app for the devAlpha / BB10. Now I want to test it but I'm stuck in this complex code signing process (as always).

 

I've downloaded the Graphical Aid and registered my code signing keys. This went fine according to the feedback the graphical aid gave me. The barsigner.csk was created, I found it somewhere on C:

 

When I try to create a debug token the progress bar pops up and that's when the app stucks. When I try to build a signed bar file the graphical aid gives me a message 'Developer Certificate not configured. Please run configuration wizard.' I've already done this to register the keys.

 

I'm using FlashDevelop with Windows8.

 

What do I have to do to get my app up and running. I've already read the docs but I'm as clever as before.

 

Thanks

lrrm

..................................................................................................................................................................................................................

My App: Peg Solitaire

Need a designer? Drop me a line
BlackBerry Development Advisor
MSohm
Posts: 14,757
Registered: ‎07-09-2008
My Device: BlackBerry Passport

Re: DevAlpha and CodeSigning Issues (the same procedure as every year)

Do you have your author.p12 file located in the %HOMEPATH%\AppData\Local\Research In Motion directory?

 

You can do all of this directly within FlashDevelop now too...

Mark Sohm
BlackBerry Development Advisor

Please refrain from posting new questions in solved threads.
Problem solved? Click the Accept As Solution button.
Found a bug? Report it using Issue Tracker
Developer
lrrm
Posts: 306
Registered: ‎03-01-2011
My Device: Playbook (sim)

Re: DevAlpha and CodeSigning Issues (the same procedure as every year)

[ Edited ]

thanks for your reply.

nope... the graphical aid fails creating an author.p12 ... when I'm running the configuration wizard and click "create certifficate" and enter my data and then click "generate certificate" the button reacts but nothing happens.

do you know a tutorial for FlashDevelop?

edit: maybe it's the same issue with windows 8 like here: http://supportforums.blackberry.com/t5/Testing-and-Deployment/Windows-8-Code-Signing/m-p/2075287#M53...

..................................................................................................................................................................................................................

My App: Peg Solitaire

Need a designer? Drop me a line
BlackBerry Development Advisor
MSohm
Posts: 14,757
Registered: ‎07-09-2008
My Device: BlackBerry Passport

Re: DevAlpha and CodeSigning Issues (the same procedure as every year)

Could be the same issue.  Can you try from a command line?

Mark Sohm
BlackBerry Development Advisor

Please refrain from posting new questions in solved threads.
Problem solved? Click the Accept As Solution button.
Found a bug? Report it using Issue Tracker
Developer
lrrm
Posts: 306
Registered: ‎03-01-2011
My Device: Playbook (sim)

Re: DevAlpha and CodeSigning Issues (the same procedure as every year)

if I enter blackberry-debugtokenrequest in the cmd I get the following error:

 

"'the command java is either written wrong or could not be found."


Java 1.6 is installed two days ago when I set up my machine with windows 8.

..................................................................................................................................................................................................................

My App: Peg Solitaire

Need a designer? Drop me a line
Developer
jtegen
Posts: 6,541
Registered: ‎10-27-2010
My Device: HTC One, PlayBook, LE Z10, DE Q10

Re: DevAlpha and CodeSigning Issues (the same procedure as every year)

Check that the paths are set properly and pointing to the correct JAVA_HOME and BB command directory.
Developer
lrrm
Posts: 306
Registered: ‎03-01-2011
My Device: Playbook (sim)

Re: DevAlpha and CodeSigning Issues (the same procedure as every year)

[ Edited ]

in my environment variables is set following:

 

PATH = D:\RIM\blackberry-tablet-sdk-3.0.0\bin

 

this should be ok as cmd doesn't throw an error about unknown commond or similiar but about java.

 

my java is installed in D:\java 1.6\bin

 

an extension of the path variable to

PATH = D:\RIM\blackberry-tablet-sdk-3.0.0\bin;D:\java 1.6\bin

doesn't work.

 

EDIT:

managed that myself, testing now.

..................................................................................................................................................................................................................

My App: Peg Solitaire

Need a designer? Drop me a line
Developer
jtegen
Posts: 6,541
Registered: ‎10-27-2010
My Device: HTC One, PlayBook, LE Z10, DE Q10

Re: DevAlpha and CodeSigning Issues (the same procedure as every year)

Some people that have other versions of the BB SDK might have that earlier in the path search, so they are invoking the wrong SDK binary.
Developer
lrrm
Posts: 306
Registered: ‎03-01-2011
My Device: Playbook (sim)

Re: DevAlpha and CodeSigning Issues (the same procedure as every year)

ok, I've got it. the path to the jdk was wrong. after that the graphical aid was still reluctant to build an author.p12 file. I did this via command line. creating and installing a debug token worked also only with the command line. installing an app worked with the graphical aid.

thanks a lot!
..................................................................................................................................................................................................................

My App: Peg Solitaire

Need a designer? Drop me a line