iOS App Crashing On Close

[Mark Smith]

Hi Dan, 

Just to followup, I’ve not experienced the crash you mentioned but I do remember going through a lengthy trial and error process trying to figure out which messages are sent, and when, in response to closing the app the way you describe. I think I discovered, at least I noted this as a comment In my code, that the shutdown and shutdownrequest messages are not sent to mobile devices, at least they weren’t when I was testing some years ago. Things may have changed since then. Instead I used closeStack and closeStackRequest which appear to work reliably. (But I have not tested with 10.0.0 (rc1)). Hope it helps. 

But let’s hope Panos can shine more light on this (as I often feel like I am walking around in LC with a blindfold on. Note: the documentation appears to shine no light on this situation). 

Best,
Mark

> On 7 Aug 2024, at 10:07 PM, Dan Friedman <dan at clearvisiontech.com> wrote:
> 
> Mark,
>  
> Thank you for the reply and thoughts!   I am not using closeStack or closeStackRequest anywhere in my project.   I am using shutdown and shutdownRequest but those calls have not changed since moving from 10.0.0 (dp 8) to 10.0.0 (rc1).   Also, I am not using mergeNotify (or have it included) in the build.
>  
> Maybe Panos will have some ideas?
>  
> -Dan
>  
>  
>  
> From: Mark Smith <marksmithhfx at gmail.com>
> Date: Wednesday, August 7, 2024 at 2:00 PM
> To: How to use LiveCode <use-livecode at lists.runrev.com>
> Cc: Dan Friedman <dan at clearvisiontech.com>
> Subject: Re: iOS App Crashing On Close
> 
> Hi Dan,
> 
> Just a random thought that might help orient you to a potential problem… how are you handling the closeStackRequest (or closeStack) message? “Quit” in a button obviously bypasses these. Odd that the problem would just start showing up in 10.0.0 although I do remember reading somewhere that the implementation of Monte’s mergeNotify which contained the message UIApplicationWillResignActiveNotification had been revised at some point, but can’t find any reference to it now.  Sorry if that doesn’t help. Just some random thoughts that popped into my head while reading of your problem. 
> 
> Mark
> 
> > On 7 Aug 2024, at 8:33 PM, Dan Friedman via use-livecode <use-livecode at lists.runrev.com> wrote:
> > 
> > I have an app that has been humming along just fine in the app store.  I updated the app to 10.0.0 (rc1) and it’s now in TestFlight.   When I close the app from the OS (swipe up from bottom of phone and then swipe app up to exit it), I get this message:
> > 
> > “MyAppName” – Crashed
> > Do you want to share additional information with the developer?
> > 
> > Details about the crash in TestFlight (date, time, build, device model, etc.) seem useless.   I looked at the crash log in Xcode, but it too seems to just list the threads and hex values.  For example, the highlighted red line in the Crash List (in Xcode) shows:   MyAppName: 0x104a6c000 + 634716
> > 
> > Interesting thing is if I call “quit” in a button, I don’t get the crash.
> > 
> > Any thoughts?
> > 
> > -Dan
> > _______________________________________________
> > 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
>