1

Here, or here for a complete version, you can find a sample GRPC "Hello World" project for Unity. Only the first version, that is built for Unity and wrapped in a DLL is working perfectly fine in Unity IDE and on Standalone build. The Raw Grpc.Core files are referencing everything correctly in IDE but they have Marshaling problem.

Unfortunately, it cannot get build for UWP with IL2CPP backend. Unity builds the project and creates a .sln project. But Visual Studio always gives LNK2001 for GRPC properties on the final compilation.

Here are first error codes:

LNK2001 unresolved external _grpccsharp_init@0
LNK2001 unresolved external _grpccsharp_shutdonw@0
LNK2001 unresolved external _grpccsharp_version_string@0
...

Ok, thanks to @Sunius, I digged into it a little bit more. There are some points, I am going to add to the question:

There are two methods regarding referencing extern methods in GRPC C# package. They are named static and shared libs.

internal class DllImportsFromStaticLib
{
    private const string ImportName = "__Internal";

    [DllImport(ImportName)]
    public static extern void grpcsharp_init();

    [DllImport(ImportName)]
    public static extern void grpcsharp_shutdown();

    ...
}

and

internal class DllImportsFromSharedLib
{
    private const string ImportName = "grpc_csharp_ext";

    [DllImport(ImportName)]
    public static extern void grpcsharp_init();

    [DllImport(ImportName)]
    public static extern void grpcsharp_shutdown();

    ...
}

I tried to test it with the shared one, I got another linking error file which is a little bit different.

LNK2001 unresolved external _dlopen@8
LNK2001 unresolved external _dlsym@8
...

In two separate methods, extern methods are getting connected to the internal interface:

public NativeMethods(DllImportsFromStaticLib unusedInstance) 
{
    this.grpccsharp_init = DllImportsFromStaticLib.grpccsharp_init; 
    this.grpccsharp_shutdown = DllImportsFromStaticLib.grpccsharp_shutdonw;
    ...
}

and

public NativeMethods(DllImportsFromSharedLib unusedInstance) 
{
    this.grpccsharp_init = DllImportsFromSharedLib.grpccsharp_init; 
    this.grpccsharp_shutdown = DllImportsFromSharedLib.grpccsharp_shutdonw;
    ...
}

And which method will get called is defined here:

private static NativMethods LoadNativeMethodsUnity()
{
    switch(PlatformApis.GetUnityRuntimePlatform())
    {
        case "IPhonePlayer":
            return new NativeMethods(new NativeMethods.DllImportsFromStaticLib());
        default:
            return new NativeMethods(new NativeMethods.DllImportsFromSharedLib());  
    }
}

Some updates:

Thanks to @jsmouret, there is Stub.c file in his Grpc Github with fake methods, so Linker does not complain about Grpc_init methods anymore.

Next Error: dlopen, dlsym, dlerror:

First, I tried to use the same, Stub technique, but it did not help in this case, or maybe I did it wrong.

Thanks to @Sunius, I commented out all of "__Internal" dll import codes. So I am not getting any dlopen, dlsym, and dlerror errors.

Next Error: It happens from inside application, not the visual studio debugger. It tells me: "exception: to marshal a managed method, please add an attribute named 'MonoPInvokeCallback' to the method definition."

exception: error loading the embedded resource "Grpc.Core.roots.pem"

and

exception: To marshal a managed method, please add an attribute named 'MonoPInvokeCallback' to the method definition.

After I googled it, I know my options, but the question it, for which method should I do that?!

Mohsenne
  • 356
  • 5
  • 17
  • Consider editing this question and your answer below to agument/replace the screenshots of error messages & code with their text instead. Text is easier to read, can be indexed, and is more accessible. – chwarr Dec 05 '18 at 11:34
  • @chwarr thanks for your comment. I will take care of that. – Mohsenne Dec 05 '18 at 16:40

2 Answers2

3

Thanks to my colleague Alice, @Sunius and @jsmouret, at the end, grpc works on UWP on Unity Platform through this steps:

  1. Download Grpc.Core folder from Google Grpc Github.
  2. Download Grpc Unity plugin from their official site.
  3. Copy the runtime folder to your Grpc.Core folder. Please remove Grpc.Core.dll that you get from Grpc Unity Plugin, since we are using their source code.
  4. Grpc should be in a folder called, Plugins in Unity, otherwise it will not be recognized.
  5. Include this file in your runtime folder.
  6. Include the Stub also from the Unity Plugin Inspector for WSA.
  7. Find runtime .dll for Windows and include them in WSA from Unity Plugin Inspector.

By now, you should be getting _dlopen error.

  1. Search through your Unity Solution with an IDE for "__Internal". There are not so many places, but comment them out. Also some methods that are depended on "__Internal"s, like dlopen and dlsym.

