Skip to content

feat(replay): Add troubleshooting item for cross origin frames #14674

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
merged 1 commit into from
Sep 25, 2025
Merged

feat(replay): Add troubleshooting item for cross origin frames #14674

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
17 changes: 17 additions & 0 deletions docs/platforms/javascript/common/session-replay/troubleshooting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,6 +131,23 @@ To hide this content, block the iframe, as described in our Session Replay <Plat

</Expandable>

<Expandable title="I'm getting the error: Blocked a frame with origin '...' from accessing a frame with origin '...'. Protocols, domains, and ports must match." permalink>

The replay SDK attempted to access a cross-origin frame but was not allowed to. You will need to block the iframe in order to stop the errors:

```javascript
Sentry.init({
dsn: "...",
replaysSessionSampleRate: 1,
integrations: [
Sentry.replayIntegration({
block: ["iframe"],
}),
],
})
```
</Expandable>

<Expandable title="Replay on my browser extension doesn't work" permalink>

This is not a supported use-case. The replay package is built to work on a website and not as an externally-loaded script via browser extension or other mechanism. In fact, Sentry's Session Replay product can help developers find out when a third-party Chrome extension causes otherwise hard to debug or reproduce issues with their website.
Expand Down