Search Issue Tracker
Fixed in 2020.3.40f1
Fixed in 2020.3.X, 2021.3.X, 2022.1.X, 2022.2.X, 2023.1.X, 2023.1.0a13
Votes
7
Found in
2020.3.39f1
2021.3.10f1
2022.1.17f1
2022.2.0b8
2023.1.0a11
Issue ID
UUM-14671
Regression
Yes
PlayerPrefs.GetFloat returns wrong values when used in UWP Build
How to reproduce:
1. Open the attached project "TestFloat3.rar"
2. Build the project
3. Open "UWPPlayerLauncher.exe" in the Build folder
4. Exit the Player
5. Repeat steps 3-4
Expected results: PlayerPrefs.GetFloat returns previously set float
Actual results: PlayerPrefs.GetFloat returns the wrong value
Reproducible with: 2020.3.40f1, 2021.3.10f1, 2022.1.17f1, 2022.2.0b8, 2023.1.0a11
Reproducible on: Windows 10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Add comment