PostHog / PostHog/posthog-flutter
Respect session replay feature flag after /config endpoint call
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 97
- Forks
- 85
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Description
Ticket: https://posthoghelp.zendesk.com/agent/tickets/20809 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/29952)
Session recordings start as soon as the app launches, but feature flag evaluation is executed asynchronously.
If the cached value is different that the value returned from /decide endpoint, then the recording may start (and not stop) when the flag evaluates to false
A possible fix is to mem-cache screenshots and skip processing until the /decide API has been successfully called - there are some memory footprint consideration here. We may need to use a different disk-backed queue, and drop or merge the queues once the flag evaluates?
- iOS (https://github.com/PostHog/posthog-ios/issues/263)
- Android (https://github.com/PostHog/posthog-android/issues/575)
- Flutter (this issue)
- RN (https://github.com/PostHog/posthog-js/issues/3859)
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
Trace the Flutter session recording startup path alongside the asynchronous feature-flag evaluation and the /decide endpoint call. Review the proposed screenshot caching or queue behavior, then verify that recording does not start or continue when the evaluated session replay flag is false.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100