Copyright © 2026 Unity Technologies
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.
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.
Steps to reproduce:
OR
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
Issues you vote on will appear here