Search Issue Tracker
Fixed in 1.0.1
Votes
0
Found in [Package]
0.1.0-preview.8, 1.0.0
Issue ID
1198485
Regression
Yes
Settings Manager package Sample throws errors when it is imported
Reproduction steps:
1. Open user's attached project "Settings_Manager_package_Sample"
2. Open the Package Manager and select the Settings Manager package
3. Import User Settings Example by clicking the "Import into Project" button
Expected result: Sample is imported without any errors
Actual result: "The type or namespace name 'ProjectSettingsRepository' could not be found" errors are thrown
Reproducible with: 2019.3.0b11, 2020.1.0a13
Could not test with: 2017.4.35f1 (no Package Manager), 2018.4.13f1, 2019.2.13f1, 2019.3.0a7 (no Settings Manager package)
Reproducible with package versions: 0.1.0-preview.8, 1.0.0
Not reproducible with package versions: 0.1.0-preview.4
Workaround: Changing "ProjectSettingsRepository" to "PackageSettingsRepository" in the lines that cause these errors
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment