1 person found this helpful
You can't debug AIR apps or Web apps or both? Even with a new simple
I appreciate the response, thanks!
I can debug Flex apps, it is only Air apps, and only apps (even a simple app) built with my
Flex version: 126.96.36.19976 Air version: 2.5 sdk. If I use the installed sdk it is fine.
I suppose this is an Air issue. I posted in that forum as well.
1 person found this helpful
Try getting things running from the command line. I use the following on my
$FLEX_HOME/bin/adl -runtime $FLEX_HOME/runtimes/air/mac $1-app.xml
Set FLEX_HOME to some SDK and pass in the root of an -app.xml file and see
what happens. Make sure AIR is in the runtimes folder.
Thank you for the help.
When I first tried the command line I got an error so I exported the sdk from SVN instead of getting it.
Now I recall that I downloaded the sdk and Air from Adobe because of troubles with getting from SVN.
This is what my command line looked like.
MacBook-Pro:~ claires$ export FLEX_HOME=~/dev/188.8.131.5276
MacBook-Pro:~ claires$ $FLEX_HOME/bin/adl -runtime $FLEX_HOME/runtimes/air/mac $1-app.xml
Let's say I have a simple AIR project call ClaireTest that is stored in
~/projects/ClaireTest. By default, in the bin-debug folder, there should be
a ClaireTest.SWF and ClaireTest-app.xml.
The lines I posted are from a bash shell script I use to run the AIR app.
Suppose I called the shell script db.sh. Then I would type:
Which would resolve to a shell command like:
~/dev/184.108.40.20676/bin/adl -runtime ~/dev/220.127.116.1176/runtimes/air/mac
This should launch your app without the debugger hooking up to it. If you
get that far, open another Terminal window, and type:
This should run the command line debugger. At the prompt type 'r' and hit
Enter. The debugger should say it is waiting to connect. In the other
Terminal window, try to run the app again and see if the command line
debugger hooks up.
This will tell us if most of the pieces are installed correctly. Then if
the FlashBuilder graphical debugger still can't connect, then it is a
FlashBuilder issue of some sort.
If there are missing pieces, you'll get errors along the way and we can try
to figure out what went wrong.
And if the command line debugger works but the graphical one doesn't, at
least you'll have a way to debug. Personally, I believe I am way faster at
finding most problems with the command line debugger than the graphical one.
Alex, this really helped. What I found is that I didn't have a good install of the sdk. I forfeited the install on our server through svn and downloaded Flex 4.1 and Air 2.5 onto my Mac and overlayed the Air files and found the problem was gone. Figuring out the pieces where not all there was the key to resolving the problem.
So, my word to anyone who sees "Process terminated without establishing connection to debugger" and can't figure it, if they keep their sdk files in source control, try downloading the sdk directly from the Adobe and rule out any problem which may be created by svn.
Yay, I am truly grateful this is solved.