Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Failure to import contacts, "Cannot cast value for is_primary to a Integer"

Aperta
#560 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
Mezza giornata
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
android, kotlin
Ambito
mobile

Direzione di ricerca

The stack trace ends in Android's ContactsProvider, so the cast error comes from a ContentValues insert, and the app's VCF import code is the likely source of the boolean is_primary value. Search the Kotlin import code for is_primary and check how it is written into ContentValues. Reproduce by importing a VCF with several phone numbers and watching the logcat. Done when the import completes without the ClassCastException and the dialog closes after OK.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug needs triage
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

/e/OS 3.7.3 based on Android 15

Affected device model

Fairphone 6

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug
  1. adb push contacts_20260527_224723.vcf /storage/self/primary/
  2. Go to 'Settings'
  3. Select 'Import contacts from a .vcf file'
  4. Select the vcf
  5. keep "target contacts source" as "DEVICE"
  6. press OK
Expected behavior

The dialog should not remain after we select "OK", and the cast exception should not be there.

Actual behavior

After a few seconds of "Importing..." toast displayed on top of the dialog just validated, the toast goes away while the dialog remains, then if people just wait (which is not what most people do in front of a long wait, see below) the dialog disappears, we're back to the UI, and at some point we get a notification that contacts were imported.

During this import time we can see loads of errors like the one below logged, I assume their large number causes the slowdown, apparent lack of responsiveness, and lets the dialog possible to interact with during import:

05-27 23:39:21.765  2299  5017 W AppSearchIcing: icing-search-engine.cc:364: Error: 5, Message: Document (android$contacts/, 3992) not found.
05-27 23:39:21.788  5496 11967 E ContentValues: Cannot cast value for is_primary to a Integer: false
05-27 23:39:21.788  5496 11967 E ContentValues: java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.Number
05-27 23:39:21.788  5496 11967 E ContentValues: 	at android.content.ContentValues.getAsInteger(ContentValues.java:350)
05-27 23:39:21.788  5496 11967 E ContentValues: 	at com.android.providers.contacts.DataRowHandler.insert(DataRowHandler.java:122)
05-27 23:39:21.788  5496 11967 E ContentValues: 	at com.android.providers.contacts.DataRowHandlerForCommonDataKind.insert(DataRowHandlerForCommonDataKind.java:47)
05-27 23:39:21.788  5496 11967 E ContentValues: 	at com.android.providers.contacts.DataRowHandlerForPhoneNumber.insert(DataRowHandlerForPhoneNumber.java:53)
05-27 23:39:21.788  5496 11967 E ContentValues: 	at com.android.providers.contacts.ContactsProvider2.insertData(ContactsProvider2.java:3435)
05-27 23:39:21.788  5496 11967 E ContentValues: 	at com.android.providers.contacts.ContactsProvider2.insertInTransaction(ContactsProvider2.java:3220)
05-27 23:39:21.788  5496 11967 E ContentValues: 	at com.android.providers.contacts.AbstractContactsProvider.insert(AbstractContactsProvider.java:161)
05-27 23:39:21.788  5496 11967 E ContentValues: 	at com.android.providers.contacts.ContactsProvider2.insert(ContactsProvider2.java:2404)
05-27 23:39:21.788  5496 11967 E ContentValues: 	at android.content.ContentProvider.insert(ContentProvider.java:1961)
05-27 23:39:21.788  5496 11967 E ContentValues: 	at android.content.ContentProviderOperation.applyInternal(ContentProviderOperation.java:375)
05-27 23:39:21.788  5496 11967 E ContentValues: 	at android.content.ContentProviderOperation.apply(ContentProviderOperation.java:352)
05-27 23:39:21.788  5496 11967 E ContentValues: 	at com.android.providers.contacts.AbstractContactsProvider.applyBatch(AbstractContactsProvider.java:286)
05-27 23:39:21.788  5496 11967 E ContentValues: 	at com.android.providers.contacts.ContactsProvider2.applyBatch(ContactsProvider2.java:2921)
05-27 23:39:21.788  5496 11967 E ContentValues: 	at android.content.ContentProvider.applyBatch(ContentProvider.java:2695)
05-27 23:39:21.788  5496 11967 E ContentValues: 	at android.content.ContentProvider$Transport.applyBatch(ContentProvider.java:524)
05-27 23:39:21.788  5496 11967 E ContentValues: 	at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:212)
05-27 23:39:21.788  5496 11967 E ContentValues: 	at android.os.Binder.execTransactInternal(Binder.java:1406)
05-27 23:39:21.788  5496 11967 E ContentValues: 	at android.os.Binder.execTransact(Binder.java:1350)

(I'm pretty sorry the following description highlights quite a few bugs showing as a side effect of the above large delay, it would seem awkward to log them separately, I guess they all appear because that dialog was never intended to be interacted with more than once, and disabling its controls would be enough to avoid all of them)

During this long time, trying to understand what was going on, I successively did:

  • press "OK" again, which triggers a new import (which is not necessarily understood as such initially, only while browsing, when seeing the multiple "DEVICE" lines denoting dups)
  • press outside the dialog, after which we see a partial import (visible with only a few letters on the alphabet index on the right). But then after selecting all and deleting to prepare a new import attempt, I notice that more contacts arrived in the meantime
  • press "cancel", which actually seems to stop the importing, but after deleting all the selectable records, I still see more of them actually appeared later
Screenshots/Screen recordings

No response

Additional information

This is an import of a 536-records VCF file generated by Fossify Contacts 1.6.0 on a OnePlus 6 running OxygenOS 11.1.2.2 based on Android 11.

Lingua principale
Kotlin
Stelle
917
Fork
73
Merge medio
2g 2h
PR unite (30g)
9

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di FossifyOrg/Contacts

Tutte le issue di FossifyOrg/Contacts

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.