Skip to content

Android KMP Paywall Events are sent to the Production Amplitude project instead of Sandbox and use incorrect platform value (android instead of Android) - #3954

Open
tsushanth wants to merge 1 commit into
RevenueCat:mainfrom
tsushanth:fix/Android-KMP-Paywall-Events-are-sent-to-t-1786378346
Open

Android KMP Paywall Events are sent to the Production Amplitude project instead of Sandbox and use incorrect platform value (android instead of Android)#3954
tsushanth wants to merge 1 commit into
RevenueCat:mainfrom
tsushanth:fix/Android-KMP-Paywall-Events-are-sent-to-t-1786378346

Conversation

@tsushanth

@tsushanth tsushanth commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Change WORKFLOW_CONTEXT_PLATFORM from "android" to "Android" in BackendEvent.Workflows.Context to fix the incorrect platform value sent with KMP paywall workflow events.

Scoped to just the platform-casing bug. The original report also mentions KMP paywall events being sent to the Production Amplitude project instead of Sandbox — that's a separate, unrelated issue and will be tracked/fixed in its own PR rather than bundled in here.

Found via automated repo scanning, fix written and reviewed before opening.


Note

Low Risk
Single string constant and test expectation change for analytics payload casing only; no auth, billing, or runtime behavior changes.

Overview
Fixes the context.platform value on serialized workflow backend events (KMP paywall workflow lifecycle) so it is "Android" instead of "android", matching the expected khepri / WorkflowsEvent wire shape.

The default comes from WORKFLOW_CONTEXT_PLATFORM in BackendEvent.Workflows.Context; workflow serialization tests were updated to assert "Android" in encoded JSON.

Reviewed by Cursor Bugbot for commit 4f09ffb. Bugbot is set up for automated code reviews on this repo. Configure here.

…project instead of Sandbox and use incorrect platform value (android instead of Android)
@tsushanth
tsushanth requested a review from a team as a code owner August 13, 2026 00:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant