export contacts to a .vcf fails with "ERROR: java.lang.illegal Argument Exception: jav..."
Los mantenedores suelen responder en 4 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 50/100
Línea de trabajo
Start by reproducing the failure through Settings → export contacts to a .vcf file, including contact sources and saving the export. Then trace the contact-export flow and investigate why this device's contact data causes an IllegalArgumentException; the issue does not name source files or tests. Done means exporting all contacts creates a nonempty VCF that can be imported without errors.
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
LineageOS 22.2-20251202-microG-axolotl (Android 15)
Affected device model
SHIFT6mq (axolotl)
How did you install the app?
F-Droid
Steps to reproduce the bug
1: co to Settings
2: click on: export contacts to a .vcf file
3: click on: include contact sources
4: select: "DEVICE" (it's the same result if I include all sources)
5: click on: OK
6: click on: save (german: speichern)
7: The Error shows up "ERROR: java.lang.illegal Argument Exception: jav..."
8: the exported .vcf file (contacts_20260825_120500.vcf) is empty (0 Bytes)
Expected behavior
Expected behaviour:
create a backup of all contacts without problems, which can later be imported without bugs or errors.
Actual behavior
Actual behaviour:
One ends up with an empty .vcf file and the error: "ERROR: java.lang.illegal Argument Exception: jav..."
Screenshots/Screen recordings
Additional information
Additional information:
The bug exists a very long time (multiple years) unchanged. It was even there when the application was a part of Simple Mobile Tools and before Fossify was a thing. I hoped the next time I need to migrate to another device the problem would be fixed by someone else experiencing the same problem, but obviously it still hasn't. The last time I changed my phone to a newer model I needed to export just a few contacts one by one in order to circumvent the error from happening. I think the problem is caused by the number of contacts which I have (358 contacts as of today) and the amount of information inside some of them. I have noted a few infos like opening hours and similar things in some of them, in the "Notes" field.
- 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 1/5 Menos de una hora Aptitud para principiantes 73/100
tortuvshin/open-apps#377 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
supabase-community/supabase-kt#1413 ·
Los mantenedores suelen responder en 5 días
-
Type: Possible bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
spacecowboy/Feeder#1258 ·
Los mantenedores suelen responder en 1 día
-
[Submission] 抖音火山版Abiertosubmit-adaption submit-adaption-pre
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
BetterAndroid/android-notification-icon-project#744 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
utopia-rise/godot-jvm#1004 ·
Los mantenedores suelen responder en 1 día