Skip to content

chore(android): bump mParticle core/rokt-kit floor to 5.79.2 (carries roktsdk 4.14.5 deferred-init fix)#344

Merged
nickolas-dimitrakas merged 2 commits into
mainfrom
chore/bump-rokt-kit-5.79.2
Jun 22, 2026
Merged

chore(android): bump mParticle core/rokt-kit floor to 5.79.2 (carries roktsdk 4.14.5 deferred-init fix)#344
nickolas-dimitrakas merged 2 commits into
mainfrom
chore/bump-rokt-kit-5.79.2

Conversation

@nickolas-dimitrakas

Copy link
Copy Markdown
Contributor

Summary

Raises the mParticle Android dependency floor to [5.79.2, 6.0) and bumps the sample app to 5.79.2, so React Native consumers resolve a Rokt kit built against com.rokt:roktsdk 4.14.5.

Location Before After
Expo plugin kit injection (plugin/src/withMParticleAndroid.ts) [5.79.0, 6.0) [5.79.2, 6.0)
Bridge core (android/build.gradle, api + test pin) 5.79.0 5.79.2
Sample app (sample/android/app/build.gradle) android-core / android-rokt-kit 5.79.0 5.79.2

Why

com.mparticle:android-rokt-kit:5.79.2 is the first kit built against com.rokt:roktsdk 4.14.5, which fixes overlay/bottom-sheet placements failing on late/deferred Rokt.init() — the exact React Native + mParticle scenario (async kit load / deferred first-frame init) where the SDK initialised after the host Activity had already resumed and the cached Activity stayed null. 4.14.5 observes the Activity lifecycle from process start (via a no-op ContentProvider) and recovers the host Activity from the Compose context.

Chain: ROKT/sdk-android-source#1087 (roktsdk 4.14.5, released) → mparticle-integrations/mparticle-android-integration-rokt#146 (kit pin bump) → mParticle Android SDK 5.79.2 release → this PR.

The bounded upper bound (< 6.0) is unchanged — it keeps kit + core paired on the 5.x line and avoids resolving 6.0.0-rc.1, consistent with the existing comments and #710.

⚠️ Merge ordering

This PR is gated on mParticle/mparticle-android-sdk 5.79.2 publishing android-core + android-rokt-kit 5.79.2 to Maven Central. Until then, Android CI will fail to resolve [5.79.2, 6.0) (5.79.1 is below the floor and 6.0.0-rc.1 is excluded). Do not merge before 5.79.2 is live; re-run CI once it is.

Notes

  • Plugin source only (plugin/build is gitignored); no compiled output to update.
  • Docs that read "5.79.0 or newer" describe other feature minimums (CNAME / session APIs) and remain accurate, so they're intentionally left unchanged.
  • No npm version bump here — the repo's release workflow handles versioning from the [Unreleased] CHANGELOG section.

Raises the com.mparticle:android-core / android-rokt-kit dependency floor
to [5.79.2, 6.0) in the Expo plugin kit injection and the bridge
android/build.gradle, and bumps the sample app pins to 5.79.2.

5.79.2 is the mParticle Android release whose android-rokt-kit is built
against com.rokt:roktsdk 4.14.5, which observes the Activity lifecycle
from process start so overlay placements display on deferred/late
Rokt.init() (the React Native + mParticle deferred-init scenario).
@nickolas-dimitrakas nickolas-dimitrakas requested a review from a team as a code owner June 22, 2026 20:20
Copilot AI review requested due to automatic review settings June 22, 2026 20:20
@cursor

cursor Bot commented Jun 22, 2026

Copy link
Copy Markdown

PR Summary

Medium Risk
Dependency-only change, but it shifts what every Android consumer resolves at build time and requires Maven Central 5.79.2 to be published before CI passes.

Overview
Raises the Android mParticle dependency floor from 5.79.0 to 5.79.2 (still bounded at < 6.0) in the bridge android/build.gradle, Expo kit injection in withMParticleAndroid.ts, and the sample app’s android-core / android-rokt-kit pins.

CHANGELOG documents the fix: consumers should resolve a Rokt kit built on roktsdk 4.14.5, which tracks the host Activity from process start so overlay/bottom-sheet placements work when Rokt.init() runs after the Activity has already resumed (common with deferred React Native init). sample/README is updated to match the new pin.

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

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Android mParticle dependency minimums across the React Native bridge, Expo config plugin, and sample app to ensure consumers resolve android-rokt-kit built against com.rokt:roktsdk 4.14.5 (deferred-init Activity lifecycle fix).

Changes:

  • Bump the bridge’s com.mparticle:android-core dependency range to [5.79.2, 6.0) and update the test pin to 5.79.2.
  • Raise the Expo plugin’s injected kit dependency floor to [5.79.2, 6.0).
  • Update the sample Android app to pin android-core / android-rokt-kit to 5.79.2 and document the change in CHANGELOG.md.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File Description
sample/android/app/build.gradle Bumps sample app’s pinned android-core and android-rokt-kit versions to 5.79.2.
plugin/src/withMParticleAndroid.ts Raises the injected Android kit dependency range floor to 5.79.2 while keeping < 6.0.
CHANGELOG.md Adds an Unreleased entry documenting the Android dependency floor bump and rationale.
android/build.gradle Raises the bridge’s android-core range floor and test pin to 5.79.2.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread sample/android/app/build.gradle
Addresses review feedback: sample/README stated 5.79.0 while
sample/android/app/build.gradle now pins android-core / android-rokt-kit
to 5.79.2.
@nickolas-dimitrakas nickolas-dimitrakas merged commit bec0ee4 into main Jun 22, 2026
17 of 20 checks passed
@nickolas-dimitrakas nickolas-dimitrakas deleted the chore/bump-rokt-kit-5.79.2 branch June 22, 2026 21:01
@rokt-releases rokt-releases Bot mentioned this pull request Jun 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants