Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.1.X, 2019.2.X
Votes
0
Found in
2017.3.1p1
Issue ID
1010999
Regression
No
[Perforce] Unity writes to assets that can't be checked out (e.g. exclusively checked out by another user)
To reproduce:
1. Extract the project;
2. Create a Perforce workspace A that points to the project;
3. Open the project in Unity;
4. Configure the Unity Perforce integration to use workspace A;
5. Use workspace A to submit the contents of the Assets and ProjectSettings folders to Perforce;
6. Create another Perforce workspace B that points to the same depot content, and have it point to a different folder on your machine;
7. Use workspace B to check out custom_scriptable_object.asset and custom_scriptable_object.asset.meta;
-Note: Make sure custom_scriptable_object.asset and custom_scriptable_object.asset.meta have 'exclusive checkout' (if not, press right mouse click on files > Change File Type... > Check "Exclusive Checkout");
8. Submit the changes to confirm "Exclusive Checkout"
9. Back in Unity, with workspace A, run this menu command: Custom -> Write Locked File;
10. Notice that "custom_scriptable_object.asset" is not Read-only anymore.
Expected result:
-Unity reports that custom_scriptable_object.asset cannot be checked out.
-Unity does not check out custom_scriptable_object.asset.meta.
-Unity does not write custom_scriptable_object.asset.
Actual result:
-Unity reports that custom_scriptable_object.asset cannot be checked out.
-Unity does check out custom_scriptable_object.asset.meta.
-Unity does write custom_scriptable_object.asset.
Reproduced on versions: 2017.2.2p1, 2017.3.1p4, 2018.1.0b10, 2018.2.0a4.
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
- “Assertion failed on expression” errors thrown when undoing Nodes creation with keyboard shortcut
- Crash on various stack traces when using Texture2D.CreateExternalTexture() while rendering
- Clicking on section text in Node Library > Context folder throws NullReferenceException errors
- Node Library window sections text in Context folder are not visible when Editor is set to Light Theme
- "Scene Depth Difference" Node has an input Port which is called Position WS, directly referring to the World Space Position, when only the View Space Position can reflect if the object's depth is below or above the Plane
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.0a6