I restarted, and checked my firewall settings.  It was off.  I turned it on
and made sure FlashBuilder was set to allow incoming connections.  I also
added adl to that list.  Still no go.  Turned it back off, still nothing.
 Both mobile and web debugging are stuck at 57%.

Is there a certain socket debugging happens on?  Surely I can't be the only
person running into this.

Thanks!

-Jake


On Wed, Jan 22, 2014 at 5:54 PM, Alex Harui <aha...@adobe.com> wrote:

> OK.  Restart the computer to free up any stuck sockets.
>
> If it still doesn't work, I would begin to wonder if there is a firewall
> blocking the application's access to sockets.  Here is a related article.
> No idea if it applies to Mavericks.
>
> http://www.macworld.com/article/1135888/firewalls.html
>
> -Alex
>
> On 1/22/14 3:03 PM, "Jake Churchill" <reyna...@gmail.com> wrote:
>
> >Brand new app with a label centered with "TEST" in it.  Still hangs at
> >57%.
> > I do have flash player debugger version installed.  Have tried Chrome and
> >Safari.  For Chrome, I had to disable the built-in flash plugin but both
> >showed debugger Yes on that test site.
> >
> >I went ahead and created a blank mobile project as well and tried to debug
> >in the emulator and stuck at 57%.
> >
> >-Jake
> >
> >
> >
> >On Wed, Jan 22, 2014 at 4:49 PM, Alex Harui <aha...@adobe.com> wrote:
> >
> >> Jake,
> >>
> >> Let's start with debugging a web app.  First, is this a brand new
> >> workspace or did you copy one from the old machine?  If it is old,
> >>create
> >> a new workspace and create a test case project in it.
> >>
> >> Next, using the browser that you've chosen for FB debug configs, go to
> >> flashplayersion.com.  Does it say you have a debugger player?
> >>
> >> -Alex
> >>
> >> On 1/22/14 1:43 PM, "Jake Churchill" <reyna...@gmail.com> wrote:
> >>
> >> >I recently upgraded my mac to 10.9 by way of purchasing a new mac, not
> >> >upgrading an existing.  I installed all the usual XCode, FlashBuilder
> >>4.7,
> >> >etc.  I noticed that I cannot debug anything on the desktop through
> >>ADL.
> >> > It just sticks at 57%.  I am also unable to debug web apps.  The only
> >> >type
> >> >of debugging I have gotten to work is a mobile app directly on the
> >>device
> >> >or via iOS simulator, nothing else seems to work.
> >> >
> >> >I've read up for days on the issue and applied the privacy setting to
> >> >include Flash Builder, updated ownership/permissions on the project, my
> >> >entire documents directory (where my project lives) and the
> >>applications
> >> >directory to be my user and chmod -R 777 every where I just mentioned.
> >> >
> >> >I've tried all the different flex/air combinations I have which are:
> >> >
> >> >   - flex 4.6, AIR 3.1
> >> >   - flex 4.6, AIR 3.4
> >> >   - flex 4.6, AIR 3.8
> >> >   - flex 4.6, AIR 3.9
> >> >   - flex 4.6, AIR 4.0
> >> >   - apache flex 4.11, AIR 4.0
> >> >
> >> >
> >> >I'm now at a complete loss.  When I close out the app while the
> >>debugger
> >> >progress is still stick at 57%, I get this error:
> >> >
> >> >Process terminated without establishing connection to debugger.
> >> >
> >> >2014-01-22 15:36:59.313 adl[3199:507] CoreText performance note: Client
> >> >called CTFontCreateWithName() using name "Times Roman" and got font
> >>with
> >> >PostScript name "Times-Roman". For best performance, only use
> >>PostScript
> >> >names when calling this API.
> >> >2014-01-22 15:36:59.313 adl[3199:507] CoreText performance note: Set a
> >> >breakpoint on CTFontLogSuboptimalRequest to debug.
> >> >
> >> >
> >> >Launch command details:
> >> > /Users/jake/Documents/apache_flex_sdks/flex4.11AIR4.0/bin/adl -runtime
> >> >/Users/jake/Documents/apache_flex_sdks/flex4.11AIR4.0/runtimes/air/mac
> >> >-profile mobileDevice -screensize 768x1004:768x1024 -XscreenDPI 132
> >> >-XversionPlatform IOS "/Users/jake/Documents/Adobe Flash Builder
> >> >4.7/NEIMobile/bin-debug/NEIMobile-app.xml" "/Users/jake/Documents/Adobe
> >> >Flash Builder 4.7/NEIMobile/bin-debug"
> >> >
> >> >
> >> >Any help is very much appreciated.  I'm going crazy here.
> >> >
> >> >Thanks!
> >> >
> >> >-Jake
> >>
> >>
>
>

Reply via email to