12-02-2012 06:59 AM
If you are using Windows 8 and getting weird errors concerning code-signing then please read this...
It took me two long, long days to get to the bottom of this...
Basically if you use the code signing UI or command-line to register your signing keys it fails with really weird errors.
The clue of course (looking back) was when the UI states it cannot find the .csk file after it seems to successfully register with RIM.
Anyway cutting a long story short (because I really need to get back to coding my BB10 killer application ;-) of course) the culprit is the tool "blackberry-signer" which is supposed to store the .csk file in the following directory;
C:\Users\YourUser\Local Settings\Application Data\Research In Motion
as this is where everything else is stored and indeed where it is stored on Windows editions prior to Windows 8.
However it turns out that in Windows 8 it actually stores the .csk file in this directory;
C:\Users\YourUser\AppData\Local\Research In Motion
I didn't have time to work out which files should be in which folder; I just make sure that all the code-signing files are in both locations and now it works.
I can now issue debug tokens and my world is now a happy place...
Hope this saves someone bacon!
12-06-2012 04:33 PM
Thanks for reporting this. I've logged it in Issue Tracker and reported it to our internal development team.
01-04-2013 01:46 PM - edited 01-04-2013 01:59 PM
06-21-2013 06:18 AM
Thanks a lot for sharing. Unfortunately I wasted a few hours trying to find a solution for "Error: not yet registered to request debug tokens" before I found this article.
As this is a known bug since a very long time, I am wondering why BlackBerry doesn't fix it.
06-21-2013 09:22 AM
The comments in Issue Tracker for that issue appear to be broken. It was determined that this wasn't a bug but a problem from running the application in Windows XP compatibility mode, which causes barsigner to place the files in the location for Windows XP.