Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2021.3.15f1
2022.2.0f1
2023.1.0a21
Issue ID
UUM-20163
Regression
No
Generated C++ code fails to compile due to invalid il2cpp_codegen_cast_struct
How to reproduce:
- Open the attached project "PDA-AR.zip"
- Build the project for UWP
- Open the built project with Visual Studio
- Build
Expected results: Build is successful
Actual results:
Il2CppOutputProject\Source\il2cppOutput\GenericMethods11.cpp(21673): note: Siehe Verweis auf die gerade kompilierte Instanziierung "R il2cpp_codegen_cast_struct<ReadOnlySequence_1_t38998D05CBF65F5F510360A9312CCD3791C56F06,ReadOnlySequence_1_t85097489C00952FC58DF9F3ACE926EAE9A51898A>(S *)" der Funktions-Vorlage.
1> with
1> [
1> R=ReadOnlySequence_1_t38998D05CBF65F5F510360A9312CCD3791C56F06,
1> S=ReadOnlySequence_1_t85097489C00952FC58DF9F3ACE926EAE9A51898A
1> ]
1>
Reproducible with: 2021.3.15f1, 2022.1.23f1, 2022.2.0f1, 2023.1.0a21
Could not test with: 2020.3.42f1 (compilation errors in the Console window)
Reproducible on: Windows 10
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note:
The issue was caused by incompatible versions of System.Buffers.dll and System.Memory.dll found in the project. These DLLs are already part of .NET Standard 2.1 and come from Unity. Deleting these DLLs from the project resolves the issue.
Resolution Note (2023.1.X):
The issue was caused by incompatible versions of System.Buffers.dll and System.Memory.dll found in the project. These DLLs are already part of .NET Standard 2.1 and come from Unity. Deleting these DLLs from the project resolves the issue.