06-16-2013 05:45 PM
I've created many debug tokens manually in the past, but now I get the "debugtokenrequest error: not yet registered to request debug tokens" error.
My C:\Users\dev\AppData\Local\Research In Motion folder contains barsigner.csk, barsigner.db and my .p12 files - the p12 file seems fine as I just signed and uploaded an application into draft mode.
The debug token request is the same as the many others I've created ( just CutnPaste )
I read some of the other comments on this subject , but seems an error with many causes.
Anybody had this error and solved it ?
Solved! Go to Solution.
06-17-2013 09:30 AM
Try looking through this thread on expired debug tokens and faulty .p12 files.
06-17-2013 11:22 AM
yeah I saw that thread thanks, but on checking my barsigner.db I have both an RDK and PBDT entry in the file, looking at when in was genearated I've been using this to generate debugtokens since sept 2011 but the last request was a few months back.
So I'm thinking maybe something server side :/
06-17-2013 11:56 AM
Just to add, if I leave out the .p12 file I get the same error, or if I ask for a .p12 file that doesn't exist then again the same error ( not a very useful error message ), so I'm thinking the .p12 file is fine but the rim tools cant find it ? it's on the same path as it's always been but the PC has been upgraded to win 8 pro from win 7 pro since the last debug token request.
Come to think of it the signer was giving me this error
06-17-2013 12:15 PM
In the BlackBerry Native SDK, click on the Window menu, choose Preferences then expand BlackBerry and choose Signing. Does it show the correct author.p12 file and that the keys are registered?
If it does check the permissions on the directory that stores the keys. I've seen cases where those were sent wrong after upgrading to Windows 8, which prevented our tools from accessing the key files.
06-17-2013 12:41 PM
thanks, not quite a permission thing but having to looking in the folder I can see the barsigner.db was zero bytes, opened it up and it was empty, just replaced it with the back up.
It seems the upgrade had created an empty file ?
Odd but now debug token created, the signing was working because I was using the backup anyway for that in the marmalade deploy tool.
Cheers for that.