Remote debugging - expected behavior

[Bob Sneidar]

This sounds similar to a problem I have building apps. I have a login stack that I call modally when the main stack is opened. When I build the app it OPENS THE LOGIN APP MODALLY as though it is actually RUNNING my scripts, and since it is modal I have to manually set the stack to top-level for the standalone builder to continue. It did not do this in 8.0.x. It started in 8.1. I just deal with it like you have been doing. 

Bob S


> On Sep 28, 2017, at 11:45 , J. Landman Gay via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> What is the expected behavior of remote debugging? I'm not sure if what I see is how it is supposed to work, or a bug.
> 
> I have an app that does not have the remote debugger included in the Inclusions pane. Looking at the revStandaloneSettings custom properties, it is (correctly) not in there either.
> 
> Every time I do a test build, LC asks if I want to start a remote debugging session. Until I noticed the dialog, I thought the app had hung on launch. I have to provide a response on every test build before the app will run. Also, even if I just relaunch the app after installation, it asks again. Basically I can't run the app without replying to the dialog. Is this correct behavior?