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
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
- Element name field has no character limit in UI Builder
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
Add comment