LiveCode Forums.

And I'm getting error messages about an incorrect SDK when building for Android, even though I've built with that SDK for a long time and building directly to the phone works fine. Restarting LC allows a build normally until I make changes to the stack, where the error appears again.

Stam, have you tried restarting LC after it happens? I think there may be something wrong with the error reporting system.

jacque wrote: Sun Feb 06, 2022 7:09 pm Stam, have you tried restarting LC after it happens? I think there may be something wrong with the error reporting system.

Yep have restarted and also reinstalled 9.6.4 and 9.6.5.
Still the same for me.
Maybe deleting prefs will help? Not sure why it would tho…

One more question. Before you get the error message, do you save the stack manually? I've tracked my problem as far as the Save dialog which appears even if I've saved the stack myself.

This error was happening on resizing the stack (basically resizing text in fields that grow longer and vice versa). Experience with the GM means I ALWAYS save before resizing the stack as sometimes crazy wonky things can happen and you can spend hours resizing/repositioning controls.

So yeh saved and saved frequently…

I've updated my bug report and included a reference to this topic here on the forums.
https://quality.livecode.com/show_bug.cgi?id=23541 My workaround is to edit the LC backscript, details are in my bug report. If you don't see a redundant Save dialog after you've already saved manually, then we may not be seeing the same bug. Or else the problem lies deeper in the IDE and my workaround just aborts it earlier.

My problem started somewhere around LC 9.6.6 which is near the same time frame as yours.

Edit: I guess if you're not building a standalone you wouldn't see a Save dialog, so that doesn't apply. But the wrong error messages still sound like the same problem.

Thanks Jacque,
just to make this more interesting, after days of suffering with this issue, it's just inexplicably stopped, and i can finally see the error debug window again. I presume there was a gremlin somewhere causing havoc...

Did you change anything that might have fixed it? A script maybe?

Oh, I know what it was... I linked to your posts here. Maybe if you link to mine, mine will go away too.

jacque wrote: Mon Feb 07, 2022 7:55 am Oh, I know what it was... I linked to your posts here. Maybe if you link to mine, mine will go away too.

Actually i can still trigger the error and have a reproducible recipe; I have updated the bug report above.
The error only happens with LC 9.6.6 for me now (I'm on MacOS Monterey, haven't tested other environments)

Recipe to reproduce:
- create new stack
- add 2 buttons side by side (btn1 on the left and btn2 on the right)
- using the geometry manager, have btn2 move with the right edge of the stack
- using the geometry manager have btn1 move with btn2

At this point all works as expected - dragging the right edge of the stack moves both buttons.
Now group btn2 (knowing this will cause a GM error).
On dragging the right edge of the stack the GM fails (as expected), and on mouseUp you get the error i reported in the OP, with a dialog stating the remoteDebugger is password protected.

This has been reproduced by Panos - hopefully LC will be able to fix.
I wonder if others can trigger this as well on other platforms using 9.6.6?

I have never really got the Geometry Manager to
play nicely with me, so always do my own "wiggling around".

The point isn’t so much the geometry manager, it’s that the error messaging is very wrong…

it’s that the error messaging is very wrong…

Many of those error messages seem a bit obscure to me.

I don't expect to be troubled by remoteDebugger errors when working on a project in the IDE...

This isn’t “obscure”, it’s very clearly a malfunction.

Stam- Can you move the remote debugger stack somewhere else to make sure it doesn't get accessed?

mwieder wrote: Wed Feb 09, 2022 7:13 pm Stam- Can you move the remote debugger stack somewhere else to make sure it doesn't get accessed?

the remoteDebugger seems to live inside the application package on Mac at:
/Applications/LiveCode 9.6.6.app/Contents/Tools/Extensions/com.livecode.library.remotedebugger/remotedebugger.livecode

Moving the folder com.livecode.library.remotedebugger out of the extensions folder of the app package stops the dialog from popping up. Only now revErrorDisplay pops up and is immediately wiped so no information is displayed. So problem not solved

LC are on the case and hopefully will be fixed soon...