Sorry Mark, I see you provided a path in /etc/hosts below. I'll try that. ----- Original Message -----
From: modjkl...@comcast.net To: users@flex.apache.org Sent: Wednesday, February 12, 2014 7:54:58 AM Subject: Re: new Mac machine, running Flex application sticks at 57% Thanks for the tip Mark, I've seen this posted on Google but never knew how to set it. Could you give a little more detail? Is this a setting in Flash Builder? Or is it a Mac OSX System Preferences setting? ----- Original Message ----- From: "Mark Line" <markl...@gmail.com> To: users@flex.apache.org Sent: Wednesday, February 12, 2014 7:50:49 AM Subject: RE: new Mac machine, running Flex application sticks at 57% I'm not sure if you need this on OSX but could you tried making sure you have localhost set up on in your hosts file correctly I'm assuming it’s the same as most *nix in /etc/hosts Add the following line: 127.0.0.1 localhost -----Original Message----- From: modjkl...@comcast.net [mailto:modjkl...@comcast.net] Sent: 12 February 2014 15:37 To: users@flex.apache.org Subject: Re: new Mac machine, running Flex application sticks at 57% Still haven't resolved this... let me simplify the discussion. Instead of upgrading the OS as originally posted for this thread, I'm now using a new macbook OSX 10.9.1 machine with fresh install of FB 4.7, and SDK 4.12 (nightly build). However, it produces the same results... When I run any program, it doesn't match which program (firefox, chrome), the progress panel shows "Launching Main (57%). Waiting to connect to the running application..." After 2 minutes it times out with a popup that states: The Flash Builder debugger failed to connect to the running application. Ensure that: 1. For in-browser applications, you are running the debugger version of Flash Player. 2. For network debugging on a mobile device, you have a reliable network connection to the device, and port 7935 is open on your machine's firewall. For example, the following application gives the above error: <?xml version="1.0" encoding="utf-8"?> <!-- http://blog.flexexamples.com/2009/03/30/setting-the-base-color-on-an-fxcheckbox-control-in-flex-gumbo/ --> <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="955" minHeight="600"> <s:CheckBox id="checkBox" label="Spark CheckBox" selected="true" symbolColor="red" horizontalCenter="0" verticalCenter="0" /> </s:Application> Things I've done to troubleshoot: 1. Verified debug version of Flash Player is installed. 2. Verified my "Adobe Flash Builder 4.ini" and "Adobe Flash Builder 4.7.ini" files contain switches -Xms512m, -Xmx1024m, -XX:MaxPermSize=1024m. 3. Verified Main.html and Main.swf files are in the bin-debug directory. 4. disabled automatic rebuilds 5. Note, there is no anti-virus installed 6. Note, there's no connection to SVN or other repository 7. cleaned project several times 8. rebooted machine several times I *really* could use some help here. Where should I look next? (as an aside, I contacted Abode to purchase an individual per incident contract support but after many hours on the phone being on hold and transferred in circles between sales and support for 2 days, it appears no one in Adobe knows where to route me or how I can purchase an individual support contract for Adobe Flex Platform. Would be interested if anyone knows of a direct line or contact.) Thanks in advance. ----- Original Message ----- From: modjkl...@comcast.net To: "apache flex users" <users@flex.apache.org> Sent: Sunday, February 9, 2014 11:45:09 PM Subject: upgraded Mac OSX to Mavericks and application won't run Hi experts, I'm using a nightly build from SDK 4.12 from a month ago, and FB 4.7. I just upgraded my Mac OSX from 10.6.8 (Snow Leopard) to 10.9.1 (Mavericks). Using the new OSX, when I rebuild the application then run it using Firefox with debug version of FB (I verified it is debug version by visiting a website showing me what version FP is running in the browser), the progress panel shows "Launching Main (57%). Waiting to connect to the running application..." After 2 minutes it times out with a popup that states: The Flash Builder debugger failed to connect to the running application. Ensure that: 1. For in-browser applications, you are running the debugger version of Flash Player. 2. For network debugging on a mobile device, you have a reliable network connection to the device, and port 7935 is open on your machine's firewall. I've seen this error many times in the past, but I've always been able to recover it by exiting the application and browser, rebooting the machine, rebuilding, and running again. I've tried everything I can think of in the new OSX and nothing seems to change this. I verified the java version is the correct version for OSX 10.9.1, and that Flash Builder's .ini file for setting java heap size is sufficiently large (it's same settings used by OSX 10.6.8). A couple of other observations, if it helps... If I exit my web application, then start it again (still using 10.9.1), while it's trying to connect (e.g. before it times out), if I double-click the Main.html file in the bin-debug folder, the app runs fine but it runs inside a tab of Flash Builder 4.7 (as opposed to in the Firefox browser). Also, before upgrading to OSX 10.9.1, I bought an external hard drive and made a clone of the original hard drive when it was OSX 10.6.8. If I boot the computer using this clone, everything runs fine from OSX 10.6.8. If I boot again using the (updated original) hard drive with OSX 10.9.1, I see the error above. If I switch to Safari (instead of firefox, and try OSX 10.9.1), the application opens in a Safari browser window and runs, but as soon as I attempt to do an HTTP POST operation to the server, I get a fault with the following showing in the debugger: event : mx.rpc.events.FaultEvent event.fault : mx.rpc.Fault event.fault.faultCode="Server.Error.Request" event.fault.faultDetail="Error: [IOErrorEvent type="ioError" bubbles=false cancelable=false eventPhase=2, text="Error #2032: Stream Error. URL: https://www.companyname.com:443/myapp/login"] . event.fault.faultString="HTTP request error" Would really appreciate any help, as I've run out of ideas what to try next. Thanks in advance.