can this be caused that I am saaving and creating unity project on mapped drive?
I have R: drive and its dropbox shared folder
but one of my last projects was at this drive, and it worked.
I was testing exactly same workflow, once saved at C: and secondly saved on R: and project saved on my C: is working without problems
by user 869976161550217286
Yes, that would be the root cause.
You can also read more here: Discord
I wonder why you didn’t get a warning though since we do check for the availability of symlinks on the project drive.
Changed the channel name: Build fails on Dropbox network drive
I think this is different issue where a drive is mapped - not a drive without symlink support
Dropbox / Google Drive are kind of “virtual network drives”, I thought they didn’t have symlink support either but maybe they do. We should probably exclude both, it’s not a good idea to have projects with many files on them - and as far as I’m aware there’s no .gitignore or similar for them either
I am baffled by the environments people try to use for dev like this 
if there are any tutorial makers out there encouraging this I will go tell them off personally
by user 103054507105067008
Well, I know firsthand how hard it is to get people to unlearn “put the project where my files sync between machines” and learn “the mystical source control that is git”…
Some never learn that 
I think it would be good if at some point we have some docs for it! It looks like a steep learning curve.