nextcloud / nextcloud/contacts
Unable to add more than one contact in fresh install
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 642
- Forks
- 220
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 51
Description
Describe the bug
First contact create after page load works; every subsequent create in the same session
fails with "Contact not found". A hard page reload does NOT restore the ability
(contrary to typical stale-UI-state bugs).
Steps to reproduce
- Fresh Nextcloud install (Docker, nextcloud:latest, server 34.0.3.2, MariaDB 11.8.9)
- Open Contacts app; delete the single default welcome contact
- Click "+ New contact", fill in name/email, save → works (contact persists in oc_cards)
- Immediately click "+ New contact" again → error: "Contact not found"
- All subsequent create attempts fail identically
Expected behavior
Each "+ New contact" click should create a new editable contact.
Actual behavior
First create after page load works; every subsequent create in the same session
fails with "Contact not found". A hard page reload does NOT restore the ability
(contrary to typical stale-UI-state bugs).
Contact version
8.8.0 (latest available; occ app:update contacts reported "up-to-date" at the time of testing)
Operating system
Linux ubuntuserver 7.0.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Aug 1 04:26:38 UTC 2026 x86_64 GNU/Linux, Server version: 34.0.3 (Nextcloud 34, docker image nextcloud:latest)
PHP engine version
None
Web server
None
Database
MariaDB
Additional info
- Server version: 34.0.3 (Nextcloud 34, docker image nextcloud:latest)
- Contacts app version: 8.8.0 (latest available;
occ app:update contacts
reported "up-to-date" at the time of testing) - Database: MariaDB 11.8.9
- Browser: Chrome and Firefox, private/incognito windows — fails identically
- Hard refresh (Ctrl+Shift+R): does not help
- One address book originally; error reproduces in a second, newly created
address book too
Evidence that the write path itself works
- Editing an existing contact via the GUI works and changes persist to
oc_cards.carddata (verified via SQL) - Creating a new address book via the GUI works (persisted in oc_addressbooks)
- Importing a multi-contact .vcf file WORKS — all imported contacts appear
and persist, including a second and third contact (i.e. only the
single-card create flow is broken) - Error message "Contact not found" appears with no visible error in
nextcloud.log - Browser DevTools Network tab shows NO HTTP request is made at all when the
failing "+ New contact" click occurs — the failure appears to be purely
client-side (JS error in the frontend; console entries captured with
Console error at failure (captured with "Preserve log" enabled)
[ERROR] contacts: Something wrong happened while picking a file
Object { app: "contacts", uid: "", level: 2 }
Error: FilePicker: No nodes selected
fileName: http://192.168.1.119:8080/custom_apps/contacts/js/style-BlAQ7A1q.chunk.mjs
lineNumber: 3, columnNumber: 120501
stack:
Qg@http://192.168.1.119:8080/custom_apps/contacts/js/style-BlAQ7A1q.chunk.mjs:3:120501
pickNodes@http://192.168.1.119:8080/custom_apps/contacts/js/style-BlAQ7A1q.chunk.mjs:3:121414
Impact
Manual contact creation is impossible; importing a pre-built .vcf is a
functional workaround.
Reproduced 100% of attempts on a brand-new install with only default apps
(Calendar, Contacts, Mail, Nextcloud Office, Notes) installed.
Contributor 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.
Research direction
Reproduce the second-contact failure in the Contacts app and inspect the browser console and Network tab, focusing on the reported style-BlAQ7A1q.chunk.mjs FilePicker error. Trace the client-side failure from the "+ New contact" action; done means repeated clicks create editable contacts and generate the expected requests without "Contact not found".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100