How to quit an Android app

[J. Landman Gay]

I did write about it but I hadn't tried it yet. You were right on the 
nose, that fixes it. I had to allow a short wait. This fails as before:

   tsNetClose
   quit

But this works:

   tsNetClose
   wait 1 with messages
   quit

Success! :)


On 12/21/16 11:17 AM, Matthias Rebbe wrote:
> Hi, ignore my last posting. Just noticed that you wrote about that possiblitiy already.
>
>
>> Am 21.12.2016 um 18:05 schrieb Matthias Rebbe <matthias_livecode_150811 at m-r-d.de <mailto:matthias_livecode_150811 at m-r-d.de>>:
>>
>> Hi,
>>
>> just a shot in the dark, but did you try tsNetClose before quitting. This would close all open connections and disables tsNet.
>>
>> Matthias
>>
>>
>>> Am 21.12.2016 um 07:24 schrieb J. Landman Gay <jacque at hyperactivesw.com <mailto:jacque at hyperactivesw.com>>:
>>>
>>> Sending "quit" in 10 milliseconds doesn't crash the app on second launch (good.) But it hangs for a while and then returns a "socket timeout" message. So it does look like maybe it's TSNet.
>>>
>>>
>>> On 12/21/16 12:20 AM, J. Landman Gay wrote:
>>>> Yeah, I tried that. Maybe "in 0" isn't long enough?
>>>>
>>>> I'm wondering if it's TSNet, since the app loads another stack from a
>>>> server. On the second launch that crashes, I see the loader stack
>>>> briefly and it crashes when it tries to download the remote stack.
>>>> There's a way to remove TSNet from RAM, I'll look it up and see if
>>>> that's the problem.
>>>>
>>>> I assume no one else sees this?
>>>>
>>>>
>>>> On 12/20/16 11:40 PM, Scott Rossi wrote:
>>>>> Maybe try sending the quit command after a short delay instead of from
>>>>> within the handler?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Scott Rossi
>>>>> Creative Director
>>>>> Tactile Media, UX/UI Design
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 12/20/16, 9:38 PM, "use-livecode on behalf of J. Landman Gay"
>>>>> <use-livecode-bounces at lists.runrev.com <mailto:use-livecode-bounces at lists.runrev.com> on behalf of
>>>>> jacque at hyperactivesw.com <mailto:jacque at hyperactivesw.com>> wrote:
>>>>>
>>>>>> I have an Android app with a simple handler:
>>>>>>
>>>>>> on doQuit
>>>>>> quit
>>>>>> end doQuit
>>>>>>
>>>>>> It quits as directed. On relaunch it crashes. On a second relaunch it
>>>>>> works fine. This is consistent behavior.
>>>>>>
>>>>>> I have tried sending "quit" in 0, locking messages, etc. How do you
>>>>>> cleanly quit an Android standalone?
>>>
>>>
>>> --
>>> Jacqueline Landman Gay         |     jacque at hyperactivesw.com <mailto:jacque at hyperactivesw.com>
>>> HyperActive Software           |     http://www.hyperactivesw.com <http://www.hyperactivesw.com/>
>>>
>>> _______________________________________________
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com <mailto:use-livecode at lists.runrev.com>
>>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com <mailto:use-livecode at lists.runrev.com>
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>


-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com