Skip to content

fix(cef): expose CDP port in release builds so embedded webviews navigate #960

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
senamakel merged 1 commit into from
Apr 27, 2026
+9 −3
Merged

fix(cef): expose CDP port in release builds so embedded webviews navigate #960

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 9 additions & 3 deletions app/src-tauri/src/lib.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -824,9 +824,15 @@ pub fn run() {
// silently disappears and huddle/call buttons no-op.
("--enable-features", Some("SharedArrayBuffer")),
];
if cfg!(debug_assertions) {
args.push(("--remote-debugging-port", Some("19222")));
}
// Always expose the CDP port, not just in debug. The webview-accounts
// CDP session opener navigates each embedded provider webview from its
// `about:blank#openhuman-acct-...` placeholder to the real provider URL
// via `Page.navigate`. Without this port available in release builds,
// the CDP client can't attach (`browser_ws_url()` 404s on /json/version),
// the navigation never fires, and the embedded webview stays on
// `about:blank` (blank panel for Telegram / WhatsApp / Slack / Discord).
// Same port the `cdp::CDP_HOST`/`cdp::CDP_PORT` constants expect.
args.push(("--remote-debugging-port", Some("19222")));
tauri::Builder::<tauri::Cef>::new().command_line_args::<&str, &str>(args)
};

Expand Down
Loading