"Touch to retry" doesn't work to resend a message
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start by tracing the message send and retry behavior triggered by touching “Not sent. Touch to retry,” then inspect how that flow saves messages to the telephony database. Reproduce the steps with airplane mode enabled and compare the retry with the original send. Done means retrying resends the same message without creating a duplicate or showing the database error.
Written by the indexing model from the issue text.
Description
Checklist
- I can reproduce the bug with the latest version given here.
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- This issue contains only one bug.
- I have read and understood the contribution guidelines.
Affected app version
1.8.0
Affected Android/Custom ROM version
Android 10
Affected device model
Xiaomi Mi 9
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
- Turn "plane mode" on
- Write a message to a random contact
- Click on "send" button
- Wait for the error message "Not sent. Touch to retry."
- Touch the error message
- Click on "send" button
Expected behavior
The same message should be resend not a duplicated one
Actual behavior
A pop-up error message appears "unable to save message to the telephony database"
Screenshots/Screen recordings
No response
Additional information
No response
- Dominant language
- Kotlin
- Stars
- 1.6k
- Forks
- 187
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 20
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from FossifyOrg/Messages
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FossifyOrg/Messages#897 · 1 comment ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FossifyOrg/Messages#761 ·
Maintainers usually reply within 1 day
-
[Export] mms "No entries for export have been found"May be free again A pull request for this issue was closed without being merged. Openbug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
FossifyOrg/Messages#493 · 24 comments · 3 reactions ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 3/5 1-2 days Newbie friendliness 56/100
FossifyOrg/Messages#902 ·
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 5/5 Over a week Newbie friendliness 28/100
FossifyOrg/Messages#900 ·
Maintainers usually reply within 1 day
All issues in FossifyOrg/Messages
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
utopia-rise/godot-jvm#1004 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
pedroSG94/RootEncoder#2213 ·
Maintainers usually reply within 2 days
-
coding good first issue size:xs skill:kotlin-core sub-issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
SKaiNET-developers/SKaiNET#1323 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
dzid26/TeslaBatteryBLE#183 ·
Maintainers usually reply within 1 day