Search Issue Tracker
By Design
By Design in 2022.2.X
Votes
0
Found in
2019.4.39f1
2020.3.35f1
2021.3.4f1
2022.1.4f1
2022.2.0a16
Issue ID
UUM-7861
Regression
No
[WebGL] ExposedReference<Transform>.Resolve() is not generated correctly in WebGL
Reproduction steps:
1. Open the user’s attached project
2. Open the TestScene.unity located in \\Assets\\Scenes folder in the Project window
3. Comment out lines 64-69 in TestScript.cs Script located in \\Assets\\Scripts folder in the Project window
4. Enter Play Mode
5. Observe the text after clicking the “Test” button in the Game View
6. Exit Play Mode
7. Switch Platform to WebGL and then Build And Run the project (File > Build Settings > WebGL)
8. Observe the text after clicking the “Test” button in the WebGL Player
Expected result: “result Transform TestContainer (UnityEngine.Transform)” should be outputted
Actual result: “result Boolean False” gets outputted
Reproducible with: 2019.4.39f1, 2020.3.35f1, 2021.3.4f1, 2022.1.4f1, 2022.2.0a16
Reproducible on: Windows 10 (21H2)
Note: if the lines 64-69 in TestScript.cs Script located in \\Assets\\Scripts folder in the Project window are not commented, the issue is not present
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
- 2D Freeform Light shadows disappear when light center is offset from shape bounds
- Crash on MarkAllDependencies when opening scenes with Assets from the YarnSpinner package
- Crash on CollectAllSceneManagerAndObjectIDs when opening a specific Scene
- GPU device suspended error when replaying a video in the Video Player with NVIDIA Vertical Sync set to Fast
- GPU device suspended error when replaying a video in the Video Player with NVIDIA Vertical Sync set to Fast
Resolution Note:
The problem here is a weakness in the attached project that is exposed when managed code stripping is enabled. Unity is behaving as expected.
Resolution Note (2022.2.X):
The problem here is a weakness in the attached project that is exposed when managed code stripping is enabled. Unity is behaving as expected.