Search Issue Tracker
Fixed in 2021.3.29f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.2.0a22
Votes
0
Found in
2021.3.24f1
2022.2.16f1
2023.1.0b12
2023.2.0a13
Issue ID
UUM-35575
Regression
Yes
“PlayerPrefsException: Could not store preference value“ when root project entry does not exist
Reproduction steps:
1. Open the attached project
2. Delete the project folder in the Registry Editor
3. Enter the Playmode
4. Observe the Console
Expected result: PlayerPrefs “Amount“ is displayed in the console
Actual result: “PlayerPrefsException: Could not store preference value“ error is thrown
Reproducible with: 2021.2.0a1, 2021.3.24f1, 2022.2.16f1, 2023.1.0b12, 2023.2.0a13
Not reproducible with: 2020.3.48f1, 2021.1.28f1
Reproducible on: Windows 10
Comments (1)
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
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
josenunes
Dec 15, 2023 15:51
how to fix?