Error running exported app from latest preview

Hey,

This is on 5.3-318. I’m building an app that makes use of Skia and Redis. The build goes on just fine, but when I try to run my executable, I’m getting this Exception :

Exception
System.Exception: The required service System.Threading.SynchronizationContext was not found
   at VL.Core.ServiceProviderExtensions.GetRequiredService[T](IServiceProvider serviceProvider)
   at VL.AppServices.AppHostBase.get_SynchronizationContext()
   at _VL_Reactive_.Reactive.ToMainThread_NZOQYzLzdQ4QYpoHttT0mT`1.<>c__DisplayClass3_0`1.<Update>b__0()
   at _CoreLibBasics_.Primitive.Delegates.Delegate__0_MG_1._Operations_.Invoke[T](Func`1 Input_In, T& Result_Out)
   at _VL_Reactive_.Reactive.ToObservable_Switch_Factory_C`1.Update[T2,AdM](Func`1 Factory_In, Boolean Send_In, IObservable`1& Result_Out)
   at _VL_Reactive_.Reactive.ToMainThread_NZOQYzLzdQ4QYpoHttT0mT`1.Update[AdM](IObservable`1 Input_In, AppHost App_Host_In, IObservable`1& Result_Out)
   at _VL_Reactive_.Reactive.ReactOnMainThread_AQwd5D1b4nXLUb46HTAFTF`1.Update[AdM](IObservable`1 Input_In, AppHost App_Host_In, Action`1 Action_In)
   at _PublicAPI_.VL.SaveToModelPin_C`1.__Create__[AdM](IChannel`1 Model_Stream_In, NodeContext Node_Context_In, Boolean Enabled_In, String Pin_Name_In)
   at _PublicAPI_.VL.SaveToModelPin_C`1.Create[AdM](IChannel`1 Model_Stream_In, NodeContext Node_Context_In, Boolean Enabled_In, String Pin_Name_In)
   at _AppName_.AppName.Redis.Redis_C.__Create__(RedisConfig_R Redis_Config_In, NodeContext Node_Context_In)
   at _AppName_.AppName.Redis.Redis_C.Create(RedisConfig_R Redis_Config_In, NodeContext Node_Context_In)
   at _AppName_.__auto.AppNameApplication_KJVrcuPxxN3P3cJfYHjLLz.__Create__(NodeContext Node_Context)
   at _AppName_.__auto.AppNameApplication_KJVrcuPxxN3P3cJfYHjLLz.Create(NodeContext Node_Context)
   at Program.<>c.<Main>b__0_0(NodeContext c)
   at VL.AppServices.ExportedAppHost.<>c__DisplayClass22_1.<RunCoreAsync>b__1(Object _)

Exporting the same app under 310 works just fine. Can provide the patch privately if need be.

Thanks in advance!

True, sorry for that one. Fix in upcoming.

2 Likes