Skip to content

fix: [MR-179] added container-side event emitter for AppEventPayload - #290

Open
janfb-codev wants to merge 1 commit into
epic/MR-166from
feature/MR-179
Open

fix: [MR-179] added container-side event emitter for AppEventPayload#290
janfb-codev wants to merge 1 commit into
epic/MR-166from
feature/MR-179

Conversation

@janfb-codev

@janfb-codev janfb-codev commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Changes

  • Added AppEventEmitter as the single entry point for emitting an AppEventPayload. Java callers can now emit events without going through the WebView bridge, which was previously the only way in.
  • Added AppEventPayloadBuilder for Java-side payload construction. .add() / .replace() populate data and options together so an invalid merge option is unconstructible, and timestamp is stamped automatically.
  • Added an optional AppEventWriteCallback (onQueued / onWritten / onFailed). onQueued fires when the write is durable in Firestore's local persistence queue; onWritten fires only on server ack, which offline may be much later or never. Callers holding the only other copy of a measurement should release it on onQueued.
  • WebApp.logMessage() now delegates to the emitter JSON parsing, validation and dispatch moved out of the Activity.
  • Payload-rejection logs moved from tag WebApp to AppEventEmitter (message text unchanged).

Groundwork for MR-180 through MR-184, which write container-measured sub-app usage into summary_data.

How to test

  • Launch Feed The Monster from the container, complete a level and a puzzle. Confirm summary_data and user_sessions_data are written exactly as before same metadata (including container_app_version, country, language), same attribution, and data fields still accumulating rather than overwriting.
  • Watch the bridge path with adb logcat -s AppEventEmitter AppEventHandler.

Ref: MR-179

@janfb-codev janfb-codev self-assigned this Aug 19, 2026
@coderabbitai

coderabbitai Bot commented Aug 19, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (3)
  • develop
  • test
  • main

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 8c682a1f-528c-45ba-9fb3-07b3b1619d6b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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