Search Issue Tracker
Duplicate
Votes
0
Found in
2018.1.0b1
Issue ID
981057
Regression
Yes
Unity fails to resolve packages after opening a project stored in cloud storage
Steps to reproduce:
1. Download and install Microsoft OneDrive
2. Create a new Unity project in OneDrive directory
3. Close Unity
4. Wait for the project to be uploaded to OneDrive
5. Open Unity
6. Open created project
Expected results:
Project opens without any issues
Actual results:
Unity fails to resolve packages
Reproduced in: 2018.1.0b1
Didn’t reproduce in: 2018.1.0a7, 2017.3.0p1, 2017.2.1p1, 2017.1.3f1, 2017.1.0a1
Regression introduced in: 2018.1.0b1
Note: After opening the project, an error appears in the console: "Failed to initialize project : [C:/Users/USERNAME/OneDrive/PROJECT_NAME/UnityPackageManager] directory does not exist. No packages loaded.". Crashes on PackageManager::PackageAssets::RegisterPackages in Unity 2017.2 and 2017.3 instead (Case 981002)
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
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
This is a duplicate of issue #981002