Re: OS X Firewall triggering on launch

2017-04-24 Thread Mike Kerner via use-livecode
I just removed it, then fired up dp6, and didn't get the dialog. I then went back into the firewall, and dp6 was in there, enabled. On Mon, Apr 24, 2017 at 2:18 PM, J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > I did some googling and it turns out this is an OS X

Re: OS X Firewall triggering on launch

2017-04-24 Thread J. Landman Gay via use-livecode
I did some googling and it turns out this is an OS X glitch that dates back several years. It isn't app-specific. The first thing to try is to remove the app from the firewall list and then put it back again when you next launch. That hasn't worked for me. The nuclear option is to delete the

Re: OS X Firewall triggering on launch

2017-04-24 Thread Mike Kerner via use-livecode
I'm also getting this with every launch, even though dp6 is in the firewall settings. It's much less annoying, now that LC isn't crashing constantly with the new version of mergDeploy, so I don't quit and relaunch 9 very often, now. On Tue, Apr 11, 2017 at 10:49 PM, J. Landman Gay via

Re: OS X Firewall triggering on launch

2017-04-11 Thread J. Landman Gay via use-livecode
On 4/11/17 9:17 PM, J. Landman Gay via use-livecode wrote: On 4/11/17 5:17 PM, Monte Goulding via use-livecode wrote: On 12 Apr 2017, at 4:48 am, J. Landman Gay via use-livecode wrote: And it is still putting up the alert on launch. Seems I'm stuck with it.

Re: OS X Firewall triggering on launch

2017-04-11 Thread J. Landman Gay via use-livecode
On 4/11/17 5:17 PM, Monte Goulding via use-livecode wrote: On 12 Apr 2017, at 4:48 am, J. Landman Gay via use-livecode wrote: And it is still putting up the alert on launch. Seems I'm stuck with it. Hmm… that’s odd. I’ll ask the team if anyone has any ideas

Re: OS X Firewall triggering on launch

2017-04-11 Thread Monte Goulding via use-livecode
> On 12 Apr 2017, at 4:48 am, J. Landman Gay via use-livecode > wrote: > > And it is still putting up the alert on launch. Seems I'm stuck with it. Hmm… that’s odd. I’ll ask the team if anyone has any ideas why this is occurring. Just to make sure you aren’t

Re: OS X Firewall triggering on launch

2017-04-11 Thread J. Landman Gay via use-livecode
On 4/11/17 1:07 PM, J. Landman Gay via use-livecode wrote: I just added dp6 to the firewall manually. And it is still putting up the alert on launch. Seems I'm stuck with it. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software |

Re: OS X Firewall triggering on launch

2017-04-11 Thread J. Landman Gay via use-livecode
On 4/11/17 1:01 PM, J. Landman Gay via use-livecode wrote: On 4/11/17 1:35 AM, Monte Goulding via use-livecode wrote: Yes the IDE is accepting connections for the remote debugger to work. Standalones then open sockets to the IDE. You should only get this dialog if you don’t allow signed apps

Re: OS X Firewall triggering on launch

2017-04-11 Thread J. Landman Gay via use-livecode
On 4/11/17 1:35 AM, Monte Goulding via use-livecode wrote: Yes the IDE is accepting connections for the remote debugger to work. Standalones then open sockets to the IDE. You should only get this dialog if you don’t allow signed apps to accept connections by default and/or don’t allow it the

Re: OS X Firewall triggering on launch

2017-04-11 Thread Paul Hibbert via use-livecode
Just checked my Firewall settings and there’s no entry for LC, but I’m not seeing any trigger, I’ve used LC 9.0 (dp6) quite a few times since install and no problem so-far! Mac OS Sierra 10.12.4 Paul > On 10 Apr 2017, at 23:21, J. Landman Gay via use-livecode >

Re: OS X Firewall triggering on launch

2017-04-11 Thread Monte Goulding via use-livecode
> On 11 Apr 2017, at 4:21 pm, J. Landman Gay via use-livecode > wrote: > > LC 9.0dp6 triggers the OS X firewall every time I launch it. I know I can set > the firewall to accept LC so it won't warn me, but I'm wondering what LC is > doing that makes that

OS X Firewall triggering on launch

2017-04-11 Thread J. Landman Gay via use-livecode
LC 9.0dp6 triggers the OS X firewall every time I launch it. I know I can set the firewall to accept LC so it won't warn me, but I'm wondering what LC is doing that makes that happen. I suspect it has something to do with remote debugging. Does anyone know? -- Jacqueline Landman Gay |