Search Issue Tracker
Fixed
Fixed in 6000.6.0a1
Won't Fix in 6000.4.X, 6000.5.X
Votes
0
Found in
6000.3.3f1
6000.4.0b4
6000.5.0a4
6000.6.0a1
Issue ID
UUM-131807
Regression
No
Script with Errors is created in Example Package Sample when creating a Package with default fields
Steps to reproduce:
- Open any Project and download the attached Unity Package
- Open the Package Manager and click the "+" button in the top left corner of the Window
- Select "Install Package from tarball..." and select the downloaded Unity Package
- In the Package Manager select this Package and open the Samples tab, then download and import it into the Project
- Observe the Console
OR
- Create a Package from the Package Manager with a default Manifest
- Export it
- Add it to the Package Manager
- Download and import the example Sample
Actual results: Error "Assets\Samples\test3\0.1.0\Example Sample\SampleExample.cs(25,13): error CS0103: The name 'Debug' does not exist in the current context" is logged in the Console
Expected results: When creating a custom Package with default fields the example Package's Sample is created without any errors
Reproducible with versions: 6000.3.3f1, 6000.4.0b4, 6000.5.0a4
Can’t test with versions: 6000.0.64f1, 6000.2.15f1 (No Package creation from PM)
Tested on (OS): Windows 11, macOS 15
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.6.0a1
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.4.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.