Following up my note: yes, granting Full Disk Access to /usr/sbin/cron solved the issue.
So, it looks like you need to grant Full Disk Access to whatever program is launching rsync.
dreby
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
From
Boston, MA, United States
Post
Replies
Boosts
Views
Activity
Same issue. I wrote a backup script (/usr/local/bin/backup) that uses rsync to copy /Users/Myname to a mounted network drive. It works perfectly when I run the script by hand, but when I run it in my personal crontab, I get these errors:
rsync: opendir "/Users/Myname/.Trash" failed: Operation not permitted (1)
rsync: opendir "/Users/Myname/Documents" failed: Operation not permitted (1)
rsync: opendir "/Users/Myname/Downloads" failed: Operation not permitted (1)
...
I granted Full Disk Access to both /usr/bin/rsync and my script, and it didn't make any difference.
This is in Catalina 10.15.3.
Any suggestions?
I am tempted to grant Full Disk Access to bash, but that would seem to defeat the purpose of access control....
UPDATE: I found an article on Stack Exchange (apple.stackexchange.com/questions/375383/rsync-in-cron-on-catalina-no-longer-working) that says for cron scripts to work in Catalina, you have to grant Full Disk Access to /usr/sbin/cron. I'll try that next.