[turnipdabeets]

Important

Stacked on #108 and depends on PostHog/posthog-android#908. posthog-android 4.0 removes wireframe replay and PostHogSessionReplayConfig.screenshot, so #108 no longer compiles for Android without this. If PostHog/posthog-android#908 is dropped from 4.0, close this PR.

💡 Motivation and Context

posthog-ios 4.0 (PostHog/posthog-ios#907, PostHog/posthog-ios#973) and posthog-android 4.0 (PostHog/posthog-android#908) both drop wireframe session replay. Replay always records masked screenshots. #108 already stopped forwarding screenshot to iOS. Android's flag is now gone as well, so SessionRecordingConfig.screenshot doesn't do anything on any platform.

Changes:

• Remove SessionRecordingConfig.screenshot and stop passing it to PostHogSessionReplayConfig on Android.
• Remove the JVM constructor and copy overloads kept for the pre-verifyScreenshotMaskAlignment signature, along with their Java test (SessionRecordingConfigJavaTest). That signature included screenshot, so it can't be kept. Leaving a 7-argument overload next to the primary constructor would also make SessionRecordingConfig() ambiguous.
• Drop "Only applies when [screenshot] is enabled" from the verifyScreenshotMaskAlignment KDoc.
• Changeset: minor with a Breaking: entry, the same as chore!: adopt posthog-android 4.0, core 7.0 and posthog-ios 4.0 #108.

This removes the option rather than deprecating it, matching the native SDKs. An app that set screenshot = false to keep pixels out of recordings gets a compile error instead of silently uploading masked screenshots.

💚 How did you test it?

Built against posthog-android 4.0.0 / core 7.0.0 published from PostHog/posthog-android#908 to a local Maven repo, using an init script so the build files stay unchanged:

• PostHogAndroidConfigTest (4), PostHogConfigTest on Android host and JVM (16 each), PostHogConfigJavaTest (2): pass.
• detekt and :sample:androidApp:compileDebugKotlin: pass.
• 12 JVM and 10 Android-host routing tests (testCaptureRoutesCorrectly, testAliasRoutesCorrectly, …) fail with expected [new_alias, null] but was [new_alias]. chore!: adopt posthog-android 4.0, core 7.0 and posthog-ios 4.0 #108 alone fails the same 12 JVM tests against these artifacts: they expect the trailing options argument from the capture-v1 PRs (feat!: send events through capture v1 and add captureAi posthog-android#881/#882), which aren't in this Android base. chore!: adopt posthog-android 4.0, core 7.0 and posthog-ios 4.0 #108 alone can't compile Android against these artifacts, so there's no Android-host baseline. Its 10 failures are the same routing tests with the same message.
• Not run: Apple targets. This PR doesn't touch iosMain / appleMain, and commonMain only loses a constructor parameter.

📝 Checklist

• I reviewed the submitted code.
• I added tests to verify the changes.
• I updated the docs if needed.
• No breaking change or entry added to the changelog. (Breaking; changeset added.)

If releasing new changes

• Ran pnpm changeset to generate a changeset file

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

• Written with Claude Code (Opus 5.5) at the maintainer's request, as a follow-up to the Android wireframe removal.
• Chose removal over a deprecated no-op to match posthog-ios/posthog-android 4.0. If we'd rather keep KMP source-compatible, a @Deprecated no-op is a small change.

🤖 Generated with Claude Code

[sampo-s-bot]

⚠️ No changeset detected

No new .sampo/changesets/*.md files were detected in this PR. To add one:

• run sampo add
• follow the prompts to pick the affected packages and describe the change
• commit the generated file to this pull request, and it will be detected automatically

If this PR isn't supposed to introduce any changes (e.g., documentation updates), you can ignore this message.