Search Issue Tracker

Won't Fix

Votes

0

Found in

2017.4

2018.4

2019.1

2019.2

2020.1

2020.2

2020.2.0a11

Issue ID

1246521

Regression

No

[Packman] Upgrading unity project from scene file leads to package mismatch errors

Packman

-

Open Unity 2020.2.0a11 Scene file by double click on it while 2019.3.14f1 is opened which leads to package errors in the console.

Pre Condition: Have at least two projects with at least one scene in each on your machine.

Steps to Repro:

1. Open a new Project in Unity 2019.3.14f1
2. Open a new project in Unity 2020.2.0a11
3. Close the 2020.2.0a11 project and double click on the Scene file in the Explorer/Finder
4. Click the open button in the "About to open another project" popup
5. Click on the Continue button on the "Opening Project in Non-Matching Editor Installation" popup

Expected Result:
Scene should be open in the Editor with updated packages

Actual Result:
Package mismatch errors are thrown

Reproducible on: 2020.2.0a11, 2020.1.0b9, 2019.2.12f1, 2019.1.14f1, 2018.4.14f1, 2017.4.20f1

Environment: Windows 10 and Mac 10.14

Stack Trace:
Failed to load 'C:/Users/Admin/Downloads/New Unity Project (115)/Library/ScriptMapper'. File may be corrupted or was serialized with a newer version of Unity.

Failed to load 'C:/Users/Admin/Downloads/New Unity Project (115)/Library/MonoManager.asset'. File may be corrupted or was serialized with a newer version of Unity.

  1. Resolution Note:

    For the time being, opening a project in an older version is unsupported.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.