Contact groups deleted by GoogleContacts on phone storage adressbook still visible in FossifyContacts
Los mantenedores suelen responder en 4 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Tranquilo
- Área
- mobile-dev
Línea de trabajo
Start by tracing how FossifyContacts loads and refreshes groups from Android's device-storage address book; the issue does not name a source file or test. Reproduce by deleting a group with Google Contacts and checking FossifyContacts before and after a reboot. Done means the deleted group disappears in FossifyContacts without requiring a reboot.
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.6.0
Affected Android/Custom ROM version
Android 11 / but likely not depending on
Affected device model
Motorola One Hyper
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
- Create a group in device storage adressbook (After restoring Contacts on this device, groups were created inside the phone storage adressbook.)
- Remove group using GoogleContacts from device adressbook (To remove them I re-activated the GoogleContacts-app and choose the Device adressbook then deleted the not needed group labels/names)
- re-boot the device
Expected behavior
When a group label/name is removed from any adressbook by other apps, for fossifyContacts it is also removed.
Actual behavior
When a group label/name is removed from phone storage adressbook by other app (GoogleContacts) for fossifyContacts it still exists.
Maybe happens for other adressbook entrys too.
Screenshots/Screen recordings
List with faulty (multiple) entrys
Group list in GoogleContacts from device storage with unwanted groups
Look after deleting in GoogleContacts
Look after deleting in FossifyContacts
Additional information
After re-boot, deleted group labels/names in the Google-Account adressbook did not show up anymore in FossifyContacts, though only after the re-boot.
Only while writing this bug I figured out how to delete a group using fossifyContacts. Long press on group name.
Without opening an issue right now for: For simplicity, delete and change name could (also) be visible when group opened and/or on group tab.
Hotfix: Use delete function inside FossifyContacts and "delete" again.
- Lenguaje dominante
- Kotlin
- Estrellas
- 917
- Forks
- 73
- Merge medio
- 5 d 8 h
- PR fusionados (30 d)
- 7
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/Contacts
-
feature request needs triage
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
FossifyOrg/Contacts#176 · 1 comentario ·
Los mantenedores suelen responder en 4 días
-
bug needs triage
Dificultad 3/5 1-2 días Aptitud para principiantes 64/100
FossifyOrg/Contacts#618 ·
Los mantenedores suelen responder en 4 días
-
feature request needs triage
Dificultad 3/5 1-2 días Aptitud para principiantes 65/100
FossifyOrg/Contacts#614 · 1 comentario ·
Los mantenedores suelen responder en 4 días
-
New field: IBANAbiertofeature request needs triage
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
FossifyOrg/Contacts#613 ·
Los mantenedores suelen responder en 4 días
-
bug needs triage
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
FossifyOrg/Contacts#612 · 5 comentarios · 1 reacción ·
Los mantenedores suelen responder en 4 días
Todos los issues de FossifyOrg/Contacts
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
Kotlin/kotlin-lsp#288 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
johanhaleby/occurrent#1261 ·
Los mantenedores suelen responder en 1 día
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
chrisbanes/haze#1536 ·
Los mantenedores suelen responder en 1 día
-
Cassiopeia drops the `präsentiert von` credit printed in the event bodyPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertoafk-ok area:data-quality importer size:S
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
enorm-labs/event-junkie#3166 ·
Los mantenedores suelen responder en 1 día
-
enhancement good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
rajpreetcodes/Skills_MCP_Server#25 ·
Los mantenedores suelen responder en 1 día