PostHog / PostHog/posthog-flutter
Session replay: capture console/print logs into replay
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 97
- Forks
- 85
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Part of the replay parity tracker PostHog/posthog#30889.
Problem
posthog-js records console logs into the replay ($console_log). Flutter has no equivalent: the Android layer hard-disables it (captureLogcat = false in PosthogFlutterPlugin.kt), iOS has no console-into-replay, and the Dart pipeline captures only screenshots. So Dart print/logging output never reaches the replay.
Scope
- Capture Dart
print/logging output into the replay stream.
Note: value is limited on Flutter's screenshot-based replay, worth weighing before prioritizing.
Reference: posthog-js console-log recording in packages/browser/src/extensions/replay/external/lazy-loaded-session-recorder.ts.
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 with the Android setting in PosthogFlutterPlugin.kt and compare it with the iOS replay path, then trace the Dart screenshot-based replay pipeline. Use the posthog-js recorder in packages/browser/src/extensions/replay/external/lazy-loaded-session-recorder.ts as the reference; done means Dart print or logging output is captured in the replay stream on the supported platforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, dart, flutter, ios
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100