Electron.net: Socket Disconnection Error

[AykutToprak]

• Version: 9.31.2
• CLI Version: 9.31.2
  

• Target: .NET Core 3.1

Got disconnect! Reason: transport close
ASP.NET Core Application connected... global.electronsocket fVcXgik5tZt05sn7AAAB 2020-07-21T13:23:13.319Z
stdout: BridgeConnector connected!

As it showed above socket are disconnected and reconnected again. This caused problem for IPC Listeners. I guess they are somehow removed.
Is there any workaround to solve this? @GregorBiswanger

Similar issue : #442 #428

[rakista112]

I've been facing this issue too. One minute all IPC works properly, then a transport error appears and it doesn't try to reconnect.
I'm using ElectronNET.CLI Version: 9.31.2.0
Here is the error that's being displayed.

Got disconnect! Reason: transport error
ASP.NET Core Application connected... global.electronsocket dZkuRoGtHpejWwBYAAAC 2020-07-29T11:42:47.602Z
stdout: BridgeConnector connected!

stdout: dbug: Microsoft.AspNetCore.Server.Kestrel[10]
      Connection id "0HM1JMHGH414A" disconnecting.
dbug: Microsoft.AspNetCore.Server.Kestrel[10]
      Connection id "0HM1JMHGH4149" disconnecting.

stdout: dbug: Microsoft.AspNetCore.Server.Kestrel[2]
      Connection id "0HM1JMHGH4149" stopped.
dbug: Microsoft.AspNetCore.Server.Kestrel[2]
      Connection id "0HM1JMHGH414A" stopped.

stdout: dbug: Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets[7]
      Connection id "0HM1JMHGH4149" sending FIN because: "The Socket transport's send loop completed gracefully."

stdout: dbug: Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets[7]
      Connection id "0HM1JMHGH414A" sending FIN because: "The Socket transport's send loop completed gracefully."

[GregorBiswanger]

Normally the socket connection should restore the registrations. Have you lost these?

[AykutToprak]

Socket connection is restored however IPC Listeners are not. Commitications between front-end and back-end are completely disconnected

[Gaulomatic]

I am encountering this issue as well. On _some_ Windows 10 machines this leads to the situation where the app can not quit itself anymore. The main process is killed, but all remaining Electron processes as well as the ASP.NET core process run until they are force killed by any means (e.g. TaskManager).

EDIT:
Here is an example if you invoke Electron.WindowManager.BrowserWindows.First().Maximize(); after the disconnect happened: