04-28-2013 07:58 AM - edited 04-28-2013 07:59 AM
I am exploring Cascades and native. Setup:
Windows 7 English version. Regional setting English US
Simulator BB10_1_X.1483 IP:192.168.56.129
Autodiscover comes up with the following
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
04-30-2013 09:25 AM
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?
05-01-2013 07:51 PM
I got issus while trying to deploy on a simulator ! :s
05-02-2013 03:41 AM
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