From 0f6355496241d98919d76b08b95b794b64bfaac7 Mon Sep 17 00:00:00 2001
From: Dhiogo Brustolin <dhiogo.brustolin@sentry.io>
Date: Thu, 7 Nov 2024 10:59:36 +0100
Subject: [PATCH] Update Sources/Sentry/SentrySessionReplayIntegration.m

---
 Sources/Sentry/SentrySessionReplayIntegration.m | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Sources/Sentry/SentrySessionReplayIntegration.m b/Sources/Sentry/SentrySessionReplayIntegration.m
index 2aced23b41..3c5245dac7 100644
--- a/Sources/Sentry/SentrySessionReplayIntegration.m
+++ b/Sources/Sentry/SentrySessionReplayIntegration.m
@@ -48,6 +48,8 @@ @implementation SentrySessionReplayIntegration {
     SentryNSNotificationCenterWrapper *_notificationCenter;
     SentryOnDemandReplay *_resumeReplayMaker;
     id<SentryRateLimits> _rateLimits;
+   // We need to use this variable to identify whether rate limiting was ever activated for session replay in this session, instead of always looking for the rate status in `SentryRateLimits`
+   // This is the easiest way to ensure segment 0 will always reach the server, because session replay absolutely needs segment 0 to make replay work.
     BOOL _rateLimited;
 }