Search Issue Tracker
Fixed in 2023.1.X
Fixed in 2020.3.X, 2021.3.X, 2022.1.X, 2022.2.X
Votes
0
Found in
2019.4
2020.3
2021.1
2021.2
2021.2.0b5
2022.1
Issue ID
1354652
Regression
No
'displayName' in package.json is ignored if the package is from GitHub
How to reproduce:
1. Create a GitHub account and go into github.com/settings/tokens
2. Press "Generate new token" and scroll down to the third row of the table
3. Check the "read:packages" setting ON
4. Scroll down and generate token
5. Place the attached "upmconfig.toml" file into the "Users/<username>" directory and rename it to ".upmconfig.toml"
6. Open the user attached project "PackageManagerDisplayNameReport.zip"
7. Open the Packages folder
Expected result: Packages use “displayName: Prefab Package Example ” from “package.json”
Actual result: Packages use “name: com.tsgcpp.unitygithubpackageexample.prefab” instead of “displayName: Prefab Package Example” from “package.json"
Reproducible: 2019.4.30f1, 2020.3.18f1, 2021.1.21f1, 2021.2.0b12, 2022.1.0a8
Note:
* The access token currently in the file ".upmconfig.toml" expires on 10/06, replace it with the token you generated if expired/doesn't work
* When renaming "upmconfig.toml" you might be warned that the file will be hidden, you can still open it with VScode if you go into the directory it's in
* For step 5 refer to the documentation: https://docs.unity3d.com/Manual/upm-config.html
* For result examples, please refer to the screenshots attached
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note (fix version 2023.1):
Fixed in: 2023.1.0a2
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0b1
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.9f1
Resolution Note (fix version 2021.3):
Fixed in: 2021.3.7f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.37f1