By now, you are not getting anymore build error but you need to make Grpc work.

  1. Search for something like "DefaultSslRootsOverride" and comment out like below:

    internal static class DefaultSslRootsOverride
    {
        const string RootsPemResourceName = "Grpc.Core.roots.pem";
        static object staticLock = new object();
    
        /// <summary>
        /// Overrides C core's default roots with roots.pem loaded as embedded resource.
        /// </summary>
        public static void Override(NativeMethods native)
        {
            lock (staticLock)
            {
                //var stream = typeof(DefaultSslRootsOverride).GetTypeInfo().Assembly.GetManifestResourceStream(RootsPemResourceName);
                //if (stream == null)
                //{
                //    throw new IOException(string.Format("Error loading the embedded resource \"{0}\"", RootsPemResourceName));   
                //}
                //using (var streamReader = new StreamReader(stream))
                //{
                //    var pemRootCerts = streamReader.ReadToEnd();
                //    native.grpcsharp_override_default_ssl_roots(pemRootCerts);
                //}
            }
        }
    }
    
  2. Search for something like "static void HandWrite" and add an attribute like something in below:

    [MonoPInvokeCallback(typeof(GprLogDelegate))]
    private static void HandleWrite(IntPtr fileStringPtr, int line, ulong threadId, IntPtr severityStringPtr, IntPtr msgPtr)
    {
        try
        {
            var logger = GrpcEnvironment.Logger;
            string severityString = Marshal.PtrToStringAnsi(severityStringPtr);
            string message = string.Format("{0} {1}:{2}: {3}",
                threadId,
                Marshal.PtrToStringAnsi(fileStringPtr), 
                line, 
                Marshal.PtrToStringAnsi(msgPtr));
    
            switch (severityString)
            {
                case "D":
                    logger.Debug(message);
                    break;
                case "I":
                    logger.Info(message);
                    break;
                case "E":
                    logger.Error(message);
                    break;
                default:
                    // severity not recognized, default to error.
                    logger.Error(message);
                    break;
            }
        }
        catch (Exception e)
        {
            Console.WriteLine("Caught exception in native callback " + e);
        }
    }
    

I guess, you are done. In case, it did not work for your UWP, let me know, maybe I can help. :)

Mohsenne
  • 356
  • 5
  • 17
1

It looks like your plugin uses "__Internal" P/Invoke to call those native functions:

https://github.com/grpc/grpc/blob/befc7220cadb963755de86763a04ab6f9dc14200/src/csharp/Grpc.Core/Internal/NativeMethods.Generated.cs#L542

However, the linker cannot locate those functions and thus fails. You should change that code to either specify the DLL file name where the functions are implemented, or drop the source files with definitions for those functions into your Unity project. Or, if that code path isn't actually invoked (since you said it works on the standalone player), #ifdef it out from UWP build.

You can find more information about "__Internal" P/Invoke here:

https://docs.unity3d.com/Manual/windowsstore-plugins-il2cpp.html

Sunius
  • 2,789
  • 18
  • 30
  • 1. Specifying the DLL instead of "__Internal" is not easy as it sounds: There is no DLL from GRPC team that I could add to Unity project and reference it. – Mohsenne Nov 28 '18 at 11:05
  • 2. It would be nice, if you could give me a link to GRPC source files so I can drop it to Unity and make a reference for those extern methods manually. Unfortunately, I could not find anything like native method definitions on their GitHub page. – Mohsenne Nov 28 '18 at 11:08
  • 3. The Path is invoked and "__Internal" works as expected in Standalone build. The problem is this C++ Machine Conversion in IL2CPP that cannot hold GRPC Core in its references at the moment of code compilation. – Mohsenne Nov 28 '18 at 11:12
  • I bet that "__Internal" code does not in fact work on Standalone player, otherwise it would work on UWP too. I suggest stepping through that code on Standalone player and seeing how it actually invokes those methods. – Sunius Nov 28 '18 at 20:45
  • I will dig into that, a little bit more and get back to you. Thanks again. – Mohsenne Nov 29 '18 at 08:27
  • Ok, you were right. "__Internal" was not getting called on Standalone build. I found somebody who could get a build for UWP. [ToHisGitHub](https://github.com/jsmouret/grpc-unity-package/issues/6). – Mohsenne Nov 29 '18 at 23:45
  • Unfortunately, still I have problems including his pseudo methods to the project so linker can be "at ease". As I mentioned in his Github, I tried many methods, but I could not get any good results. – Mohsenne Nov 29 '18 at 23:48
  • But as I marked the provided Win .dll inclusion in Unity, the .dll could be recognized. Since then I got only _dlOpen errors. – Mohsenne Nov 30 '18 at 00:06
  • Looks like there is C# code which uses DllImport("__Internal") to call into dlopen and friends. Those functions are only available on POSIX platforms, so not UWP. You need to #ifdef them in C# code. – Sunius Nov 30 '18 at 17:50
  • You are right. I found two more "__Internal" dll import. I commented all of them out. But now, I am getting, "exception: to marshal a managed method, please add an attribute named 'MonoPInvokeCallBack' to the method definition". Unfortunately, I do not know where does it exactly coming from. – Mohsenne Dec 03 '18 at 08:12
  • I assume, the guy who wrapped Grpc.Core into one DLL used somewhere MonoPInvokeCallBack, that is why it works with DLL. But in my raw Grpc.Core from Google, I need to do it somewhere myself. Where! Idk! – Mohsenne Dec 03 '18 at 11:06