Search Issue Tracker
Fixed in Unity 2018.3
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [iOS][Editor]Legacy Launch Images iPhone 6.5 Landscape resolution mislabelled in Player Settings/Splash Image
- Memory leaks and Editor crashes/freezes when using decimal values in Gizmos
- Crash on PhysicsScene::ProcessTriggerEnterExits when splitting meshes that also exit a Trigger with OnTriggerExit
- "The page you were looking for doesn't exist" message appears when trying to Sign in using Unity Hub/Editor
- [Regression] Enviroment lighting is broken in the 2017.4.27f1 version
Add comment