-
Notifications
You must be signed in to change notification settings - Fork 174
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
macos contacts app does not reflect adding or deleting contacts #575
Comments
Hello :) This is not related to nextcloud |
Hey, yes I have checked about the other macos issues, but it does not seem to be related at all. 1 I did not try to sync multiple address books or groups, just one. I did a lot of research before posting this. Syncing with macos is working with other tools like baikal or radicale. So it is highly plausible that this issue is nextcloud related. Please read the specified issue description in the post above and please reopen the issue. If you have any questions or if I can try to help like testing I`ll happily do that. Thanks |
Okay, let's do some debug then!
If it's here, then it is not a nextcloud issue but is related to mac and the synchronisation or your config |
Thanks for reopening and the detailled debug infos. I just tried and yes, the contact is there. But I already reported that behavior in my issue report. iOS and nextcloud sync, create and delete contacts. But neither writing nor deleting from nextcloud to macos seems to work. Writing from macos to nextlcoud works. Seems to something wrong in the way nextcloud tries to write to macos or tries to inform macos about updates. If you delete the complete account on macos and readd it, it reflects everything on nextcloud contacts. Must be something wrong in the way nextcloud pushes things to macos. As I´m correct baikal uses the same "technology" to sync and baikal works perfectly. Would be very nice to see it solved so it will work afterwards. I know that there are some problems floating around connecting to macos contacts, but the most have to do with nginx rewrite and wrong way of connecting. If done both correctly it should work with every carddav server. |
Yes, I still wanted to try to make sure we're on the same page for this. Therefore, I don't see much what we can do. Could it be that the mac software does not update the information automatically? |
Thanks for the explanation. You can force a sync by really quitting the contacts app and reopen it. When reopening a sync is forced. What`s strange to me is that baikal and radicale work perfectly. If for all carddav software the issue would be the same I would agree with you that it is a mac issue. But as it`s not it seems to me that nextcloud contacts does have a problem writing to the macos contacts app. |
So if you do that, the sync is done properly? |
With radicale or baikal as carddav server yes, with nextcloud as carddav server no. More precise, yes one way and no the other way. macos contacs does write to nextcloud but nextcloud does not write to macos contacts. So if a contact is added on macos it gets synced to nextcloud but if a contact is added in nextcloud it does not appear on macos. Radicale and baikal do work in both directions. |
Do you see requests in the access log coming from the mac contacts app? |
In which log? I added the nginx log to the first post. As stated the webserver log posted starts with creating a new contact on ios, then syncs it to nextcloud and then opening macos contacts, the contact does not show up in macos contacts afterwards. |
On the webserver's. :) |
yes, the log is from nginx and reflects exactly the time of the described events ;) |
sorry, just hit the wrong button when closing ;) |
as the label "needs info" is still applied, is there anything I can help with additionally? |
Hi, I can confirm this issue from @tiiiecherle Just tested with a nextcloud demo test instance and my Mac OSX contacts app. BUT ... in my case it seems that this is happen due to an issue on mac osx contacts app. Always when I changed something on a card from the contact app, all other changes where correctly synced after that. It looks like the "sync download" might have some issue on osx app? Cheers |
Just as a data point, I use iOS and MacOS, but with a NC15 (contacts 3.0.2) instance on Ubuntu (16.04), and I just created two contacts on the web interface for testing another bug, and they did create OK on my MacOS (10.14.3) contacts app just fine, so it seems likely something in the nginx or arch side maybe. |
I took some time to try this again yesterday with next cloud 15.0.5 on archlinux with all packages up-to-date and proper configuration. macOS is also up-to-date with 10.14.3. The issue still persists. macOS contacts sync once when adding the account, no more syncs possible afterwards. |
This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions. |
This problem still exists :( |
Can confirm - still exists |
Confirmed here too. I had 2 contacts in Nextcloud. I added the profile to my Mac (Mojave 10.14.6). On the Mac, I edited one contact and deleted the other one. These changes are only visible on the Mac and did not sync with the web view of Nextcloud. |
DO you have multiple addressbooks? |
yes, from different mail accounts but only one from nextcloud
|
In my case I have two addressbooks from NextCloud and a bunch of iCloud ones. |
Can any of you see PUT requests to your nextcloud server from your Apple devices? |
I see a put request when I add a new contact from MacOS: 192.168.200.101 - - [14/Jul/2020:19:20:20 +0200] "PROPFIND /remote.php/dav/addressbooks/users/ben/ HTTP/1.1" 401 557 This created the contact on NextCloud. Next I edit it from my iPhone and change a field in that record: 192.168.200.65 - - [14/Jul/2020:19:23:44 +0200] "REPORT /remote.php/dav/addressbooks/users/ben/contacts/ HTTP/1.1" 401 557 But in NextCloud the change is not visible. But here is the odd thing, sometimes it does work. I tried it a few times, also by quiting apps, reloading the NextCloud page, etc. I don't know if this matters, but the calendar works fine from MacOS and iOS. It is just the addressbook that's giving me trouble. I added both in one go using the Apple profile option in NextCloud. |
For every PUT request, can you confirm changes are properly visible? |
Still exists? |
@skjnldsv We've upgrade to v19.0.2 since. I haven't seen the problem since. |
Good to hear! :) |
Steps to reproduce
Expected behaviour
Both clients should be able to see, read and write to the address book and should reflect changes, additions and deletions.
Actual behaviour
The behaviour on the ios client is fine and matches everything that happens in the the nextlcoud contacts.
The problem occurs with the macos contacts client. If you create a contact on macos it gets synced and appears in nextcloud. But a contact created in nextcloud or in ios does not show up in macos. And if you delete a contact in nextcloud or ios it does not get deleted in macos contacts app.
Server configuration
Operating system:
archlinux
Web server:
nginx
Database:
mariadb
PHP version:
7.2.7-1
Nextcloud version: (see Nextcloud admin page)
13.0.4-1
Contacts version: (see Nextcloud apps page)
2.1.5-1
Updated from an older Nextcloud or fresh install:
fresh contacts install
Signing status:
List of activated apps:
Nextcloud configuration:
Are you using external storage, if yes which one: local/smb/sftp/...
no
Are you using encryption: yes/no
no
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
no
Client configuration
Browser:
Safari
Operating system:
macos 10.13.5
ios 11.4
CardDAV-clients:
macos contacts
ios addresss book
Logs
Web server error log
the webserver log starts with creating a new contact on ios, then syncs it to nextcloud and then opening macos contacts, the contact does not show up in macos contacts afterwards
Nextcloud log (data/nextcloud.log)
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: