Search Issue Tracker

Fixed in 2020.2.X

Fixed in 2019.4.X, 2020.1.X

Votes

0

Found in

2019.3

2019.3.5f1

2020.1

2020.2

Issue ID

1232838

Regression

No

Added Asset changes are lost in Unity Collaborate when renaming new Assets with Asset Import Pipeline V2 enabled

Asset - Database

-

How to reproduce:
1. Create and open a new project
2. Set up the Unity Collaborate
3. Publish the initial changes in the Collaborate window
4. Create a new C# Script Asset in the Project window
5. Rename the C# Script Asset to anything else in the Project window

Expected result: It is still possible to Publish the change with the new Asset name in the Collaborate window
Actual result: The new Asset isn't recognized as a change and therefore cannot be Published in the Collaborate window

Reproducible with: 2019.3.8f1 (1.2.16, 2.0.0-preview.17, AIPV2), 2020.1.0b3 (1.3.7, 2.1.0-preview.3), 2020.2.0a5 (1.3.7)
Not reproducible with: 2017.4.39f1, 2018.4.20f1 (1.2.15, 1.2.16, 2.0.0-preview.17), 2019.3.8f1 (1.2.16 AIPV1)
Could not test with: 2020.1.0b3 (AIP1), 2020.2.0a5 (AIP2) (the option to use AIP1 isn't available)

Notes:
-A workaround for this is to reimport the Asset
-This also works with already existing Assets being imported to the project as shown in "ImportedAssetExpected.mp4" and "ImportedAssetActual.mp4" videos
-This is caused by the Asset Import Pipeline V2 since that is the main change going from 2018.4 to 2019.3 and choosing to use Asset Import Pipeline V1 in a project where both are available makes the bug not reproducible
-The initial changes mentioned above are usually the "SampleScene" Scene and "Scenes" folder
-The package versions mentioned in the parentheses are versions of the Unity Collaborate package

  1. Resolution Note (fix version 2020.2):

    Fixed in 2020.2.0a21

Add comment

Log in to post comment