Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.3.X, 2021.1.X
Votes
7
Found in
2020.1.0a8
2020.1.17f1
2020.2
2021.1
2021.2
Issue ID
1313205
Regression
Yes
Setting HttpClient.Timeout to a value greater than the default value of 100 seconds has no effect
Reproduction steps:
1. Open user's project "Timeout.zip"
2. Open "SampleScene" Scene
3. Enter Play mode
4. Wait for 3 minutes
Expected result: Console logs out "Status: OK" after 3 minutes
Actual result: Console logs out error: "Error after 40: System.Net.Http.HttpRequestException: An error occurred while sending the request ---> System.Net.WebException: The operation has timed out." after 100 seconds (full error in edits)
Reproducible with: 2020.1.0a8, 2020.2.6f1, 2021.1.0b9, 2021.2.0a7
Not reproducible with: 2018.4.32f1, 2019.4.21f1, 2020.1.0a7
Note: Setting HttpClient.Timeout to a lower value than 100 seconds has an effect, but setting it over 100 seconds doesn't
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a11
Resolution Note (fix version 2021.1):
Fixed in 2021.1.9f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.12f1