Search Issue Tracker
Fixed in 2020.3.48f1
Fixed in 2020.3.X, 2021.3.X, 2022.2.X, 2023.1.X, 2023.1.0b12, 2023.2.X
Votes
4
Found in
2020.3.40f1
2021.3.13f1
2022.1.22f1
2022.2.0b14
2023.1.0a17
Issue ID
UUM-19658
Regression
No
The error "invalid. Expected a 'SemVer' compatible value" is thrown when adding a Dependency in the Inspector with letters in the version name
Steps to reproduce:
1. Open the “IN-17628” project
2. Select the package.json at “Studious Backup Package” package
3. Click + in the Inspector at the Dependencies and add name: com.unity.sharp-zip-lib, version: 1.3.2-preview
4. Click Apply
Expected result: The dependency was added successfully
Actual result: An error “invalid. Expected a 'SemVer' compatible value” occurs
Reproducible with: 2020.3.40f1, 2021.3.13f1, 2022.1.22f1, 2022.2.0b14, 2023.1.0a17
Reproduced on: macOS Monterey 12.5.1 (Intel)
Workaround: Try to add for a second time
Comments (2)
-
Dewald_Bodenstein
Feb 07, 2024 16:15
I'm experiencing this with 2023.2.3f1
-
NilsAtLinx
Mar 17, 2023 10:13
using the git url approach as shown in these docs also throw the same error: https://docs.unity3d.com/Manual/upm-git.html#revision
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
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Resolution Note (fix version 2023.2):
Fixed in: 2023.2.0a10
Resolution Note (fix version 2023.1):
Fixed in: 2023.1.0b12