Using "Manage shown contact fields" when adding a new contact can result in some filled input fields getting erased
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
The payload names no source file, so start from the add-new-contact screen and the three-dots menu action "Manage shown contact fields", then find where that action changes the visible fields and whether the form is rebuilt and loses its typed values. Reproduce the steps in the report on a debug build. Done means first name, surname and notes keep their text after ticking a field such as nickname, with a test or manual check that covers it.
由索引模型根据 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.5.0
Affected Android/Custom ROM version
Android 15
Affected device model
Moto G84
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
- With default shown fields setting, start to add a new contact
- Fill input fields, especially first name, surname and notes
- Open the three dots menu > Manage shown contact fields
- Tick for example nickname: you want to add a nickname to this contact
- While some input fields remains untouched (email, phone number), some others gets reset, like both name fields or the Notes one.
Expected behavior
What user already filled/wrote should remain here and not be erased.
Actual behavior
Some already filled input fields gets erased.
Screenshots/Screen recordings
No response
Additional information
No response
- 主要语言
- 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
-
design good first issue help wanted
难度 2/5 1-3 小时 新手友好度 68/100
scribe-org/Scribe-Android#739 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 76/100
xybrid-ai/xybrid#661 · 1 条评论 ·
维护者通常 1 天内回复
-
android bug kotlin vulkan
难度 2/5 1-3 小时 新手友好度 68/100
maplibre/maplibre-native-ffi#852 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
-
难度 1/5 1 小时以内 新手友好度 86/100
维护者通常 1 天内回复