PostHog / PostHog/posthog-flutter
Stop all integrations like session replay and autocapture on opt-out
Open
Nobody has claimed this yet.
bug
- Dominant language
- Dart
- Stars
- 97
- Forks
- 85
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Description
Original discussion: https://github.com/PostHog/posthog-ios/pull/276#discussion_r1905431037
When opting-out, we should stop() all integrations since they won't be processed by the SDK, and then start() again on next opt-in.
For session replay, when opting-in a new session should be created.
- iOS
- Android (https://github.com/PostHog/posthog-android/issues/242)
- RN (https://github.com/PostHog/posthog-js/issues/3813)
- Flutter (this issue)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Flutter SDK's opt-out handling and how integrations such as session replay and autocapture are started and stopped. Done means every integration stops on opt-out, starts again on the next opt-in, and session replay creates a new session after opting back in.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100