Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.2.6f1
2020.3
2021.1
2021.2
Issue ID
1317668
Regression
No
IL2CPP does not correctly distinguish between types with equal names from different assemblies
How to reproduce:
1. Open the project (link in the edit)
2. Build to UWP
3. Open built the solution in Visual Studio
4. Start Debugging on Release x64
5. Observe compiler errors
Expected result: Build is launched successfully
Actual result: Build launch fails with "C2440 'initializing': cannot convert from 'Vector3_t3CFF64FAF0923FE4B51D84DE2E2DC139F1B53152' to 'Vector3_tA1B8517EED04F753987922C4361B51A4F3AE8C65' Il2CppOutputProject E:\Files\TestIL2CPPNameConflict\TestIL2CPPNameConflict\New folder\Il2CppOutputProject\Source\il2cppOutput\Microsoft.MixedReality.Toolkit.Providers.WindowsMixedReality.cpp 15055" error
Reproducible with: 2019.4.25f1, 2020.3.5f1, 2021.1.4f1, 2021.2.0a14
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment