The symbolic links might be sufficient, but I’ve been running this way since the betas and just re-drag the versioned R/Rscript binaries each time I upgrade (or rebuild) R. I also used the Finder’s “Go To” command to head on over /usr/local/bin and use the “Show Original” popup on both R and Rscript and dragged their fully qualified path binaries into the pane as well (you can’t see them b/c the pane is far too small).
You can do that by adding both the R executable and RStudio executable (drag their icons) to the Full Disk Access pane under the Privacy tab of System Preferences => Security & Privacy: The TLDR for getting your R/RStudio bits to work in these sandboxed areas is to grant them “Full Disk Access” (if that sounds scary, it is) permissions. Managing Mojave’s privacy protection: Privacy controlsĪnd/or Google/DuckDuckGo for macos privacy tcc full disk access as there have been a ton of blogs on this topic.Working with Mojave’s Privacy Protection.Mojave’s privacy protection is complex and will crash innocent apps.Rather than reinvent the wheel by blathering about what that means, give these links a visit if you want more background info: If you’re an R/RStudio user who has migrated to Mojave (macOS 10.14) or are contemplating migrating to it, you will likely eventually run into an issue where you’re trying to access resources that are in Apple’s new hardened filesystem sandboxes.
0 kommentar(er)
