Thanks. One more question: should remote debugging work with script-only
stacks that are part of the app? I have several breakpoints set but none
of them trigger in a test build.
On 9/28/17 2:16 PM, panagiotis merakos via use-livecode wrote:
Hi Jacque,
This is the expected behaviour. The remote debugger is included in the
standalone when you click on the Test button, even if you don't select it
in the Inclusions (the same applies to Android Internet permission).
See the discussion in this bug report:
http://quality.livecode.com/show_bug.cgi?id=19370
If you think this is not expected behaviour, please file a report for us to
reconsider.
A workaround to prevent the remote debugger from being included in the
standalone is to turn off the wifi in your Android device (or connect to a
different network than the one your machine is connected to). I have not
tested it but I suppose it will work.
Best,
Panos
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
