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 Compiler IPC Exception and Editor Crash on AMD 9000-X3D CPU series
- Editor crashes in TextLib::FindIntersectingLink when hovering UITK Labels with <link> tags rendered via ATG
- Crash on mono_log_write_logfile when more than one copy of bee_backend is running
- NativeList<T>.ParallelWriter.AddNoResize() causes memory corruption when used in a [BurstCompile] IJobParallelFor on Web builds
- Realtime reflection probe changes light strength when removing light sources using URP WebGL
This is a duplicate of issue #981002