-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PinWatchers are not started sometimes, when the app is in background #764
Comments
Maybe I fucked up something when touching ChatThreadLoader yesterday. But I think I first noticed this thing even before that. |
Alright, this only happens once, the very first update call after the app has been killed, and happens because we now force call |
This isn't a regression, just Android being Android. It's a pretty old issue considering I found this: https://github.com/evernote/android-job/issues/128, but someone recently submitted a bug report https://issuetracker.google.com/issues/149556385. |
I mean you can clearly see that it doesn't notify Wakeables because |
Figured it out. If you've got a foreground service running (ie the watch notification), then all resources will be kept in-memory, so a swiped-away app is technically still running. That means that all the PinWatchers are still in memory (therefore don't need to be created), the tl:dr; no bugs to me, all good |
Oh yeah, this explains it. |
Or rather, PinWatchers are getting created but they are not getting updated, i.e. they do not load new posts. Usually this happen on first app wake up after it getting killed. Here is the first app wake up:
And here is the second one:
Third one is the same as the second one:
Notice that there are ChanThreadLoader calls now:
The text was updated successfully, but these errors were encountered: