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@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@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@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
