Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.2.0f1
Issue ID
953995
Regression
No
Using Collab, adding an asset, publishing the change, and then restoring clean to before it will spam console about meta files
What was expected?:
Adding an asset or folder to a project, publishing the change, and then restoring clean to a commit before that change should result in a clean local project as it was before the new asset or folder was added.
What actually happened?:
Technically correct behavior occurs, but as part of the process, it orphans the .meta file(s) for the newly added asset(s) and the cleanup of it produces console warnings.
How do you reproduce this problem?:
1) Add a new asset
2) Publish change
3) Click "go back" to second to last revision
4) Update to lastest commit
5) Restart Unity
6) Check to see there are no changes pending, as expected, but you got some console warnings along the way complaining about orphaned meta files.
Discovered on the 2017.2.0f1 RC1 build.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [RenderGraph] [CameraStacking] Passes are failing when CameraStacking and RG are enabled
- Physics and Raycast have different behavior when enum is exposed in the Editor
- TextField's text is mixed up and overlapping when "Noto Sans-Display" font is used
- TutorialManager Warnings are thrown when creating Test Track, LEGO or 2D Platform microgame template projects
- Incorrect ScrollToItem behavior when called on a deattached ListView
Add comment