Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2017.4.X, 2018.1.X, 2018.2.X
Votes
0
Found in
2017.1.2f1
Issue ID
1020262
Regression
No
The assignment of the reference parameter is applied to the local copy of the variable under il2сpp
Steps to reproduce:
1. Open the attached project
2. Switch platform to Windows Store
3. Open the scene.unity scene
4. Build
5. Open VS solution
6. Deploy on a local machine
7. Observe the local variable is null
Actual results The assignment of the reference parameter is applied to the local copy of the variable
Expected: The assignment of the reference parameter should not be applied to the local copy of the variable
Reproduced with: 2017.1.3p2, 2017.2.2p3, 2017.4.1f1, 2018.1.0b13, 2018.2.0a8
Backported to: 2017.4.4f1, 2018.1.2f1, 2018.2.0b11
Comments (6)
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
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
SaintOtis
Apr 07, 2023 03:10
that's all the useful information I was looking for. thank you for sharing!