This isn't a Homestead issue, but an issue with the current Vagrant release and Mac OS Catalina when using NFS exports.
Until Vagrant is updated to resolve this issue, it might be worth highlighting it for users who have upgraded to Catalina and are unable to launch Homestead.
Workaround is to prefix each folder in Homestead.yaml with /System/Volumes/Data/Users, removing ~ and make the same change in /etc/exports.
e.g. ~/taylor/Laravel would become /System/Volumes/Data/Users/taylor/Laravel.
Second potential issue with upgrading to Catalina is bash is being phased out for zsh, and users may have replaced their shell with zsh (or have it as default if it's a new install).
If so, the homestead function added to ~/.bash_profile would need to be added to ~/.zshrc instead. Simply renaming ~/.bash_profile should work.
Here's the corresponding Vagrant issue: https://github.com/hashicorp/vagrant/issues/10961
Update/Solution:
All seems to be working now.
https://github.com/hashicorp/vagrant/issues/10961#issuecomment-541070382
In other words people need to be aware that /sbin/nfsd now has to be granted full disk access if ones files reside in the Documents folder after the Catalina update.
As far as i can see the issue _should have been_ resolved in the new Vagrant 2.2.6 release.
But updating following musikovs post i now get this when running "homestead up":
homestead: Bindfs 1.13.7 is installed
==> homestead: Machine is ready to use bindfs!
==> homestead: Creating bind mounts after synced_folders...
==> homestead: Cannot create bind mount from '/home/vagrant/Code' to '/home/vagrant/Code': Source path '/home/vagrant/Code' doesn't exist
Upgraded to latest Vagrant 2.2.6 and also today 2nd update of MACOs Catalina and still doesn't work.
When I specify the folder mapping to -> type: "nfs" - it throws the usual errors and when I ssh to vagrant box, the synced folders are empty. When I remove the NFS option, it works fine.
The tried the other idea - deleted /etc/exports, vagrant destroy, re-enabled NFS on all synced folders, Vagrant up and this time it worked fine.
Most helpful comment
Upgraded to latest Vagrant 2.2.6 and also today 2nd update of MACOs Catalina and still doesn't work.
When I specify the folder mapping to -> type: "nfs" - it throws the usual errors and when I ssh to vagrant box, the synced folders are empty. When I remove the NFS option, it works fine.
The tried the other idea - deleted /etc/exports, vagrant destroy, re-enabled NFS on all synced folders, Vagrant up and this time it worked fine.