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
1
Found in
2017.1.1f1
Issue ID
952679
Regression
No
[FixInGit1.4] Cannot revert moving an existing file into a new (not checked in) folder, get error "File cannot be reverted"
DESCRIPTION:
If a collab user creates a new folder (not checked in), then moves an existing asset (checked in / no changes to the asset) into that new folder, they cannot revert that move from the collab toolbar.
REPRO:
1. Open a collab-enabled project with some existing assets
2. Create a new folder.
3. Move any existing asset into the new folder.
4. Open the collab toolbar.
5. Find the file that you moved and click the Revert button.
RESULTS:
"File cannot be reverted" error
EXPECTED:
Users can revert file moves
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Specular lighting visible in a camera with Path Tracing when Preserve specular lighting is disabled in observed material
- Cinemachine package throws CS1061 errors in the Console when installed in a project that has HDRP and URP installed
- Editor.log file size grows rapidly when a scene exceeds the "Maximum Shadow on Screen" limit setting in the HDRP Asset
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
Add comment