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
Allow postponing event captures until User Consent is collected #6758
Have the SDK operate ‘properly’, with it's configured features such as Replay. But ‘hold off’ on sending events until consent is given. If revoked stop events from being sent again.
changed the title [-]Allow postponing event captures until _User Consent_ is collected[/-][+]Allow postponing event captures until User Consent is collected[/+]on Jan 12, 2023
Activity
[-]Allow postponing event captures until _User Consent_ is collected[/-][+]Allow postponing event captures until User Consent is collected[/+]bruno-garcia commentedon Mar 30, 2023
@AbhiPrasad any notes on why we decided not to go ahead with this?
AbhiPrasad commentedon Mar 31, 2023
Nope, I think it just fell through the cracks. I moved it to Archived since it was a stale-bot closed issue. We can re-open and backlog!
zemlanin commentedon Jul 8, 2024
Hi. What is expected way of handling user consent until this issue is resolved?
Add
<script>/callSentry.initonly after user has agreed to gathering analytics? Something else?17 remaining items
timfish commentedon Feb 3, 2025
They get stored until another envelope is sent and
shouldSendreturns true. Once one envelope is sent successfully the rest are attempted.There is also an option to attempt flushing shortly after startup.
github-actions commentedon Apr 16, 2025
A PR closing this issue has just been released 🚀
This issue was referenced by PR #15937, which was included in the 9.13.0 release.