thunderbird / thunderbird/thunderbird-android
PUSH service do not properly restart if process com.fsck.k9 is killed (some OS kill it if app is removed from recent window, even if a service is running)
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
Checklist
- I have used the search function to see if someone else has already submitted the same bug report.
- I will describe the problem with as much detail as possible.
App
K-9 Mail
App version
8.2
Where did you get the app from?
F-Droid
Android version
14
Device model
Jelly Max
Steps to reproduce
- Turn on Push for inbox folder (with relative permission to schedule alarm)
- Launch App
- Close App
- notification bell in status bar disappear and after few seconds appear again
- send mail
- no notification
- pull down notification area and click on Waiting for new emails and then Tap to learn more (informative windows appear)
- notification for previous mail arrive immediately
Expected behavior
If there is notification service active and bell notification icon i expect that push notification should work.
Actual behavior
Seems that when application is closed, imap idle connection is closed too, then bell notification reappear but push notification do not work anymore until i click on "tap to learn more".
Logs
It's a strange behavior, consider that the push service is always running i can see from Android "Developer Option/Running service" that it's never stopped, it's even listed in "Active Apps" warning with running time equals to boot time (i attach a screen).
I own the mail server that i use for imap push, so i have looked at the mail logs; when application is stopped IMAP idle connection is closed.
Then even if bell icon reappear in notification status bar, connection is not re-established until i click on "Tap to learn more".
As soon as i click on "Tap to learn more" imap connection is established and if there are pending emails i am immediately notified.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue using the listed Android 14 steps, focusing on the push service after the app process is killed and the IMAP IDLE connection closes. Start by tracing the push service lifecycle and the “Tap to learn more” notification action. Done means the connection is re-established and new-mail notifications work without tapping that action.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100