Search Issue Tracker
By Design
Votes
0
Found in
2017.4
2019.3.0f6
2020.2
Issue ID
1215266
Regression
No
Cannot create a new Unity project in a shared network folder with r/w access
Reproduction steps:
1. Set up a shared folder on a device in a local network with read/write access
2. Connect to that folder using another device in the network
3. Try creating a Unity project in the shared folder
Expected result: the project will be created
Actual result: the project is not created and you get an error message offering you to force quit. Force quitting throws a Fatal Error. The project created in the shared folder is not recognized by the Unity Hub (check note 3 and the images attached)
Reproducible with: 2017.4.38f1, 2018.4.19f1, 2019.3.6f1, 2020.1.0b1, 2020.2.0a2
Notes:
1. In 2018.4.19f1 and earlier the project is created without any visible errors. Unity is trying to launch but never does
2. This was tested: local network set up on Mac High Sierra, connecting via iMac Catalina
3. Some files are created such as Assets, Logs, Temp, but this varies between versions. Hub recognizes that it is a project but is not able to launch it indicating that it does not have the Unity version on the machine (the version is unidentified).
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Top-level lists are handled differently than nested lists when using JsonUtility.FromJson
- Console does not display Deprecation Warnings for certain packages
- Decal's fade occurs inconsistently when Scene and Game views are both open
- Not all Post-processing Overrides are visible when Camera Stack is applied
- Framebuffer blends material instead of rendering opaque when using Built-in Render Pipeline
Resolution Note:
Unity requires the use of memory-mapped files to work correctly, which in some operating systems doesn't work well or at all over network shares; due to that, opening projects from network shares is not supported.