Search Issue Tracker
Fixed
Votes
1
Found in [Package]
1.16.6
Issue ID
ADDR-1794
Regression
Yes
A false popup appears when changing Addressable settings in a project connected to Perforce
How to reproduce:
1. Open the attached "1309513.zip" project
2. In Edit -> Project Settings -> Version Control connect the project via Perforce (Perforce integration: https://docs.unity3d.com/Manual/perForceIntegration.html)
3. In the Hierarchy select "Main Camera"
4. Via the Inspector click on either the "Load Default..." or "Load Custom..."
Expected results: A popup doesn't appear
Actual results: After the button press, a popup appears, informing you that you are trying to edit a locked file
Reproducible with: 1.16.6, 1.17.4-preview (2020.1.17f1, 2020.2.3f1, 2021.1.0b5, 2021.2.0a4)
Not reproducible with: 1.16.1 (2020.1.17f1, 2020.2.3f1, 2021.1.0b5, 2021.2.0a4)
Could not test with: 2018.4.31f1, 2019.4.20f1 (downgraded project has errors)
Note:
- The popup says "File Assets/AddressableAssetData/DefaultObject.asset is locked. Check out?"
- The issue seems to be related specifically to Perforce version control
Comments (1)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
phulcybrazos
Mar 05, 2021 15:45
I am also see the issue and have tracked it down to AddressableAssetUtility.cs:326
Looks like it is not checking to see if the asset is already checked out in source control before displaying the dialogue to ask to lock the file.