It’s not memory pressure related.
iOS is killing the app because it doesn’t have access to the API that allows it to run in the background. That’s why it’s not listed in the Background App Refresh menu in the Settings app.
All API permissions are disabled by default on iOS. The developer must enable the API requests, and the user must accept them for the feature to be enabled.
There’s a difference between iOS killing the app and suspending it. When suspended an app remains in memory and the OS doesn’t give it any opportunities to run any code. When the user switches back the app resumes without any change in its state.
It also happens just locking the phone and coming back, even with no other apps open.
Do you have any other resource hogs running in the background? Perhaps a poorly-coded VoIP or VPN extension could do that.
If you have access to a Mac you can use Console.app to see what log events there are about Voyager when you switch away. That would explain why it’s being killed.
thanks for using Leebra!
go to feed...
iOS is probably killing the Voyager app when it’s in the background because whatever you’re switching to is using a lot of memory.
save