thunderbird / thunderbird/thunderbird-android
"After deleting or moving a message" setting not respected
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
Thunderbird for Android
App version
17.0b3
Where did you get the app from?
Other
Android version
LineageOS, 22.2-20260211-NIGHTLY-FP3
Device model
Fairphone 3
Steps to reproduce
Delete or archive messages.
Expected behavior
Next message shown (if that setting is selected)
Actual behavior
The app seems to glitch (maybe ~50% of the time) and return to the message list.
It doesn't feel like it is simply not listening to the setting, it seems like it is glitching someway. See screen-recording.
https://github.com/user-attachments/assets/321b0b2c-7bb4-46ba-8860-f967cdf3282b
I think I've seen this behavior for the last ~2 months, in various stable and beta versions (16/17).
Other potentially useful things
- I mainly use an outlook.com account.
- I have multiple accounts.
- I have a high local folder size (5000)
Very happy to help if there's any way I can.
Logs
Side-note - the logs have a default filename of "k9mail-logs". Is this intended?
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
No source files or tests are named. Start by reproducing delete and archive actions on the reported Android setup, then review the attached screen recording and k9mail logs alongside the handling of the “After deleting or moving a message” preference. Done means the selected next-message behavior works consistently after both actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100