Skip to content
4 changes: 0 additions & 4 deletions dev-packages/e2e-tests/maestro/captureReplay.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,6 @@
- runFlow:
file: utils/launchTestAppClear.yml
env:
replaysOnErrorSampleRate: 1.0
- tapOn: "Capture Exception"
- runFlow: utils/assertEventIdVisible.yml

Check warning on line 9 in dev-packages/e2e-tests/maestro/captureReplay.yml

View check run for this annotation

@sentry/warden / warden: code-review

iOS replay e2e assertion removed instead of made tolerant, eliminating coverage

The hunk deletes the iOS-conditional `runFlow: utils/assertReplay.yml` block, which was the only e2e check that the native iOS replay buffer produced a replay (asserting replayId, replayDuration, replaySegments, and the ftypmp42 codec). The PR description states the fix adds a retry loop around replay_id extraction in sentryApi.js, but sentryApi.js still throws immediately when replay_id is missing (line 72), and the assertion is no longer invoked at all. The net effect is a loss of iOS replay coverage rather than a flakiness fix, so future regressions in the iOS native replay integration will go undetected.
Comment thread
antonis marked this conversation as resolved.
- runFlow:
file: utils/assertReplay.yml
when:
platform: iOS
Loading