We have a VPN app with Packet Tunnel Provider for iOS. The option disconnectOnSleep from <NetworkExtension/NEVPNProtocol.h> is false.
Sometimes our users experiences an issue when the process stops itself after some period of time without crashes.
In the logs, everything looks Ok.
The iOS versions with the reproduced issue are 16.7.2, 17.1. Memory usage of our VPN app is ~9Mb.
I've implemented NEProvider's interfaces in our subclass of NEPacketTunnelProvider:
override func sleep(completionHandler: @escaping () -> Void) {
NSLog("Sleep")
completionHandler()
}
override func wake() {
NSLog("Wake")
super.wake()
}
After retesting by users, I've noticed that there are multiple subsequent calls of sleep-wake, sleep-wake, sleep-wake API, but in the problem scenario, our logs and the process stops after "Sleep".
I've read the post https://developer.apple.com/forums/thread/95988, and didn't get an idea: what if sleep(_:) nor wake() are not implemented - how does it affect the VPN app behaviour?
Is it a correct hypothesis that sometimes the iOS kills the process silently without crash? What are the triggers that force the system to kill a VPN app?
Hellena
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
User for
Post
Replies
Boosts
Views
Activity
Hello,
We have misunderstanding with a quantity of crashes in different sources.
In our case, we see the growth of crashes for specific product's version for last two weeks. In App Store Connect, we see about 1000 crash reports for opt-in users.
On the other hand, in Xcode Organizer, the same version of the product at the same period of time have produced 1 crash that appeared on 6 devices.
Doing simple math, it means that 6 devices has produced ~170 crashes in two weeks. Is that correct conclusion?
I'm not sure, should I trust to this math, because the crash is flaky, and its appearance grows time to time.
Is there any way to see the same numbers in Xcode Organizer and App Store Connect?
For now, I'm not sure, if this one crash on 6 devices from Xcode Organizer covers all the 1000 crashes from App Store Connect. How can I be sure, that Xcode Organizer haven't missed any other kind of crashes?