Unity Issue Tracker - MissingMethodException in Player.log when calling Type.GUID in IL2CPP Build

Fixed in 2022.2.X

Fixed in 2021.2.X, 2022.1.X

Votes

2

Found in

2021.2

2021.2.0a18

2021.2.7f1

2022.1

2022.2

Issue ID

1397603

Regression

Yes

MissingMethodException in Player.log when calling Type.GUID in IL2CPP Build

IL2CPP

Jan 24, 2022

Reproduction steps:
1. Open the user's attached project ("GuidTest.zip")
2. Build and Run the project
3. Open Player.log

Expected result: No MissingMethodException in the Player.log
Actual result: Exception in the Player.log:
MissingMethodException: System.RuntimeType::GetGUID(System.Type,System.Byte[])
at System.RuntimeType.get_GUID () [0x00000] in <00000000000000000000000000000000>:0
at DefaultNamespace.GuidTestBehaviour.Awake () [0x00000] in <00000000000000000000000000000000>:0

Reproducible with: 2021.2.0a18, 2021.2.9f1, 2022.1.0b5, 2022.2.0a3
Not reproducible with: 2019.4.36f1, 2020.3.27f1, 2021.2.0a17

Resolution Note (fix version 2022.2):

Fixed in: 2022.2.0a5
Resolution Note (fix version 2022.1):

Fixed in: 2022.1.0b10
Resolution Note (fix version 2021.2):

Fixed in: 2021.2.14f1

Comments (3)

allseeingeye

Apr 06, 2022 20:37

This issue is still not resolved for us, preventing us from using external hardware with the Quest 2 due to the SDK relying on reflection with IL2CPP / 64-bit, both of which we need for performance and distribution via AppLab.
SimonDarksideJ

Mar 13, 2022 20:04

THIS ISSUE IS NOT FIXED.

The bug/exception may be handled but IT DOES NOT WORK in 2021. I have projects that run perfectly fine in 2020 using reflection, that CEASE to function in 2021 using IL2CPP (Mono seems ok)
Din0m1te

Feb 21, 2022 08:34

How can this only have two votes? This issue makes it impossible to release any updates to production channels on Oculus/Meta as IL2CPP is the only way to generate 64bit ARM builds. This issue is a huge blocker for anyone building with the IL2CPP scripting backend.

Search Issue Tracker

2