Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2018.2.0a5
2018.2.13f1
2018.3.0a1
Issue ID
1092852
Regression
Yes
"UNITYTLS_INTERNAL_ERROR" error when sending a message to Azure IoT Hub using the client SDK
"TlsException: Handshake failed - error code: UNITYTLS_INTERNAL_ERROR, verify result: UNITYTLS_X509VERIFY_FATAL_ERROR" when sending a message to Azure IoT Hub using the client SDK
Reproduction steps:
1. Open "New Unity Project.zip" project
2. Open "SampleScene" scene
3. Enter Playmode
4. Notice an error: "TlsException: Handshake failed - error code: UNITYTLS_INTERNAL_ERROR, verify result: UNITYTLS_X509VERIFY_FATAL_ERROR"
Expected Result: No errors appear
Actual Result: Error appears
Fixed in: 2019.2.0a4, 2019.1.0a1, 2018.3.0a4
Reproduced with: 2018.3.0a3, 2018.2.20f1, 2018.2.0f10, 2018.2.0f1, 2018.2.0b1, 2018.2.0a7
Did not reproduce on: 2019.2.0a1, 2019.1.0a14, 2018.3.3f1, 2018.3.0a4, 2017.4.18f1 (Can't compile due to broken .dll files), 2018.2.0a4, 2018.2.0a1, 2018.1.9f2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
- Shader Graph validation errors are not pointing to the right implementation
- Rich Text is not correctly highlighted when searching through Debug Logs in the Console window
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
Add comment