thunderbird / thunderbird/thunderbird-android
Switching activity resets Thunderbird, making it impossible to add attachments
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
15.0
Where did you get the app from?
Google Play
Android version
16
Device model
Pixel 7 Pro
Steps to reproduce
- Open Thunderbird
- Select a message
- Tap on the "reply" button
- Add an attachment
Expected behavior
The attachment is added. More generally, Thunderbird does not exit the activity it was in.
Actual behavior
Thunderbird completely discards the draft you wrote and displays the message you were replying to. This also happens if you switch to a different application and then go back. More generally, if you switch to a different activity Thunderbird goes back to the activity it was previously in; if you were drafting a message, even without adding any attachments, Thunderbird goes back to displaying the message in the inbox and will discard your draft as if it never existed (it is not automatically saved in the "drafts" folder).
Logs
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 file or test is named. First reproduce the issue in Thunderbird for Android 15.0 using the listed reply, attachment, and app-switch steps, then trace the activity and draft handling involved. Done means switching activities no longer discards the draft or prevents the attachment from being added.
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
- Needs clarification
- Newbie friendliness
- 30/100