Search Issue Tracker
Third Party Issue
Third Party Issue in 2023.3.X
Votes
0
Found in
2021.3.30f1
2022.3.9f1
2023.1.13f1
2023.2.0b9
2023.3.0a5
Issue ID
UUM-49003
Regression
No
[IL2CPP] Error "no matching function for call to" when building a project with an enum that is converted to struct
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Click the Build button in File > Build Settings window
Expected result: Build succeeds
Actual result: Build fails with error “no matching function for call to 'CachePermissions_set_Role_mA21789CE06ADB42CFC944AA1C01ECB4D469C3C8E'“
Reproducible with: 2021.3.30f1, 2022.3.9f1, 2023.1.13f1, 2023.2.0b9, 2023.3.0a5
Reproducible on: Windows 10 Enterprise 21H2 (Windows Standalone - IL2CPP, Android Platform - IL2CPP)
Not reproducible on: Windows 10 Enterprise 21H2 (Windows Standalone - Mono, Android Platform - Mono)
Note:
- The user has a plugin that is using protobuf. This plugin generates some classes and enums that are used in their SDK. When doing an assignment on an object and trying to Build the project with the Android platform, the above error appears in the Console window
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
- MissingReferenceException errors are thrown after entering Play mode when multiple Inspector windows are displaying different objects with Grid Layout Group component
- "Can't change name, category with the same name already exists" Error is logged when renaming a Category to a name with a trailing space in the VFX Graph Blackboard
- Delete does nothing on an in-use Custom Attribute when re-triggered after cancelling the deletion confirmation prompt in the VFX Graph Blackboard
- No Ellipses are used for the Visual Effect Graph Create Context Menu Option
- Crash on LaunchBugReporter when opening a specific project using DirectX 12
Resolution Note:
It seems the issue was due to one of the dependent dlls for the user's SDK dll. After updating that dependency to the latest version it fixed their issue.
Resolution Note (2023.3.X):
It seems the issue was due to one of the dependent dlls for the user's SDK dll. After updating that dependency to the latest version it fixed their issue.