Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X
Votes
0
Found in
2021.3.40f1
2022.3.37f1
6000.0.10f1
Issue ID
UUM-76466
Regression
No
Autoconnect Profiler does not connect to the WebGL Player when the Unity Editor is re-opened
Reproduction steps:
1. Open the attached “WebGLProfilerConnect.zip” project
2. In the Build Settings, make sure the WebGL platform is selected
3. Enable “Development build” and “Autoconnect Profiler”
4. Press “Build” and wait for the Player to build
5. Close and re-open the project
6. Open Unity Profiler
7. Host the WebGL Player (If you have Python you can navigate to the build's folder using a command window and run the “py -m http.server” command)
8. Open a browser and connect to the Player via this link: [http://localhost:8000|http://localhost:8000/]/
9. Observe the Profiler window inside Unity
Expected result: The Profiler automatically connects to the WebGL Player
Actual result: The Profiler does not connect to the WebGL Player
Reproducible with: 2021.3.40f1, 2022.3.37f1, 6000.0.10f1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note: Profiler always automatically connects to the Windows Player if “Autoconnect Profiler” is enabled
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Select Preset "None" icon changes after switching tabs
- [Android] Crash when using xxHash3 and targeting the ARMv7 Architecture with IL2CPP Scripting Backend
- GameObject reference in a Script Component becomes missing when unpacking a variant of another Prefab variant
- Project Settings vertical separator position is not synchronized with the mouse position when dragging it horizontally
- Crash on PhysicsDebugDraw::SelectFiltering::Update when entering play mode with Physics Debug window docked and unfocused
Add comment