Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0a2
Issue ID
885953
Regression
Yes
Collab - Collab window will display 0 changes when there actual changes waiting to be published.
Assuming the user has a collab-enabled project, has done his first publish (this is not necessary, however) and there are some files with changes waiting to be published.
1. Manipulate an asset (rename, recase, edit, create all work) and publish.
2. Cancel (note that this obviously works better with a larger file as the window to cancel does not require feline-like reflexes)
Observed results: Note that the Collab window will display two issues:
a) It will display the error "Cannot submit change to server" (ALREADY logged: https://fogbugz.unity3d.com/f/cases/881196/ - Closing Duplicate in favor of this one)
b) It will ask you to Publish again but will display "0 changes"
Expected Result: The message should be "Operation Cancelled" and there should be changes displayed on the Collab window.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment