Search Issue Tracker
In Progress
Fix In Review for 6000.2.16f1, 6000.3.1f1
Fixed in 6000.0.64f1, 6000.4.0a6, 6000.5.0a2
Votes
2
Found in
6000.0.57f1
6000.1.16f1
6000.2.3f1
6000.3.0b1
6000.5.0a1
Issue ID
UUM-116426
Regression
No
[WebGL][Android] Corrupt header when connecting via IP
Steps to reproduce:
1. Open the “IN-112979” project
2. Build And Run
3. Host the build
4. Open the build on the device
5. In the browser, open another tab and search for anything, then open another tab and open the build
Expected result: Connected successfully
Actual result: “[21] The message header is corrupted and for security reasons connection will be terminated.” error is thrown
Reproducible with: 6000.0.57f1, 6000.1.16f1, 6000.2.3f1, 6000.3.0b1
Testing environment: macOS 15.6.1 (M4 Pro), Windows 11 (by user)
Not reproducible on: No other environment tested
Reproducible with these devices:
VLNQA00409 - Galaxy Z Fold3 5G (SM-F926B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
VLNQA00335 - Galaxy S20+ 5G (SM-G986B), CPU: Exynos 990, GPU: Mali-G77, OS: 10
Not reproducible with these devices:
VLNQA00334 - Xiaomi Mi A3 (Mi A3), CPU: Snapdragon 665 SM6125, GPU: Adreno 610, OS: 11
VLNQA00319 - Google Pixel 4 (Pixel 4), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 13
Note: Doesn’t reproduce on all devices
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Initialization Mode" and "Update Mode" drop-downs are not localized in the Custom Render Texture asset
- Switching Graphics Default or DevLook Profile to “NightSkyRenderingSettings Profile” throws “KeyNotFoundException” error in the Console window
- Section separator renders in the wrong place in Search Journaling and Archetypes windows
- [D3D12][UWP] Additional persistent shadows are drawn in UWP builds when using D3D12
- Search Journaling window link to Journal Manager documentation isn’t working
Add comment