SPIKE—Notifications Don't Show Up or Are Delayed

A great deal of the issues submitted regarding notifications seem to involve users not receiving their notifications in a timely matter or—sometimes—not at all. These will likely require a much larger change to how we manage syncing, for example, some users may believe 15 minutes is not frequent enough to check for new messages. Others may want push for accounts that support it. And we may have issues with background workers staying active, or the alarm feature we use to schedule workers.

As a result, this will likely become a primary task of the refactor. However, it's worth looking into these bugs, confirming them, and seeing if anything can be done quickly to improve them for our users.

Some examples:

• https://github.com/thunderbird/thunderbird-android/issues/9326
• https://github.com/thunderbird/thunderbird-android/issues/10098
• https://github.com/thunderbird/thunderbird-android/issues/8434
• https://github.com/thunderbird/thunderbird-android/issues/11017
• https://github.com/thunderbird/thunderbird-android/issues/10890
• https://github.com/thunderbird/thunderbird-android/issues/9216
• https://github.com/thunderbird/thunderbird-android/issues/7839
• https://github.com/thunderbird/thunderbird-android/issues/9239
• https://github.com/thunderbird/thunderbird-android/issues/9898
• https://github.com/thunderbird/thunderbird-android/issues/9216

AC:

• Create new tickets for these bugs, either a combined ticket in the sync/notification refactor milestone or in this milestone, for fixing smaller bugs we have deemed high priority, low-to-mid effort.
• If issues are separate, break up existing tickets into examples
• Close out tickets that are duplicates and combine them into individual issue tickets to better track the work and keep all related reports together