ci(example): publish example app to Play Store internal track

[evan-masseau]

Summary

• Adds .github/workflows/publish-example-android.yml to build and publish the React Native SDK example app (com.klaviyoreactnativesdkexample) to the Google Play internal track
• Triggers on release: published (mirrors the Android test app pattern) and workflow_dispatch for manual publishes
• Handles Node 20 + Yarn 3 workspace setup, JS bundle generation via the RN Gradle plugin, AAB signing, and Play Store upload
• Includes Slack notifications for both success and failure

Motivation

The RN SDK example app needs to be distributable via Play Store internal track for QA and stakeholder testing, matching what the Android test app already does. Branches off ecm/example-app/4-native (PR #345) since the Play Store pipeline depends on that PR's Android Firebase + bundle-id setup.

Parallel CI improvement: klaviyo-android-test-app — Slack notifications on publish, which brings the test app's publish workflow to parity with this one.

Required Secrets

Wire these up in repo Settings → Secrets and variables → Actions before the workflow will succeed:

Secret	Description
GOOGLE_SERVICES_JSON	Contents of google-services.json for Firebase
SIGNING_KEY	Base64-encoded release keystore (upload key for Play App Signing)
ALIAS	Key alias in the keystore
KEY_STORE_PASSWORD	Keystore password
KEY_PASSWORD	Key password
SERVICE_ACCOUNT_JSON	Google Play service account JSON (plain text)
KLAVIYO_EXAMPLE_API_KEY	Klaviyo public API key — written into example/.env at build time so the RN app initializes Klaviyo on launch
SLACK_WEBHOOK_URL	Incoming webhook URL for Slack notifications

A guard step early in the workflow fails the run with a clear message if KLAVIYO_EXAMPLE_API_KEY is unset — no silent fallback, no crashing builds on Play Store.

Test plan

• Wire up all required secrets in the repo
• Trigger via workflow_dispatch and confirm the AAB is uploaded to the Play Store internal track
• Confirm Slack notification fires in both success and failure cases
• Verify the published app launches and initializes Klaviyo correctly on a test device (check for a Klaviyo event from the build's API key)

Part of MAGE-464

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 7f6e898. Configure here.}

[evan-masseau]

I need to add a trigger here that I can use to test this on github actions, before merging to master... maybe a label?

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 0924305. Configure here.}

[cursor]

Temporary push trigger left in workflow file

Medium Severity

A temporary push trigger on branch ecm/ci/android-example-play-publish is still present in the workflow, with an inline comment explicitly stating "Remove this push trigger before merging to master." If merged as-is, any push to that branch would trigger the full publish pipeline, potentially uploading unintended builds to the Play Store internal track. The PR description only mentions workflow_dispatch and release: published as intended triggers.

 

^{Reviewed by Cursor Bugbot for commit 0924305. Configure here.}