getsentry
Uploading Session Replay When it should not?
Platform
iOS
Environment
Production
Installed
Swift Package Manager
Version
8.44.0
Xcode Version
16.2
Did it work on previous versions?
No response
Steps to Reproduce
My session replay configuration is set like:
options.sessionReplay.sessionSampleRate = 0.0
options.sessionReplay.onErrorSampleRate = 0.5
Expected Result
Should not upload a full session replay to Sentry
Actual Result
I am seeing a full session replay uploaded to Sentry web WITHOUT an error.
Are you willing to submit a PR?
No response
Hi @acfriedman, thanks for reporting this issue.
Can you please provide your full Sentry configuration block (or ideally a reproducible project), so I can try to reproduce it in our sample projects?
Furthermore, are you using SentrySDK.replay.start() in your application?
Hi @philprime
I spoke with "Billy" about this in Discord, and he said that this specific issue that I was seeing was a result of the error being filtered out due to rate limiting. Which makes sense to me. Our project has a very low rate limit at the moment.
However, Billy also said:
I'm also seeing other oddities with that replay that we will look into (e.g. most of that replay is "unavailable" which looks wrong)
I'd also like to suggest a feature enhancement, that is, our app has very long sessions, and its very unlikely that most of these sessions will require the full recording after an error. If we could set a max duration on the replay that would be nice. I'm not sure how much an hour+ video impacts performance, but even if its still negligible the UX doesn't seem great either way.
Furthermore, are you using SentrySDK.replay.start() in your application?
We are not
Also, I am no longer seeing this particular replay in the sentry Web view.. looks like it was potentially deleted
@acfriedman hey, Billy here -- we took another look at it, and some details in the replay suggest it may not be due to rate limiting (the replayType says it's session), so we're continuing investigation.
Sorry @acfriedman for the long delay on this issue. Can you still reproduce the issue with the latest version of the SDK?