Failure to import contacts, "Cannot cast value for is_primary to a Integer"
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
adb push contacts_20260527_224723.vcf /storage/self/primary/- Go to 'Settings'
- Select 'Import contacts from a .vcf file'
- Select the vcf
- keep "target contacts source" as "DEVICE"
- 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.
- 主要语言
- Kotlin
- 星标
- 917
- 派生
- 73
- 平均合并
- 2 天 2 小时
- 30 天内合并 PR
- 9
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
FossifyOrg/Contacts 的其他 Issue
-
feature request needs triage
难度 1/5 1 小时以内 新手友好度 72/100
FossifyOrg/Contacts#176 · 1 条评论 ·
维护者通常 1 天内回复
-
bug needs triage
难度 3/5 1-2 天 新手友好度 65/100
FossifyOrg/Contacts#630 ·
维护者通常 1 天内回复
-
bug needs triage
难度 3/5 1-2 天 新手友好度 64/100
FossifyOrg/Contacts#618 ·
维护者通常 1 天内回复
-
feature request needs triage
难度 3/5 1-2 天 新手友好度 65/100
FossifyOrg/Contacts#614 · 1 条评论 ·
维护者通常 1 天内回复
-
New field: IBAN未关闭feature request needs triage
难度 4/5 3-5 天 新手友好度 48/100
FossifyOrg/Contacts#613 ·
维护者通常 1 天内回复
查看 FossifyOrg/Contacts 的全部 Issue
相似的 Issue
-
Moshi and Gson JSON adapters fail for messages with a map<bool, V> field可能已有人在做 @auraseb 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
bug Missing saved game
难度 2/5 1-3 小时 新手友好度 72/100
yairm210/Unciv#15826 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
AniTrend/anitrend-v2#1344 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
zhanghai/MaterialFiles#1659 ·
-
难度 2/5 1-3 小时 新手友好度 66/100
Droid-Deck/DroidDeck#1098 ·
维护者通常 1 天内回复