Remote Debugger Anomalies

[Sannyasin Brahmanathaswami]

Well I play with it a while, I don't have  a perfect recipe yet...

1) debug error show up. Do edit the script. You check the error and
close the script editor. So far I think the IDE has no cache of it.

2) then on the phone, you go to App Info, Uninstall.

So far I didn't get a cached script. But if you "touch" the script. In
some way, even to change a space. Then even after you uninstall the app
on the phone and close the editor, then open it again make some changes,
and you change some code and (verified save text file of a behavior by
BBedit)

 Then, magically then old code may appear!

then carefully, close the SE, and uninstall the app, appears go away..

No doubt Monte is going to say :-) "this is not problem, best you ignore
this" ha!~

BR


On 9/15/18 6:39 AM, J. Landman Gay via use-livecode wrote:
> I asked this before and the fix is to quit the app, if I remember right. 
> The problem on Android is that apps never really quit, they remain in the 
> background until the OS needs the RAM. When the OS wipes the app, we don't 
> receive any messages so the debugger won't know when the socket closes. The 
> same thing happens when the user hits the Home or Recent buttons to leave 
> the app, which also does not notify us. We need messages for these events. 
> Android does send the app a notification but LC hasn't implemented it.
>
> The result is that LC Android apps usually never know what's going on. It 
> interferes with the ability to save the app state as well.
>
> You might try adding a Quit button to see if that works. The quit command 
> was updated a bit recently so that might work, even if you just use it 
> temporarily for debugging.

-- 
Svasti Astu, Be Well!
Brahmanathaswami
 
Get the SivaSiva app, it's free:
https://www.himalayanacademy.com/apps/sivasiva