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:

[IIiKoBiT]

When will it be fixed?
This is very critical for me. Is there a way to temporarily fix this?

[IIiKoBiT]

@GregorBiswanger
I didn't wait for an answer, I cloned the whole project and built it. The disconnect problem is gone and everything works well. But any resources stopped working for me, there are no icons and images, what could it be?

[danatcofo]

I believe this is fixed as of 11.5.1 @GregorBiswanger

[JollyRoger91]

@danatcofo Unfortunately, this bug is not fixed yet.

I'm facing this issue now too and I'm using the latest release 11.5.1

As @Gaulomatic pointed out, it seems that this issue depends on the machine. Our Software runs on 30-40 machines without any issue, but on 4 machines this issue happens frequently. I do not see any obvious difference between the machines which work and the machines which won't work.

• All are physical machines (no VMs)
• All running Windows 10 (1903 to 2004)
• It happens irregularly (Sometimes it fails after 10 Minutes, sometimes it fails after a couple of hours (max 5))

@IIiKoBiT I don't quite understand how this bug can be fixed if I compile this project myself? Did you make additional make any changes to the code?

[GregorBiswanger]

I can hardly reproduce it. We need support.

Here is a video of how you can install the missing features yourself and submit them as a pull request: https://youtu.be/Po-saU_Z6Ws

Please also test it with you.