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

Native Development

Reply
Developer
ingvar_e
Posts: 551
Registered: ‎10-31-2009
My Device: Torch 9800, Bold 9700
My Carrier: Movistar, Telenor

Problems with debug tokens and..

[ Edited ]

I am exploring  Cascades and native. Setup:

 

Windows 7 English version. Regional setting English US

SDK  10.0.1.1483

Simulator  BB10_1_X.1483      IP:192.168.56.129

 

Autodiscover comes up with the following

 

192.168.56.129

USB Device          169.254.0.1

192.168.56.128        ?????       Where did this come from? I have only one running!

 

New debug tokens generated. They can be uploaded by batch file to the simulator but import says:

"unable to parse expiry date from debug token"

 

Only message is "deploy failed"

 

Have restarted computer just in case but no.

 

This worked yesterday  and I am not aware of any changes except I started on the next sample "Native"

 

Launching gets stuck on 78% "Configuring GDB"

 

Manually importing debug tokens, both old and new ones gets the "unable to parse.." message

 


  

If everything seems to be under control, you're just not driving fast enough
-Mario Andretti-
Please use plain text.
Administrator
MSohm
Posts: 14,241
Registered: ‎07-09-2008
My Device: BlackBerry Z30, BlackBerry PlayBook
My Carrier: Bell

Re: Problems with debug tokens and..

Debug tokens are not required when using the BlackBerry 10 Simulator, only on a real device.

 

Are you getting errors deploying to your device or just the simulator?

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
Please use plain text.
Contributor
devolco
Posts: 16
Registered: ‎05-01-2013
My Device: BB PB & BB curve 8520
My Carrier: Tunisiana

Re: Problems with debug tokens and..

I got issus while trying to deploy on a simulator ! :s

---------------------------------------------------------------------------------------------
1. If any post helps you please thumb's up below .
2. Please resolve your thread by marking the post Solution which solved it for you !!
Please use plain text.
Developer
ingvar_e
Posts: 551
Registered: ‎10-31-2009
My Device: Torch 9800, Bold 9700
My Carrier: Movistar, Telenor

Re: Problems with debug tokens and..

Sorry I forgot this thread. It works now. I am not sure what caused the problem. I am deploying to the simulator. Since the error message was about interpreting a date and it occured when I tried to import the tokens I suspect a a date format problem. I was using 2 computers due to problems with the graphics card on one of them. It might be that the token where generated on a computer with Swedish settings (and date settings) and used on a computer with US settings but I am not sure. After I got the US computer uppgraded with a new graphics card so I can run the simulator on it and also created the tokens on it the problem has disappeared.

 

Using debug tokens was a routine from when I used  Ripple

 

Date formats are tricky things. A couple of years ago I was developing software  with international distribution that had an interface with Excel.

All dates where stored as "long" in the Microsoft format. If I remember  correctly  1 was January 1 1900

 

 

If everything seems to be under control, you're just not driving fast enough
-Mario Andretti-
Please use plain text.