04-30-2011 10:00 PM - edited 04-30-2011 10:01 PM
just wanna post my experience -- i've successfully installed the debug tokens and deployed a debug-mode app to the device via wifi. i cant tell you how much i dont trust the IDE (Flash Builder / Burrito) when it comes to registering keys and what not. So i always do the important stuff via command line and this time was no different. It gives me more control and the error messages are more obvious as opposed to letting the IDE handle it.
Here's what i did:
That's my experience -- do the heavy lifting with command line and do the not so disasterous parts in the IDE and it should work like a charm.
also i forgot to mention make sure to use the debug token .csj file and not the other one -- i came close to mixing that up lol
good luck to everyone -- it's a pretty cool feeling after you get this part done -- kind of like a roller coaster you dont want to go on hah
05-01-2011 02:20 PM
if you do all the debug token stuff via the command line, then yes, you can still debug as u normally would via Flash Builder. The debug token serves simply as a key to get into the device and allow unsigned apps to run like from Flash Builder. once you do all the command line stuff you can simply do as you normally would from Flash Builder after setting up the device with its IP address and what not.
05-01-2011 04:49 PM - edited 05-01-2011 06:22 PM
Thanks JRab. I think the key is to use the SAME csk password for both the signing token and the debug token. Flash Builder can't seem to handle two different CSK passwords for signing and debug. I believe the p12 password can be different than the CSK (it can for signing). If you mess up and register with different passwords, then the only alternative I can see it to go get a new SIGNING key and set the password to what ever your developer key was. You can reset the registration of the signing keys by getting a new signing CSJ but I've tried resetting the debug CSJ's and once you set one (presumably against your machine), you are toast. At least re-registring a debug csj doesn't make it invalid like it does for the signing csj's. They need a -deregister command for both so you can start again using your existing CSJ's.
05-09-2011 02:10 PM