Search Issue Tracker
Fixed
Fixed in 2020.3.48f1, 2021.3.23f1, 2022.2.14f1, 2023.1.0b12, 2023.2.0a10
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
-
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
- Standard Unity Materials and Shaders become corrupted after importing specific Asset Packages
- [Linux][OpenGL][Vulkan] Draw calls are not shown in the Event List when taking a capture of a frame with RenderDoc
- Inaccurate collision detections when Rigidbody Collision Detection is set to "Continuous" or "Continuous Dynamic"
- Crash on Object::IncrementPersistentDirtyIndex when upgrading project version
- [iOS] Multiple Xcode project instances created before opens up when performing Build and Run for iOS Platform
Resolution Note (fix version 2023.2.0a10):
Fixed in: 2023.2.0a10
Resolution Note (fix version 2023.1.0b12):
Fixed in: 2023.1.0b12