You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we can trust these documented defaults this means that in any given notification fetch (i.e., approx every 15 minutes) Tusky will get the batch of next-newest 15 notifications and display them. If the user has more notifications than that they will have to wait another ~ 15 minutes until they are fetched.
That's probably also a source of user complaints about missing notifications.
Fix is to either:
Use the NotificationsRepository and fetch the notifications that way, taking advantage of its existing code for paging up (prepending) the list of notifications. Not sure how well Pager3 is suited to that though.
Write some additional code here that repeatedly fetches new notifications until there are no new ones.
…tifications (#3700)
* Fetch all outstanding Mastodon notifications when creating Android notifications
Previous code fetched the oldest page of unfetched Mastodon notifications.
If you had more than a page of Mastodon notifications you'd get Android notifications for that page, then ~ 15 minutes later Android notifications for the next page, and so on.
This code fetches all the outstanding notifications at once.
If this results in more than 40 total notifications the list is still trimmed so that a maximum of 40 Android notifications is displayed.
Fixes#3648
* Build the list using buildList
To repeat the comment from #3626:
fetchNotifications
(fetchNewNotifications
in this PR) makes one call to get new notifications (mastodonApi.notificationsWithAuth
).That will return N new notifications, starting with the oldest new one, up to
limit
.limit
is not set in this code, and is documented as being default=15 max=30 at https://docs.joinmastodon.org/methods/notifications/#get.If we can trust these documented defaults this means that in any given notification fetch (i.e., approx every 15 minutes) Tusky will get the batch of next-newest 15 notifications and display them. If the user has more notifications than that they will have to wait another ~ 15 minutes until they are fetched.
That's probably also a source of user complaints about missing notifications.
Fix is to either:
Originally posted by @nikclayton in #3626 (comment)
The text was updated successfully, but these errors were encountered: