Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2021.3.11f1
2022.1.19f1
2022.2.0b10
2023.1.0a13
Issue ID
UUM-15813
Regression
No
Build fails with errors "unresolved external symbol grpcsharp_init referenced in function" when gRCP plugins are included
How to reproduce:
1. Open the attached project “PDA-AR.zip”
2. Build the project for UWP
3. Open the generated Solution in VS
4. Build the Solution
Expected results: Build is successful
Actual results: Build fails with errors “unresolved external symbol grpcsharp_init referenced in function DllImportsFromStaticLib_grpcsharp_init_m2426CCF4CA2929DD8B718C5DF15B10DD30B8030C”
Reproducible with: 2021.3.11f1, 2022.1.19f1, 2022.2.0b10, 2023.1.0a13
Could not test with: 2020.3.40f1 (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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Resolution Note:
This is not a bug in Unity. When you use "[DllImport("__Internal")]" in your C# code, it is your responsibility to make sure that the native linker finds the function implementation. If the function is missing from the project, it will result in compilation errors.
Resolution Note (2023.1.X):
This is not a bug in Unity. When you use "[DllImport("__Internal")]" in your C# code, it is your responsibility to make sure that the native linker finds the function implementation. If the function is missing from the project, it will result in compilation errors.