Search Issue Tracker
Third Party Issue
Unknown (hidden) 2019.4.X, 2020.3.X, 2021.3.X, 2022.3.X, 2023.1.X
Votes
0
Found in
2019.4.0f2
2021.3.7f1
2023.1.0a1
Issue ID
UUM-2443
Regression
No
SSL/TLS is not working when using a third party DotNetty.dll
Reproduction steps:
1. Open the attached project
2. Open the SampleScene under Assets/Scenes in the Project window
3. Enter Play Mode
4. Observe Console output
Expected result: the Console output should output AggregatedFullHttpResponse
Actual result: the AggregatedFullHttpResponse is not logged in the Console
Reproducible with: 2019.4.39f1, 2020.3.35f1, 2021.3.4f1, 2022.1.3f1, 2022.2.0a15
Reproducible on: Windows 10 (21H2)
Notes: the scripts are using a third party DotNetty.dll and if they are compiled and played in a normal DotNet Console Application, they produce the output as expected
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
The DotNetty library appears to have several async tasks that are not returning leading to the described issue.