10-27-2010 12:40 AM - edited 10-27-2010 12:41 AM
I'm running via command line, and can't see any traces in the console... The app launches on the simulator fine, I can see the initial stage, what am I missing here??
I tried using -target bar-debug but no luck.
10-27-2010 04:57 PM
So the trick is to create a remote debugging session, and pass "-connect 192.x.x.x" in the compile settings.
I'm just not sure how to start the debugging session from FlashBuilder... I found some tricks for a MXML project, but not for a pure AS one...
10-27-2010 10:16 PM
SDK installs plugins for Flash Builder, so you should have Launch configuration called BlackBerry Air Application - if you create it - you just use it in Debug mode. If you don't have it - something is wrong with installation
10-27-2010 11:29 PM - edited 10-27-2010 11:43 PM
Whenever I am in a situation where I have to test without a debug version of the player, I always do one of two things:
1. Create a separate application that I can localConnection into and send all of my trace data there, rather than using trace().
2. Create a simple TextArea that can easily be removed or commented out for final release and have that accessible, but all of the text to be traced gets pushed into that window.
I know this might not apply to you, but I thought you might find it helpful in case you have a hard time getting trace to actually work. If you do, please let me know how you did it.
10-27-2010 11:35 PM
Well I have 4.0, which the debug option won't appear in (I copied the .ink file), and I downloaded 4.5 and can add a debug config, but it throws an error when deploying
An internal error occurred during: "Launching BlackberryHello (1)".
Works fine when I use a custom run command... I really don't want to download a 3rd version of FB :/
10-28-2010 08:29 AM - edited 10-28-2010 08:42 AM
You should stay out of threads if you don't have a clue to the proper answer, how about that?
All we need is to be able to start a remote debug session, and we can easily deploy via command line, instead of relying on some half broken GUI, or requiring a minor dot release of FB.
12-12-2010 12:51 PM
12-12-2010 01:30 PM
I too get trace() to work sometimes and getting the remote debug to work from the simulator has been problematic. Though I still have trouble getting my environment to work to debug from the simulator, local debug has been nice by using Alcon (http://blog.hexagonstar.com/downloads/alcon/). Other than levels of debug, it shows continuous on FPS and memory usage, plus it has a nice object inspector that shows an object in a tree form. Very simple library to install and API.
The author mentioned he is working on a remote connection. If you like the tool, let him know you too would be interested in a remote debug control session.