You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Session replay: throttleDelay cannot be changed after setup() #765
The interval is baked into the subscription, so mutating config.sessionReplayConfig.throttleDelay after setup(_:) has no effect until the integration restarts.
Apps with screens of very different interaction density want a finer interval on some screens and a coarser one elsewhere. Today the only options are restarting the SDK or accepting one global value.
Proposal: support updating throttleDelay at runtime, either by re-reading the config value per capture or by exposing a setter that re-subscribes with the new interval. The JS SDK's set_config allows post-init changes, so there is precedent for runtime reconfiguration.
this would be a bigger change, the options are immutable by design, if we want to change this, we'd have to make the whole config mutable, and this is an issue for all features that depend on eg swizzling, once you swizzle, you can't unswizzle without side effects
Activity
marandaneto commentedon Aug 14, 2026
this would be a bigger change, the options are immutable by design, if we want to change this, we'd have to make the whole config mutable, and this is an issue for all features that depend on eg swizzling, once you swizzle, you can't unswizzle without side effects