Ah, sorry. Forgot that this is a mobile test so you can't just launch it in FDB because it needs AIR.
I have tried a couple of different workflows for mobile. For this test, I started fdb and just typed run. Then I went to the mustella folder, typed ./mini_run.sh -rerun -timeout-60000 and whatever you used to run the test. Mustella will skip the compile and run the test and now you have 60 seconds before it quits the test to debug it. Sometimes, 60 seconds isn't long enough, so I do the above and then in Finder I go and find the -app.xml file in the SWFs folder and make a copy of it in that 60 second window. It may just be named .xml instead of -app.xml. Then I can go run fdb again, type run, then go to another window and run adl with the correct params and then I should be able to spend all day in the debugger. I think the following command line should work on your mac: $AIR_HOME/bin/adl -runtime $AIR_HOME/runtimes/air/mac adl_extras=-screensize 640x960:640x960 -profile mobileDevice -XscreenDPI 240 <path to -app.xml> FWIW, tests in the AIR run can be run with a keep option which saves the -app.xml, but for some reason, mobile tests can't. Hope that works for you, -Alex On 9/8/13 9:09 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: >Hi, > >> From Finder or FB or command-line? >command line. > >$fdb >(fdb) run SkinnablePopUpContainerSKEffects.swf >Attempting to launch and connect to Player using URL >SkinnablePopUpContainerSKEffects.swf > >This result in the same blank swf: >fdb ./tests/mobile/SkinnablePopupContainerSK/ss/*.swf > >Attempting to launch and connect to Player using URL >./tests/mobile/SkinnablePopupContainerSK/swfs/SkinnablePopUpContainerSKEff >ects.swf > >Also running fdb just trying run and running the swf almost works >(fdb) run >Waiting for Player to connect >Player connected; session starting. >Set breakpoints and then type 'continue' to resume the session. >[SWF] SkinnablePopUpContainerSKEffects.swf - 4,192,841 bytes after >decompression > >But the tests time out before you have a chance to set breakpoints. > >> Does the Standalone Debugger launch or some browser? >Standalone debugger starts but is blank, with the correct path to the swf > is in the title. > >Justin