It is possible to enter impossible Scope name in the Scope Registries of Package Manager Project settings

Unity: Packman

Won't Fix

6.5.X

6.4.X

6.3.X

6.0.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.

How to reproduce:
1. Create a new Unity project
2. Go to Edit -> Project Settings -> Package Manager -> Scoped Registries -> Scope(s)
3. Enter the Scope with the special symbols

Expected results: Warning or error is thrown about unsupported symbols and the Scope is being stripped
Actual results: No warnings and the scope is not stripped, so it doesn't automatically assign the matching scope packages to it

Reproducible with: 6000.0.65f1, 6000.3.3f1, 6000.4.0b3, 6000.5.0a3

Reproducible on: macOS Tahoe 26
Not reproducible on: No other environment tested

It is possible to enter impossible Scope name in the Scope Registries of Package Manager Project settings

Unity: Packman

Won't Fix

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

It is possible to enter impossible Scope name in the Scope Registries of Package Manager Project settings

Unity: Packman

Statuses

Won't Fix

Resolution Notes

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?