Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X
Votes
0
Found in
2018.4
2018.4.31f1
2019.4
Issue ID
1308013
Regression
No
UnityWebRequestAsyncOperation.progress is returned as an integer instead of a float value
Reproduction steps:
1. Open user's attached project and Scenes/SampleScene scene
2. Open the 1238418Python.py script in the attached project root folder
3. Enter the Play mode and observe the Console window
Expected result: Progress is printed as a float value
Actual result: Progress is printed as an integer value
Reproducible with: 2018.4.31f1, 2019.4.18f1, 2019.4.19f1
Not reproducible with: 2018.4.30f1, 2019.1.0a1, 2019.4.17f1, 2020.1.0a1, 2020.1.0a18, 2020.2.2f1, 2020.2.3f1, 2021.1.0b5, 2021.2.0a3
Could not test with: 2020.1.0a19, 2020.1.17f1, 2020.2.1f1 (Could not test because of Case 1238418 issue)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.2f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.22f1
Resolution Note (fix version 2018.4):
Fixed in: 2018.4.33f1