MvvmCross Xamarin Android 与 SerilogLogProvider 的链接问题
MvvmCross Xamarin Android Linking Issue with SerilogLogProvider
运行 Xamarin 中的 MvvmCross 再次出现链接器问题 Android。最近升级到 MvvmCross 6.1.2 并开始使用 Serilog。当使用“Sdk and User Assemblies”在发布模式下编译时,我在 Android 设置期间从 base.CreateLogProvider() 得到以下错误:
CreateLogProvider() 代码:
public override MvxLogProviderType GetDefaultLogProviderType()
=> MvxLogProviderType.Serilog;
protected override IMvxLogProvider CreateLogProvider()
{
Serilog.Log.Logger = new LoggerConfiguration()
.MinimumLevel.Error()
.WriteTo.AndroidLog()
.CreateLogger();
return base.CreateLogProvider();
}
异常:
System.Exception: HandleAndroidException ---> System.ArgumentNullException: Value cannot be null.
Parameter name: method
at System.Linq.Expressions.Expression.Call(System.Linq.Expressions.Expression instance, System.Reflection.MethodInfo method, System.Linq.Expressions.Expression arg0, System.Linq.Expressions.Expression arg1, System.Linq.Expressions.Expression arg2)[0x0009d] in <c674d6912966428cb26998a802347469>:0
at System.Linq.Expressions.Expression.Call(System.Linq.Expressions.Expression instance, System.Reflection.MethodInfo method, System.Collections.Generic.IEnumerable`1[T] arguments) [0x00074] in <c674d6912966428cb26998a802347469>:0
at System.Linq.Expressions.Expression.Call(System.Linq.Expressions.Expression instance, System.Reflection.MethodInfo method, System.Linq.Expressions.Expression[] arguments) [0x00000] in <c674d6912966428cb26998a802347469>:0
at MvvmCross.Logging.LogProviders.SerilogLogProvider.GetForContextMethodCall() [0x00086] in <df54a54dac96467098c3a9eece96a79b>:0
at MvvmCross.Logging.LogProviders.SerilogLogProvider..ctor() [0x00018] in <df54a54dac96467098c3a9eece96a79b>:0
at MvvmCross.Core.MvxSetup.CreateLogProvider() [0x00045] in <df54a54dac96467098c3a9eece96a79b>:0
at myRouteTracker.Droid.Setup.CreateLogProvider() [0x0002a] in <bdd41c7f90344b17a5e6bc21c3959feb>:0
at MvvmCross.Core.MvxSetup.InitializeLoggingServices() [0x00000] in <df54a54dac96467098c3a9eece96a79b>:0
at MvvmCross.Core.MvxSetup.InitializePrimary() [0x00016] in <df54a54dac96467098c3a9eece96a79b>:0
at MvvmCross.Core.MvxSetupSingleton.StartSetupInitialization() [0x0000a] in <df54a54dac96467098c3a9eece96a79b>:0
at MvvmCross.Core.MvxSetupSingleton.InitializeAndMonitor(MvvmCross.Core.IMvxSetupMonitor setupMonitor) [0x00042] in <df54a54dac96467098c3a9eece96a79b>:0
at MvvmCross.Droid.Support.V7.AppCompat.MvxSplashScreenAppCompatActivity.OnCreate(Android.OS.Bundle bundle) [0x00019] in <2d476ccd46884988a021d78ffc7a2843>:0
at Android.App.Activity.n_OnCreate_Landroid_os_Bundle_(System.IntPtr jnienv, System.IntPtr native__this, System.IntPtr native_savedInstanceState) [0x0000f] in <1b4c73c9a2864ea8b5827f31fda08c32>:0
at(wrapper dynamic-method) System.Object.e043741f-fba6-4072-a6c2-cfc97949a294(intptr, intptr, intptr)
--- End of inner exception stack trace ---
对于其他链接问题,我通常会尝试访问 LinkerPleaseInclude 中被剥离的函数。即 MvvmCross.Logging.LogProviders.SerilogLogProvider.GetForContextMethodCall() 在这种情况下。但是,SerilogLogProvider 是我无法访问的内部 class。
我尝试的最后一件事是将 Serilog 和 MvvmCross.Logging.LogProviders 添加到“跳过链接程序集”。也不行。
非常感谢您的提前帮助。
此致,
尼克
问题是 SerilogLogProvider
对 Serilog.dll
(See GitHub SerilogLogProvider
source) 使用反射。即使您可以访问 SerilogLogProvider
class,它也无助于防止链接器剥离所需的方法。原因是链接器实际上正在从 Serilog.dll
中剥离您需要的方法。
您可以将以下包含添加到您的 LinkerPleaseInclude.cs
以防止链接器删除 SerilogLogProvider
使用的方法。
public void Include(Serilog.ILogger logger)
{
Serilog.Events.LogEventLevel logEventLevel = Serilog.Events.LogEventLevel.Debug;
_ = Serilog.Log.ForContext("", "", false);
_ = Serilog.Context.LogContext.PushProperty("", "", false);
_ = !logger.IsEnabled(logEventLevel);
logger.Write(logEventLevel, "", new object[0]);
logger.Write(logEventLevel, new Exception(), "", new object[0]);
}
运行 Xamarin 中的 MvvmCross 再次出现链接器问题 Android。最近升级到 MvvmCross 6.1.2 并开始使用 Serilog。当使用“Sdk and User Assemblies”在发布模式下编译时,我在 Android 设置期间从 base.CreateLogProvider() 得到以下错误:
CreateLogProvider() 代码:
public override MvxLogProviderType GetDefaultLogProviderType()
=> MvxLogProviderType.Serilog;
protected override IMvxLogProvider CreateLogProvider()
{
Serilog.Log.Logger = new LoggerConfiguration()
.MinimumLevel.Error()
.WriteTo.AndroidLog()
.CreateLogger();
return base.CreateLogProvider();
}
异常:
System.Exception: HandleAndroidException ---> System.ArgumentNullException: Value cannot be null.
Parameter name: method
at System.Linq.Expressions.Expression.Call(System.Linq.Expressions.Expression instance, System.Reflection.MethodInfo method, System.Linq.Expressions.Expression arg0, System.Linq.Expressions.Expression arg1, System.Linq.Expressions.Expression arg2)[0x0009d] in <c674d6912966428cb26998a802347469>:0
at System.Linq.Expressions.Expression.Call(System.Linq.Expressions.Expression instance, System.Reflection.MethodInfo method, System.Collections.Generic.IEnumerable`1[T] arguments) [0x00074] in <c674d6912966428cb26998a802347469>:0
at System.Linq.Expressions.Expression.Call(System.Linq.Expressions.Expression instance, System.Reflection.MethodInfo method, System.Linq.Expressions.Expression[] arguments) [0x00000] in <c674d6912966428cb26998a802347469>:0
at MvvmCross.Logging.LogProviders.SerilogLogProvider.GetForContextMethodCall() [0x00086] in <df54a54dac96467098c3a9eece96a79b>:0
at MvvmCross.Logging.LogProviders.SerilogLogProvider..ctor() [0x00018] in <df54a54dac96467098c3a9eece96a79b>:0
at MvvmCross.Core.MvxSetup.CreateLogProvider() [0x00045] in <df54a54dac96467098c3a9eece96a79b>:0
at myRouteTracker.Droid.Setup.CreateLogProvider() [0x0002a] in <bdd41c7f90344b17a5e6bc21c3959feb>:0
at MvvmCross.Core.MvxSetup.InitializeLoggingServices() [0x00000] in <df54a54dac96467098c3a9eece96a79b>:0
at MvvmCross.Core.MvxSetup.InitializePrimary() [0x00016] in <df54a54dac96467098c3a9eece96a79b>:0
at MvvmCross.Core.MvxSetupSingleton.StartSetupInitialization() [0x0000a] in <df54a54dac96467098c3a9eece96a79b>:0
at MvvmCross.Core.MvxSetupSingleton.InitializeAndMonitor(MvvmCross.Core.IMvxSetupMonitor setupMonitor) [0x00042] in <df54a54dac96467098c3a9eece96a79b>:0
at MvvmCross.Droid.Support.V7.AppCompat.MvxSplashScreenAppCompatActivity.OnCreate(Android.OS.Bundle bundle) [0x00019] in <2d476ccd46884988a021d78ffc7a2843>:0
at Android.App.Activity.n_OnCreate_Landroid_os_Bundle_(System.IntPtr jnienv, System.IntPtr native__this, System.IntPtr native_savedInstanceState) [0x0000f] in <1b4c73c9a2864ea8b5827f31fda08c32>:0
at(wrapper dynamic-method) System.Object.e043741f-fba6-4072-a6c2-cfc97949a294(intptr, intptr, intptr)
--- End of inner exception stack trace ---
对于其他链接问题,我通常会尝试访问 LinkerPleaseInclude 中被剥离的函数。即 MvvmCross.Logging.LogProviders.SerilogLogProvider.GetForContextMethodCall() 在这种情况下。但是,SerilogLogProvider 是我无法访问的内部 class。
我尝试的最后一件事是将 Serilog 和 MvvmCross.Logging.LogProviders 添加到“跳过链接程序集”。也不行。
非常感谢您的提前帮助。
此致,
尼克
问题是 SerilogLogProvider
对 Serilog.dll
(See GitHub SerilogLogProvider
source) 使用反射。即使您可以访问 SerilogLogProvider
class,它也无助于防止链接器剥离所需的方法。原因是链接器实际上正在从 Serilog.dll
中剥离您需要的方法。
您可以将以下包含添加到您的 LinkerPleaseInclude.cs
以防止链接器删除 SerilogLogProvider
使用的方法。
public void Include(Serilog.ILogger logger)
{
Serilog.Events.LogEventLevel logEventLevel = Serilog.Events.LogEventLevel.Debug;
_ = Serilog.Log.ForContext("", "", false);
_ = Serilog.Context.LogContext.PushProperty("", "", false);
_ = !logger.IsEnabled(logEventLevel);
logger.Write(logEventLevel, "", new object[0]);
logger.Write(logEventLevel, new Exception(), "", new object[0]);
}