Contact groups deleted by GoogleContacts on phone storage adressbook still visible in FossifyContacts
I maintainer di solito rispondono entro 4 giorni
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 48/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Tranquilla
- Ambito
- mobile-dev
Direzione di ricerca
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.
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.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.
- Lingua principale
- Kotlin
- Stelle
- 917
- Fork
- 73
- Merge medio
- 5g 8h
- PR unite (30g)
- 7
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/Contacts
-
feature request needs triage
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
FossifyOrg/Contacts#176 · 1 commento ·
I maintainer di solito rispondono entro 4 giorni
-
bug needs triage
Difficoltà 3/5 1-2 giorni Idoneità per principianti 64/100
FossifyOrg/Contacts#618 ·
I maintainer di solito rispondono entro 4 giorni
-
feature request needs triage
Difficoltà 3/5 1-2 giorni Idoneità per principianti 65/100
FossifyOrg/Contacts#614 · 1 commento ·
I maintainer di solito rispondono entro 4 giorni
-
New field: IBANApertafeature request needs triage
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
FossifyOrg/Contacts#613 ·
I maintainer di solito rispondono entro 4 giorni
-
bug needs triage
Difficoltà 4/5 3-5 giorni Idoneità per principianti 52/100
FossifyOrg/Contacts#612 · 5 commenti · 1 reazione ·
I maintainer di solito rispondono entro 4 giorni
Tutte le issue di FossifyOrg/Contacts
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
Kotlin/kotlin-lsp#288 ·
-
needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
chrisbanes/haze#1536 ·
I maintainer di solito rispondono entro 1 giorno
-
Cassiopeia drops the `präsentiert von` credit printed in the event bodyForse già presa Una pull request collegata a questa issue è aperta o già unita. Apertaafk-ok area:data-quality importer size:S
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
enorm-labs/event-junkie#3166 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
rajpreetcodes/Skills_MCP_Server#25 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
com-lihaoyi/mill#7776 ·
I maintainer di solito rispondono entro 1 giorno