Duplicate outgoing SMS/MMS entries created in Telephony provider
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 45/100
Direzione di ricerca
Start by tracing the outgoing SMS and MMS send flows and where each writes to Android's Telephony provider. Reproduce the report's steps and check whether both flows can create multiple provider records for one send. Done means each send creates one outgoing record while the recipient still receives the message.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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
GrapheneOS (Android 14)
Affected device model
Google Pixel 4a (5G)
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
- Set Fossify Messages as the default SMS application.
- Open any conversation.
- Send an SMS (also reproducible with MMS).
- Observe the conversation after the message is sent.
Expected behavior
One outgoing message should be created and displayed.
Actual behavior
Two outgoing messages are created for every message sent.
The recipient receives only one SMS/MMS, but two sent messages appear in the conversation. The duplicates are also visible in other SMS applications (including the stock/AOSP Messages app), indicating that duplicate records are being written to Android's Telephony provider rather than being a Fossify UI issue.
Screenshots/Screen recordings
Additional information
- Reproducible every time.
- Happens with both SMS and MMS.
- Clearing app cache does not help.
- Disabling delivery reports does not help.
- Stock/AOSP Messages does not reproduce the issue.
- Fossify Messages is the only default SMS application.
- Other SMS apps display the same duplicate entries because they exist in the system SMS database.
ADB query after sending a single SMS with body "Fossifytest":
adb shell content query --uri content://sms/sent --projection _id,date,date_sent,type,status,sub_id,creator,address,body | grep Fossifytest
Row: 0 _id=3300, date=1781227818202, date_sent=0, type=2, status=-1, sub_id=2, creator=org.fossify.messages, address=REDACTED, body=Fossifytest
Row: 1 _id=3299, date=1781227817753, date_sent=0, type=2, status=-1, sub_id=2, creator=org.fossify.messages, address=REDACTED, body=Fossifytest
Both rows:
- have different _id values
- have different timestamps (~449 ms apart)
- have identical body, address, status, type, creator, and sub_id values
- were created by org.fossify.messages
This appears to be a duplicate insertion into the SMS provider rather than a display issue.
- Lingua principale
- Kotlin
- Stelle
- 1.6k
- Fork
- 187
- Merge medio
- 2g 9h
- PR unite (30g)
- 20
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di FossifyOrg/Messages
-
bug needs triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 63/100
FossifyOrg/Messages#919 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
bug needs triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
FossifyOrg/Messages#897 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
bug needs triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
FossifyOrg/Messages#761 ·
I maintainer di solito rispondono entro 1 giorno
-
[Export] mms "No entries for export have been found"Forse di nuovo libera Una pull request per questa issue è stata chiusa senza essere unita. Apertabug help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 60/100
FossifyOrg/Messages#493 · 24 commenti · 3 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
bug needs triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 48/100
FossifyOrg/Messages#918 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di FossifyOrg/Messages
Issue simili
-
Improve Sort Pop-Up list...Apertaenhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno
-
:maddi-inspection-kotlin:test runs out of heap in a full maddi test run; exit 1 with no failing testApertabuild/ci front-end:kotlin
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
bisq-network/bisq-mobile#1948 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
streetcomplete/StreetComplete#7286 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno