New contact not immediately found
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
The payload names no source files or tests, so start by reproducing the steps on Android with the contacts search screen. Check whether a contact saved in the app is visible to the contacts search right away, or only after a refresh or restart. Done means a newly added contact appears in search without restarting the app, with a test covering that case if one is feasible.
Written by the indexing model from the issue text.
Description
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.11.1
Affected Android/Custom ROM version
Android 15 Xiaomi HyperOS 202110
Affected device model
Xiaomi 12
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
Enter new contact in Phone app
Hit contacts button
Search the new contact name
Not found
Expected behavior
Enter new contact in Phone app
Hit contacts button
Search the new contact name
Found
Actual behavior
Not found
Screenshots/Screen recordings
No response
Additional information
No response
- Dominant language
- Kotlin
- Stars
- 1.4k
- Forks
- 213
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 14
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FossifyOrg/Phone
-
feature request needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
FossifyOrg/Phone#922 ·
Maintainers usually reply within 4 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FossifyOrg/Phone#914 · 2 comments ·
Maintainers usually reply within 4 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FossifyOrg/Phone#889 ·
Maintainers usually reply within 4 days
-
feature request needs triage
Difficulty 2/5 Half a day Newbie friendliness 60/100
FossifyOrg/Phone#822 ·
Maintainers usually reply within 4 days
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
FossifyOrg/Phone#921 ·
Maintainers usually reply within 4 days
All issues in FossifyOrg/Phone
Similar issues
-
documentation good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
djazairdev/wilayas#23 ·
Maintainers usually reply within 1 day
-
[BUG] Navigation drawer drops library-name suffixes without ellipsis (1.0.8, NVIDIA Shield)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
damontecres/Wholphin#2069 ·
Maintainers usually reply within 1 day
-
Android (vision-camera-location): HybridLocationManager never quits its HandlerThread on disposeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
margelo/react-native-vision-camera#4217 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
saisaharsh3/Leftovers#13 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 67/100
navikt/esyfo-narmesteleder#700 ·
Maintainers usually reply within 1 day