After updating to 5.2 I’m getting this error when trying to save a scene from time to time:
I’m on Yosemite 10.10.4 btw.
edit: Deleted custom script that had nothing to do with the issue.
Just found that Github Desktop was preventing me from saving scenes.
Now I wonder, I’m the only one??
Yup, definitely seeing this all the time with Unity 5.2 and Github Desktop open. Thanks for the tip!
After updating to 5.2,
on some special occasions,
I’m seeing this one, too. (these rhymes!)
I’m not using Github, though. So Github seems to be non-related for me.
I use to click the magnificent Cancel button and just hope it didn’t mess up anything. So far, I haven’t run into further problems.
I’ve found the offending software by running the following command:
lsof +D /path/to/unity/project/root
It’ll tell you which processes are using/locking which files.
In this case, I’m not sure which of the two is screwing it up.
Running that in the OSX terminal, right?
After doing so, it didn’t show me anything.
Alright, I’m getting this error now every time I’m trying to open a project while already having a project opened.
To avoid this, I have to restart Unity and load the project afterwards.
Also, if I don’t restart Unity and just cancel the Moving File Failed message, I won’t be able to click any UI items, nor will any of OnMouseDown() or OnMouseUp() / OnMouseDrag() work.
I don’t know why, but restarting Unity will fix that issue most of the time.
I’ve updated to El Capitan and the problem is not happening anymore, not sure if because of the update though. ¯_(ツ)_/¯
1 Like