PostHog / PostHog/posthog-android
Stop all integrations like session replay and autocapture on opt-out
Open
Nobody has claimed this yet.
bug
Session Replay
- Dominant language
- Kotlin
- Stars
- 90
- Forks
- 49
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 61
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 (this issue)
- RN (https://github.com/PostHog/posthog-js/issues/3813)
- Flutter (https://github.com/PostHog/posthog-flutter/issues/427)
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
No files, tests, or entry points are named. Start by tracing opt-out and opt-in handling for the session replay and autocapture integrations; done means all integrations stop on opt-out, restart on opt-in, and session replay creates a new session after opting in.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100