Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.2.0f2
Issue ID
1058377
Regression
Yes
Unity 2018.2 does not pick up that it needs to update the manifest from 2018.1 if project downloaded from Collab
Repro steps:
1. Make a NEW project in Unity 2018.1
2. Enable Collaborate
3. Add a package (for example, Post Processing Stack)
4. Commit to Unity 2018.1
5. Delete the project locally
6. Open Unity 2018.2.0f2 and download the project from the cloud.
Notice:
- no warnings that you're opening the project with a newer Unity version
- errors in regards to missing packages
- Package Manager window cannot be opened
- manifest.json only has that one Post Processing package in it (compared to the large number of required packages for Unity 2018.2)
Workaround: Download the project with Unity 2018.1 and save it locally and then proceed to upgrade it to Unity 2018.2
Second workaround: Use Help -> Reset Packages to Default
Regressed version: Unity 2018.2.0b8
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment