Search Issue Tracker
Fixed
Fixed in 2022.3.70f1, 6000.0.64f1, 6000.2.15f1, 6000.3.1f1, 6000.4.0a4
Votes
0
Found in
6000.0.47f1
6000.1.0f1
6000.2.0a9
6000.3.0a1
6000.4.0a1
Issue ID
UUM-103738
Regression
Yes
Package files do not get checked out in Perforce when the project includes a provider callback
How to reproduce:
1. Open the “IN-97138_repro“ project
2. Make sure that Perforce is set up and the project is connected to the workspace (Edit → Project Settings → Version Control)
3. In Perforce, make sure that the files in the Packages folder are submitted (select the Packages folder and press Submit)
4. In the Editor, select Window → Package Manager
5. Install a different version of the “2D SpriteShape“ package (10.1.0 or 10.0.6)
6. Refresh the Perforce workspace and observe the manifest.json and packages-lock.json files
Expected result: The files are checked out (red check marks are seen over the files)
Actual result: The files are not checked out (no red check marks are seen over the files)
Reproducible with: 2023.3.0b1, 6000.0.47f1, 6000.1.0f1, 6000.2.0a9
Not reproducible with: 2022.3.61f1, 2023.3.0a19
Reproducible on: Windows 10
Not reproducible in: No other environment tested
Notes:
- Issue does not reproduce if Assets/Editor/SpriteAtlasAssetCheckout.cs is removed
- Make sure to revert the files before reproducing the issue again
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Progress indicator in Meta Quest Build Profile configuration is barely visible
- Slightly transparent objects disappear completely in Web Player when using RenderGraph
- Visual Scripting Components are hidden behind a throbber when Multiplayer Play Mode is running with at least one local instance
- Video Player does not throw an error when playing a video with unsupported encoding settings
- Errors indicating that TMP Extras were not Imported logged when opening the Render Pipeline Converter Window while in Play Mode
Add comment