Auto-lock is disabled. It seems in 11.3 if there's no touches for anywhere between 30min-2hours the app will exit, and need to be restarted; this is a business app that's almost always running, plus all night with no interaction, and it's never happened before but now I have multiple reports. The user is not exiting, there's no corresponding crash reports being uploaded, and no out-of-memory warnings. Has anyone experienced this? I'm wondering if it has to do with the new Battery Management changes directed at Kiosks and POS which are always plugged in.
iPad app shuts down after inactivity
Does it occur if iPhone is on charge ?
It's actually exclusively an iPad app but yes, always on charge since the app runs pretty much 24/7. More specifically it's an iPad6,7 on a Lightening to USB Camera adapter.
Does not appear to be exclusive to 11.3. Received more reports from different builds of 11.2.
What could cause the app to close with the idleTimer disabled, if there's no crash report generated and no out of memory warnings?
Is your app the only one running ? Or could another app or your own app use too much memory ?
How are your func
func applicationDidEnterBackground(_ application: UIApplication) { func applicationWillResignActive(_ application: UIApplication) {and
func applicationWillTerminate(_ application: UIApplication) {Did you try to instrument to understand what's happening ?
A possible cause is that your app takes to long to respond to some events (could be network issues)
Have you checked nothing changed in your server over the last few months ?
App Termination
Apps must be prepared for termination to happen at any time and should not wait to save user data or perform other critical tasks. System-initiated termination is a normal part of an app’s life cycle. The system usually terminates apps so that it can reclaim memory and make room for other apps being launched by the user, but the system may also terminate apps that are misbehaving or not responding to events in a timely manner.
These are customer devices, so I can't say for sure if it's the only app running but it "should" be; typically they're locked in with Guided Access.
It could be memory, but I log every memory warning, and there are none leading up to the app quit.
All three of those functions are implemented with logging, and none are called prior to the app quit.
I have used instruments, but I have not been able to reproduce the issue, so I'd be guessing. It's only been happening to a handful of customer devices.
There shouldn't be any significant server changes recently, but that last part might be worth pursuing further. Your comment about "not responding to events in a timely manner", does that first call applicationWillTerminate? What events might those be? All the network communication should be using default timeout values.