Home > flex > flex debugging adding ?debug=true to your debug file path

flex debugging adding ?debug=true to your debug file path

I’ve exhausted my resources trying to figure out how to disable Flex from adding the querystring variable ?debug=true to whatever file path you use when launching your app in debug mode. I have my debug path pointing to an html file with a custom html embed so this flag isn’t being used by it. It is however blocking me from appending my own variables which get encoded and made unusable :/

The only thing I came up with in google is this semi-related reference from: http://livedocs.adobe.com/labs/flex3/html/help.html?content=apache_3.html

“Flex Builder appends ?debug=true to the URL when it launches the browser. This query string parameter triggers a compilation with the debug compiler options enabled.”

Does any of the 0 people that read my blog have an answer or suggestion? I’m assuming a solution could be found regarding the use of “query string parameter overrides” and the flex-config.xml file. The investigation continues…

Categories: flex Tags:
  1. chris
    June 18th, 2008 at 05:01 | #1

    Hello!

    Same problem here, :( have you been able to find the solution?

  2. Howard Fore
    February 19th, 2009 at 06:50 | #2

    Any solutions? I’ve got a similar problem, not in appending my own variables, but an in-house security framework that also uses a URL parameter of “debug”.

  3. February 19th, 2009 at 07:59 | #3

    Nope, my only solution was to use SWFAddress and include my variables in the address bar hash #

  4. Vic
    June 17th, 2011 at 12:49 | #4

    Invoking the debugger compiler
    You can compile a debug version of your Flex application when you are using the web-tier compiler. You do this by appending ?debug=true to the end of the query string; for example:

    http://www.myhost.com/myApps/Main.mxml?debug=true

    ***** You cannot disable this behavior of the web-tier compiler. **************

    Adding ?debug=true to your query string instructs the compiler to include debugging information in the final SWF file output. As a result, you can set breakpoints and use other features of the fdb command-line debugger or the Flex Builder visual debugger.

    To debug the application, you launch the fdb command line debugger and then launch your application in the browser with ?debug=true on the query string. The application connects to the running debugger.

    You must have a debugger version of Flash Player to compile the application with debug information in it.

    For more information on using fdb, see Using the Command-Line Debugger.

  5. Vic
  1. No trackbacks yet.