Remote Debugger Anomalies

[Sannyasin Brahmanathaswami]

-- Shut down LC
-- Android phone is connected  by USB
-- install in app on Android
-- fix a script (change a typo)
-- save the script; save the stack
-- From the test menu, choose Android
-- build the app; install on device
-- the debugged breaks on the script that I just saved, and it shows the
script at it was *before* change the typo!
-- Leave debug mode, try to change the script again,
-- try to save LC give an error message so on cannot file the path to
save the script

The above is just one scenario: after running debug on Android, you have
no clue whether you are editing a "phantom script" or the "real library"
on in your hard drive. Or you are ending a script the  lies in "depths
of the standalone maker" even though the app is installed on the phone.

In some scenarios, like the above, you feel *certain* you are editing
the "real" script. (you can tell by opening BBEdit) You delete the app
from the device, run the test again: the debugger shows that error that
you just fixed!

It is getting tiring to have to shut down LC and reboot everytime you
test. But that seem to be only way that there is not "latent" memory of
the script, as it was, broken, in the bowels of LC, even you have fixed
in it disk.

Can any provide a rock solid procedure to be *sure* that  SA *always*
get a corrected version of any script?

BR