Skip to content

Commit ea3f1e3

Browse files
authored
feat(replay): Add troubleshooting item for cross origin frames (#14674)
This adds a new troubleshooting item to address the replay SDK causing cross-origin frame errors.
1 parent 2450641 commit ea3f1e3

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

docs/platforms/javascript/common/session-replay/troubleshooting.mdx

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -131,6 +131,23 @@ To hide this content, block the iframe, as described in our Session Replay <Plat
131131

132132
</Expandable>
133133

134+
<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>
135+
136+
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:
137+
138+
```javascript
139+
Sentry.init({
140+
dsn: "...",
141+
replaysSessionSampleRate: 1,
142+
integrations: [
143+
Sentry.replayIntegration({
144+
block: ["iframe"],
145+
}),
146+
],
147+
})
148+
```
149+
</Expandable>
150+
134151
<Expandable title="Replay on my browser extension doesn't work" permalink>
135152

136153
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.

0 commit comments

Comments
 (0)