thunderbird / thunderbird/thunderbird-android
Pressing/swiping "back" in the purchase completed screen takes the user back to Settings, instead of Support Thunderbird section
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
8.0b3
Where did you get the app from?
Google Play
Android version
14
Device model
Galaxy Tab A9+
Steps to reproduce
- Launch TB
- Choose any purchase value (let's say the lowest one-but it happens with each one)
- The Essential Contribution screen is displayed.
- In the Review and Agree Google play prompt press Agree
- In the Google Play 1-tap buy prompt tap Buy.
- In the Purchase successful screen, tap /swipe to go back.
Expected behavior
I would expect to be taken back to the Support Thunderbird section when tapping/swiping "back".
Actual behavior
When the user taps/swipes back, he is taken to the general Settings section.
Logs
https://github.com/user-attachments/assets/a30be1ed-ae90-4123-b6e7-7d8c8d313f1f
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
Start by tracing navigation from the Purchase successful screen through the Essential Contribution flow and compare the back behavior with the Support Thunderbird and general Settings sections. Reproduce the Google Play purchase flow on Android, then verify that tapping or swiping back from the completed purchase returns to Support Thunderbird rather than Settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100