I thought the file was mm.cfg, not mms.cfg.

On 2/12/14 3:07 PM, "[email protected]" <[email protected]> wrote:

>I have a new Macbook OSX 10.9.1 and fresh installs of FB 4.7, and the
>nightly 4.12 SDK. 
>
>I export my fully functional application from my desktop Mac, and import
>into FB 4.8 in the Macbook.
>
>From the new Macbook, I export a release build and place on the internet.
>
>The app runs fine when I run it on the internet from my old desktop Mac
>(Chrome, Safari, Firefox).
>
>However, the NEW MACBOOK (which uses the same versions of Chrome and
>Firefox, but a newer Safari version) shows errors when accessing this app
>from the internet, and when running from FB 4.7, as follows:
>
>
>**** PRODUCTION flash player, running app from WEBSITE ****
>
>Chrome -- works 
>Firefox -- works 
>Safari -- "HTTP Request Error"
>
>The Safari error occurs as soon as Safari communicates with the server
>(to log the user in) using the variable:
>
>private var _serviceSSL:HTTPService;
>
>
>**** PRODUCTION flash player, running app from FLASH BUILDER ****
>
>Chrome -- "Security error accessing url : Destination : Default HTTP"
>Firefox -- works 
>Safari -- "HTTP Request Error"
>
>These errors occur at the same place discussed above for Safari.
>
>
>**** DEBUG flash player, running app from FLASH BUILDER ****
>
>Chrome -- works 
>Firefox -- works 
>Safari -- "HTTP Request Error"
>
>
>I tried to create a flashlog.txt file based on the article:
>
>http://helpx.adobe.com/flash-player/kb/configure-debugger-version-flash-pl
>ayer.html 
>
>I configured the mms.cfg file correctly as root, but while I have a path
>
>/Users/username/Library/Preferences/Macromedia/Flash Player/
>
>there is no Logs folder here as the knowledge base article says there
>should be. Regardless, I run the app after cleaning, and compiling, and
>still no Logs folder is created. Then I manually create a Logs folder and
>repeat and still no flashlog.txt file in the Logs folder. I must be doing
>something wrong to generate this log file.
>
>Anyway, I'm stuck here. Seems to be a security setting for my Macbook, or
>interplay between Macbook and browsers, creating some problems. Any hints
>would be much appreciated.
>
>

Reply via email to