Search Issue Tracker

Fixed in Unity 2017.3.0f3

Votes

1

Found in

2017.2.0f1

Issue ID

952686

Regression

No

Collab: When publish failed due to "Cannot copy file" error, client thinks some files are published leading to bad sync state

Collab

-

-

Priority: 2Necessary for shipping a final release

-

Severity: 1Crash, freeze, data loss, work stops

DESCRIPTION:
If a collab publish fails due to a "Cannot copy file" error, most/all of the files that COULD be copied are marked in the editor as published even though they have not been.

Assuming that you resolve the "cannot copy file" error, the only files published are the ones that couldn't originally be published - all the files that the local editor thinks WERE published are not actually published. Because the editor acts as if these files are published, you cannot publish them normally.

REPRO STEPS:
1. Add multiple files to project as new assets
2. Save project
3. Select one of those files and use a file locking tool / script to lock one of the files (you can find example powershell scripts via google)
4. Attempt to publish changes using collab

RESULTS:
Publish fails with "Cannot copy file" error, but some/all of the files are now marked in the editor UI as synced to the cloud when they are not.

REPRO RATE:
5/5

VERSIONS REPRODUCED IN:
2017.2.0f1
2017.1.1f1

Comments (2)

  1. D21b0457600588ab018a680e598d0ea7?d=mm

    BryanO

    May 17, 2019 06:49

    I ahve the same issue 2018.4 Collab version 2

  2. 6cbf55bfaf4555981245f5edeb3b2f67?d=mm

    HaakonL

    Feb 15, 2019 14:29

    This bug is back in 2018.3.5f1.

All about bugs

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