Electron.IpcMain.On doesn't allow for event parameter #649

New Issue

claunia · 2026-01-29T16:45:07Z

claunia commented

2026-01-29 16:45:07 +00:00

Originally created by @Zshandi on GitHub (Apr 14, 2021).

Originally assigned to: @GregorBiswanger on GitHub.

Version: 11.5.1

Target: Windows

Inside my main process, I am trying to receive a signal from my renderer process using IpcMain.On() and return a value back to the renderer process. The issue I am having is that I cannot access the event parameter inside of the callback function. I am receiving a compile time error stating that event is an "Invalid Expression term".

I looked at the source code for On() inside IpcMain.cs and it doesn't seem to be calling the listener callback function with an event parameter.
The comments say that the listener will be called as such:

///  Listens to channel, when a new message arrives listener would be called with 
///  listener(event, args...).

But looking at the implementation, it doesn't seem to be calling the listener with the event parameter as it says it does:

        public void On(string channel, Action<object> listener)
        {
            BridgeConnector.Socket.Emit("registerIpcMainChannel", channel);
            BridgeConnector.Socket.Off(channel);
            BridgeConnector.Socket.On(channel, (args) => 
            {
                List<object> objectArray = FormatArguments(args);

                if(objectArray.Count == 1)
                {
                    listener(objectArray.First());
                }
                else
                {
                    listener(objectArray);
                }
            });
        }

In particular, Action<object> listener forces the listener to only take a single argument, and listener(objectArray.First()); or listener(objectArray); only pass the argument object list, which doesn't include an event.

Steps to Reproduce:

Use the following code in the main process:

Electron.IpcMain.On("signal-name", (event, args) => {
  // Do something(or not, either way it still gives the error)
});

Originally created by @Zshandi on GitHub (Apr 14, 2021). Originally assigned to: @GregorBiswanger on GitHub.    * **Version**: 11.5.1   * **Target**: Windows   Inside my main process, I am trying to receive a signal from my renderer process using `IpcMain.On()` and return a value back to the renderer process. The issue I am having is that I cannot access the event parameter inside of the callback function. I am receiving a compile time error stating that event is an "Invalid Expression term". I looked at the source code for `On()` inside `IpcMain.cs` and it doesn't seem to be calling the listener callback function with an event parameter. The comments say that the listener will be called as such: ``` /// Listens to channel, when a new message arrives listener would be called with /// listener(event, args...). ``` But looking at the implementation, it doesn't seem to be calling the listener with the event parameter as it says it does: ``` public void On(string channel, Action<object> listener) { BridgeConnector.Socket.Emit("registerIpcMainChannel", channel); BridgeConnector.Socket.Off(channel); BridgeConnector.Socket.On(channel, (args) => { List<object> objectArray = FormatArguments(args); if(objectArray.Count == 1) { listener(objectArray.First()); } else { listener(objectArray); } }); } ``` In particular, `Action<object> listener` forces the listener to only take a single argument, and `listener(objectArray.First());` or `listener(objectArray);` only pass the argument object list, which doesn't include an event. Steps to Reproduce: 1. Use the following code in the main process: ``` Electron.IpcMain.On("signal-name", (event, args) => { // Do something(or not, either way it still gives the error) }); ```

claunia added the bug label 2026-01-29 16:45:08 +00:00

claunia referenced this issue

2026-01-29 16:58:50 +00:00

[PR #649] [CLOSED] new version not works #1242

claunia referenced this issue

2026-01-29 16:58:52 +00:00

[PR #649] new version not works #1245

Sign in to join this conversation.