Search Issue Tracker
Fixed
Fixed in 2020.3.40f1, 2021.3.12f1, 2022.1.20f1, 2022.2.0b10, 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
- Editor crashes when debugging a for loop
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
Add comment