this post was submitted on 16 Nov 2024
25 points (96.3% liked)

Voyager

5607 readers
452 users here now

The official lemmy community for Voyager, an open source, mobile-first client for lemmy.

Download on App Store

Download on Play Store

Use as a Web App

Download on F-Droid

Rules

  1. Be nice.
  2. lemmy.world instance policy

Sponsor development! 👇

Number of sponsors badge

💙

founded 1 year ago
MODERATORS
 

When I put my iPhone down for a bit and come back to Voyager, the app resets back to the top of the feed. I then have to scroll so far down to find the place I was at.

My iPhone settings does not show Voyager app in the background app refresh settings.

I believe this setting would keep the feed in the same place when I bring the app back.

top 6 comments
sorted by: hot top controversial new old
[–] [email protected] 10 points 16 hours ago (2 children)

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.

[–] [email protected] 9 points 15 hours ago* (last edited 12 hours ago) (1 children)

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.

[–] [email protected] 1 points 11 hours ago

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.

[–] [email protected] 3 points 16 hours ago (1 children)

It also happens just locking the phone and coming back, even with no other apps open.

[–] [email protected] 1 points 11 hours ago (1 children)

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.

[–] [email protected] 1 points 11 hours ago

Nothing that I know of. I don’t run much on this phone, and you can see in the screen shot I keep most stuff from running in the background (just my email is on).

No VPN. Only voip is the one built into the phone (Wi-Fi calling) but I’m not on Wi-Fi.

My Mac is packed away at the moment, been traveling.