Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
3
Found in
2017.3.0a7
Issue ID
950014
Regression
No
[FixInGit1.5] Changes can not be pushed if there are switched names between 2 files
To reproduce:
1. Create a new project
2. Create A and B scripts
3. Push changes
4. Edit A and B scripts
5. Switch scripts names
6. Try to push changes or revert assets
Expected: changes will be pushed/assets will be reverted
Actual: when pushing changes, error is thrown:
'[Collab] CreateRevisionValidator::InvalidRequestError: Multiple conflicting changes have been noticed on ["Assets/b.cs", "Assets/b.cs.meta", "Assets/a.cs", "Assets/a.cs.meta"], please restart Unity.'
And if reverting assets 'File already exists' is thrown.
Note: Also, if you try to push changes and then revert asset, you will notice, that error message covers warning.
Workaround: restart Unity
Reproduced on: 5.5.2p4, 5.5.4p1, 5.6.3p1, 2017.1.1f1, 2017.2.0b10, 2017.3.0a7
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
danielfangzhu
Aug 13, 2020 00:16
Same here, I would love to see this fixed.
jrronzani
Jun 10, 2020 09:02
I encounter this issue a lot since I'm working on a puzzle game with lots of levels that I am constantly renaming and rearranging. I have to restart Unity almost every time I need to publish changes on Collab.