[BETA] Remote Sync stuck on "Waiting for local session" on Windows Desktop

Title

Remote Sync cannot start because notify-local-login is not exposed by preload

Beta Build

2.8.0-beta

Platform

App - Windows

Server Installation Method

Docker

Does this happen on the latest stable release too?

No, only happens on this beta build

Troubleshooting

• I am running the :beta tag, a dated beta pre-release, or a CLI pre-release, not stable
• I have examined logs and tried to find the issue
• I have restarted the application and the issue persists
• I understand beta builds are unstable and this may be a known issue

The Problem

Remote Sync cannot be configured in Windows Desktop Beta 2.8.0.

When trying to set up Remote Sync from scratch, the connection to the self-hosted Termix server succeeds and the login is accepted, but the setup does not complete.

Instead, Termix immediately gets stuck with:

Waiting for local session

This does not happen in stable 2.7.1.

I confirmed it several times:

• Remote Sync can be configured and works normally in 2.7.1.
• After upgrading to Beta 2.8.0, Remote Sync breaks with Waiting for local session.
• Downgrading back to 2.7.1 restores normal operation.
• Upgrading again to Beta 2.8.0 reproduces the same problem.

How to Reproduce

1. Install Windows Desktop Beta 2.8.0.
2. Open Remote Sync settings.
3. Enter the URL of a self-hosted Termix server.
4. Sign in with valid credentials.
5. Authentication succeeds, but Remote Sync setup does not complete.
6. The client shows Waiting for local session.

The same setup works normally in stable 2.7.1.

Additional Context

I found a local workaround that confirms the issue is in Beta 2.8.0.

RemoteSyncEngine expects the local JWT through the notify-local-login IPC handler, but notify-local-login is missing from ALLOWED_INVOKE_CHANNELS in electron/preload.js.

After adding:

"notify-local-login",

to the preload allowlist and restarting Termix, I manually ran:

await window.electronAPI.invoke(
  "notify-local-login",
  localStorage.getItem("jwt")
)

which returned:

{ success: true }

Then:

await window.electronAPI.invoke("remote-sync-now")

completed successfully with:

{
  connected: true,
  syncing: false,
  lastError: null,
  needsReauth: false
}

So the issue appears to be caused by the local session JWT not reaching RemoteSyncEngine in Beta 2.8.0.

Start in electron/preload.js and inspect ALLOWED_INVOKE_CHANNELS, then trace how RemoteSyncEngine receives the local JWT through notify-local-login. Reproduce the setup on Windows Desktop Beta 2.8.0 and verify that Remote Sync proceeds past “Waiting for local session” with a successful remote-sync-now result.