-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: System address book is not syncable #38141
Labels
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
bug
feature: carddav
Related to CardDAV internals
integration
Comments
ChristophWurst
added
bug
1. to develop
Accepted and waiting to be taken care of
integration
feature: carddav
Related to CardDAV internals
labels
May 9, 2023
Testing with DAVx5Initial user address book sync
Initial system address book sync
|
12 tasks
ChristophWurst
added
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
and removed
1. to develop
Accepted and waiting to be taken care of
labels
May 9, 2023
Just saw system contacts on my phone. So it must work. I'll check again. |
It works just fine. Also differential sync of a display name is propagated to my phone. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
bug
feature: carddav
Related to CardDAV internals
integration
Bug description
The exposed system address book should be syncable like any other address book.
Steps to reproduce
system
addressbookExpected behavior
It syncs
Installation method
None
Nextcloud Server version
24
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
No response
List of activated Apps
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: