Recording playback isn't working

[younes0]

Description

Recording playback isn't working & console shows error:
analytics-4yf9mS08.js:4 Fetch API cannot load https://eu.i.posthog.com/e/?retry_count=1&ip=1&_=1771120088462&ver=1.240.0. Refused to connect because it violates the document's Content Security Policy.

I doubt it's related, may be 2 different bugs.

Reproduction

1. Record screen
2. Hit "Play" icon or space keyboard
3. Nothing will happen except the console logging the error everytime when do the previous action.

Additional Context

• Cap version: 4.6
• Operating system, version: Windows 11

[linear]

CAP-640

[tembo]

This appears to be a duplicate of #1505 which reports the same CSP error blocking PostHog in the desktop editor. The error message is nearly identical:

Connecting to 'https://eu.i.posthog.com/...' violates the following Content Security Policy directive: 
"default-src 'self' ws: ipc: http://ipc.localhost". Note that 'connect-src' was not explicitly set, 
so 'default-src' is used as a fallback.

The root cause is in apps/desktop/src-tauri/tauri.conf.json - the current CSP policy does not include a connect-src directive, so the restrictive default-src falls back and blocks external HTTPS connections including PostHog's eu.i.posthog.com endpoint.

Current policy:

default-src 'self' ws: ipc: http://ipc.localhost; 
img-src 'self' asset: http://asset.localhost blob: data:; 
media-src 'self' asset: http://asset.localhost; 
script-src 'self' 'unsafe-eval' 'wasm-unsafe-eval'; 
style-src 'self' 'unsafe-inline'

A fix would involve adding a connect-src directive that allows the PostHog domains:

connect-src 'self' ws: wss: https://eu.i.posthog.com https://eu-assets.i.posthog.com https://us.i.posthog.com;

The user is correct that the CSP error itself likely isn't causing the playback failure directly - the PostHog analytics should fail gracefully. However, depending on how the error propagates, it could potentially interfere with initialization. It would help to confirm whether playback works in older versions (pre-4.2) to isolate if this is a regression related to recent playback optimizations in #1598.

[younes0]

Let me try Cap 4.1 then and get back to you.

EDIT: same issues & still no logs