# Source control problem with new Catalina-enforced symlinks

**URL:** <https://qa.fmod.com/t/source-control-problem-with-new-catalina-enforced-symlinks/15700>\
**Category:** FMOD Studio\
**Created:** [April 28, 2020, 2:05am UTC](https://qa.fmod.com/t/source-control-problem-with-new-catalina-enforced-symlinks/15700 "2020-04-28T02:05:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![KurtHarlandLarson](https://avatars.discourse-cdn.com/v4/letter/k/848f3c/32.png) [@KurtHarlandLarson](https://qa.fmod.com/u/KurtHarlandLarson)\
**Post date:** [April 28, 2020, 2:05am UTC](https://qa.fmod.com/t/source-control-problem-with-new-catalina-enforced-symlinks/15700/1 "2020-04-28T02:05:50Z")

</div>

So, like many teams, after Catalina, we had to create a symlink to our ‘/projects’ folder called ‘/Users/Shared’ to get around the can’t-write-to-root problem.

But Perforce still knows it is dealing with ‘/projects’.

But Studio is asking Perforce to save a file in ‘Users/Shared’.

Any advice other than giving up on version control integration? ☹

---

<div class="post-metadata">

**Author:** ![KurtHarlandLarson](https://avatars.discourse-cdn.com/v4/letter/k/848f3c/32.png) [@KurtHarlandLarson](https://qa.fmod.com/u/KurtHarlandLarson)\
**Post date:** [April 29, 2020, 9:56pm UTC](https://qa.fmod.com/t/source-control-problem-with-new-catalina-enforced-symlinks/15700/2 "2020-04-29T21:56:37Z")

</div>

Resolved this by making a new Perforce workspace with the REAL path instead of the symlink path.