Duplicate outgoing SMS/MMS entries created in Telephony provider
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 45/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Kotlin
- Estrellas
- 1.6k
- Forks
- 187
- Merge medio
- 1 d 16 h
- PR fusionados (30 d)
- 20
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de FossifyOrg/Messages
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
FossifyOrg/Messages#929 ·
Los mantenedores suelen responder en 1 día
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
FossifyOrg/Messages#927 ·
Los mantenedores suelen responder en 1 día
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 63/100
FossifyOrg/Messages#919 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
FossifyOrg/Messages#897 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
FossifyOrg/Messages#761 ·
Los mantenedores suelen responder en 1 día
Todos los issues de FossifyOrg/Messages
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
navikt/mock-oauth2-server#1129 ·
Los mantenedores suelen responder en 1 día
-
Expose `close` on SsrEngineAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
-
unconfirmed
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
thunderbird/thunderbird-android#11778 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
software-mansion/enriched-markdown#1042 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
world-federation-of-advertisers/cross-media-measurement#4709 ·
Los mantenedores suelen responder en 1 día