Feeder icon indicating copy to clipboard operation
Feeder copied to clipboard

App doesn't work in background after last updates

Open DorH92 opened this issue 1 year ago • 7 comments

Checklist

  • [x] I have used the search function for OPEN issues to see if someone else has already submitted the same bug report.
  • [X] I have also used the search function for CLOSED issues to see if the problem is already solved and just waiting to be released.
  • [X] I will describe the problem with as much detail as possible.
  • [x] If the bug only to occurs with a certain feed, I will include the URL of that feed.

App version

2.6.33

Where did you get the app from

Google Play

Android version

14

Device model

Galaxy S23

First occurred

about 2 month ago

Current behaviour

After the last updates the app stopped working in background, doesn't refresh the feeds and doesn't send notifications. The app is woring in background for few hours, then stop working in background until you manually open the app.

That's despite there is no battery optimization set and the app's battery consumption is set as "unlimited".

Android version: 14 Phone: Galaxy S23+

DorH92 avatar Oct 29 '24 10:10 DorH92

There has been no changes to background synchronization.

I can only recommend actions on https://dontkillmyapp.com/

spacecowboy avatar Oct 29 '24 14:10 spacecowboy

@spacecowboy

I tried to move back to older version (tried randomly April 2024 version) and it works great in contrast to the newer versions. So it is indeed probably something that happened in the app's code in the last updates.

Anyway, it is not important for me to use newest version so I stay with this older version that works good. Maybe you would want to locate issues in the code so I inform you this fact.

Thank you.

DorH92 avatar Nov 09 '24 02:11 DorH92

I do have the same issue with the f-droid version.

ShinIce avatar Nov 09 '24 19:11 ShinIce

One thing that did change since April is that Feeder respects server's cache policies to a greater extent.

So if possible, please differentiate between

  • background sync doesn't run
  • no new data was fetched for some feed

I know it can be hard to tell the difference unless you have many feeds from several sources. But it would help a lot to nail down potential issues.

spacecowboy avatar Nov 11 '24 20:11 spacecowboy

@spacecowboy

New items are fetched well if I open the app manually. I can tell you also that if the app doesn't open again manually, it will not send you notifications forever until you open it manually and then after few hours the same happens.

By the way, I didn't check if the app process is killed and I'm not familiar with your code. I think it is also possible that if the process is not killed, the class responsible for background fetching doesn't get runtime from Android system. Maybe consider apply this class as a service to ensure it works always in background and Android respects it?

DorH92 avatar Nov 12 '24 13:11 DorH92

@spacecowboy

New items are fetched well if I open the app manually. I can tell you also that if the app doesn't open again manually, it will not send you notifications forever until you open it manually and then after few hours the same happens.

By the way, I didn't check if the app process is killed and I'm not familiar with your code. I think it is also possible that if the process is not killed, the class responsible for background fetching doesn't get runtime from Android system. Maybe consider apply this class as a service to ensure it works always in background and Android respects it?

That's not how Feeder works. Feeder uses the WorkManager library, which is the recommended way by Google to schedule background work.

Running manual background services is not how modern Android apps work

spacecowboy avatar Nov 15 '24 14:11 spacecowboy

@spacecowboy

Ok, Why? Service is ensured to run in background and being respected. WorkManager library doesn't ensure it as well service does.

DorH92 avatar Nov 16 '24 16:11 DorH92