PostHog / PostHog/posthog-android
Network bodies for network logs
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 90
- Forks
- 49
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 61
Description
Description
This should go somewhere here https://github.com/PostHog/posthog-ios/blob/b0c6c1847228ce1fb78438be21cfe39cddc55254/PostHog/Replay/URLSessionInterceptor.swift#L108-L117
Some builtin PII scrubbing is necessary, take a look at the JS SDK.
- Android (this issue)
- iOS (https://github.com/PostHog/posthog-ios/issues/159)
- RN (https://github.com/PostHog/posthog-js/issues/3810)
- Flutter (https://github.com/PostHog/posthog-flutter/issues/422)
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 comparing the Android network logging implementation with the referenced iOS URLSessionInterceptor.swift lines 108-117 and the JS SDK's PII-scrubbing behavior. Determine where network response bodies should be captured and what builtin scrubbing is required; done means network logs include safely scrubbed bodies across the relevant cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100