# \[Help\] NC11 + Mac Sierra Contact Sync URL

**URL:** <https://help.nextcloud.com/t/help-nc11-mac-sierra-contact-sync-url/7560>\
**Category:** ℹ️ Support\
**Tags:** contacts-app\
**Created:** [January 15, 2017, 2:22pm UTC](https://help.nextcloud.com/t/help-nc11-mac-sierra-contact-sync-url/7560 "2017-01-15T14:22:26Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![georgehrke](https://help.nextcloud.com/user_avatar/help.nextcloud.com/georgehrke/32/912_2.png) [@georgehrke](https://help.nextcloud.com/u/georgehrke)\
**Post date:** [January 16, 2017, 4:26pm UTC](https://help.nextcloud.com/t/help-nc11-mac-sierra-contact-sync-url/7560/2 "2017-01-16T16:26:59Z")

</div>

No bug in NC.

Apple (both macOS and iOS) need the principal URL.  
Other clients need the address book url.

also see [https://docs.nextcloud.com/server/11/user\_manual/pim/sync\_osx.html](https://docs.nextcloud.com/server/11/user_manual/pim/sync_osx.html) 😉

> Would it be possible to simplify enrollment by performing server-side checks to determine client platform and redirect accordingly?

No, because macOS Contacts will also access [https://FQDN/remote.php/dav/addressbooks/users/USER@TLD.COM/contacts/](https://FQDN/remote.php/dav/addressbooks/users/USER@TLD.COM/contacts/). And generally returning different results for different user agents is a very ugly hack.

---

_[View the full topic](https://help.nextcloud.com/t/help-nc11-mac-sierra-contact-sync-url/7560)._