SIM cards number reversed
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
- 42/100
Línea de trabajo
No files, tests, or code entry points are named in the issue. First reproduce the reversed SIM labels on the reported Huawei P20 running Android 9, then trace how the app assigns SIM numbers to sent and received messages. Done means messages on SIM1 are marked 1 and messages on SIM2 are marked 2.
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
Android 9 - EMUI Huawei 9.1.0
Affected device model
Huawei P20 ANE-LX1
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
Reading the messages, they are affected with the wrong number SIM card.
Expected behavior
Messages sent or received by SIM1 should be marked with 1
Messages sent or received by SIM2 should be marked with 2
Actual behavior
Messages sent or received by SIM1 are marked with 2
Messages sent or received by SIM2 are marked with 1
Screenshots/Screen recordings
No response
Additional information
No response
- Lenguaje dominante
- Kotlin
- Estrellas
- 1.6k
- Forks
- 187
- Merge medio
- 1 d 15 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 · 1 comentario ·
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 · 1 comentario ·
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
-
feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
leonlatsch/Photok#816 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
owenlejeune/ArrMatey#417 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
orgzly-revived/orgzly-android-revived#1120 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
Tiqr/eduid-app-android#277 ·
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día