Release: 2.28.0

[uc-brunosilva]

No description provided.

[codeant-ai]

Skipping CodeAnt AI review — this PR is a back-merge between long-lived branches (release/2.28.0 → master). The diff here has already been reviewed when the underlying commits landed on the source branch, so re-running analysis would produce duplicate findings on already-reviewed code.

If you want to analyze this anyway (e.g. you resolved conflicts with new logic), comment @codeant-ai : review and CodeAnt will start a review.

[coderabbitai]

Warning

Review limit reached

@uc-brunosilva, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9093a2a2-6fa4-44a1-9e2c-28bf46efeea5

📥 Commits

Reviewing files that changed from the base of the PR and between 9b26528 and 7cd559c.

⛔ Files ignored due to path filters (2)

• package-lock.json is excluded by !**/package-lock.json
• sample/ios/Podfile.lock is excluded by !**/*.lock

📒 Files selected for processing (3)

• CHANGELOG.md
• android/build.gradle.kts
• package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/2.28.0

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[qodo-code-review]

PR Summary by Qodo

Release 2.28.0

📝 Documentation ⚙️ Configuration changes 🕐 Less than 5 minutes

AI Description

• Publish 2.28.0 release notes covering cross-platform fixes.
• Bump Android and npm package versions to 2.28.0.
• Align iOS package version metadata with the 2.28.0 release.

High-Level Assessment

The following are alternative approaches to this PR:

1. Automate release versioning/changelog via release tooling

• ➕ Reduces risk of version mismatch across Gradle/package.json/changelog
• ➕ Improves repeatability (tags, notes, and artifacts generated consistently)
• ➖ Upfront setup/maintenance (e.g., changesets, semantic-release, custom scripts)
• ➖ May require adapting existing release workflow and CI permissions

2. Single source-of-truth version file consumed by build systems

• ➕ Prevents drift by deriving all versions from one file (e.g., .version or gradle.properties)
• ➕ Simplifies review (one file change for version bumps)
• ➖ Requires plumbing for npm + Gradle + any iOS packaging metadata
• ➖ May be awkward if tooling expects version in specific manifests

Recommendation: Current manual bump is fine for this release-sized change. Longer-term, consider lightweight automation (or a single version source) to avoid accidental cross-file version skew as the number of published artifacts grows.

Files changed (3) +12 / -3

Documentation (1) +9 / -0

CHANGELOG.mdAdd 2.28.0 release notes +9/-0

Add 2.28.0 release notes

• Adds a new 2.28.0 section dated Jul 8, 2026. Documents fixes across Android/iOS UI behavior, iOS Unity static package compilation, Consent-or-Pay toggle handling, Billing metrics, and TCF dependency/purpose-one behavior.

CHANGELOG.md

Other (2) +3 / -3

build.gradle.ktsBump Android SDK version constant to 2.28.0 +1/-1

Bump Android SDK version constant to 2.28.0

• Updates the 'usercentricsVersion' value from 2.27.3 to 2.28.0 to match the release.

android/build.gradle.kts

package.jsonBump npm and iOS package versions to 2.28.0 +2/-2

Bump npm and iOS package versions to 2.28.0

• Updates the npm package 'version' and 'iosPackageVersion' fields from 2.27.3 to 2.28.0 to align published artifacts for this release.

package.json

[pantoaibot]

PR Summary:

Release: 2.28.0 — bumps package versions and adds changelog entries for several platform fixes.

• Updated version strings:
  • android/build.gradle.kts: usercentricsVersion → 2.28.0
  • package.json: version → 2.28.0, iosPackageVersion → 2.28.0
• Changelog (2.28.0) — Fixes:
  • Android/iOS: prevent multiple overlapping banners when showFirstLayer/showSecondLayer are called rapidly
  • Android: fix button spacing ignored in the second-layer footer
  • iOS: fix Unity static package iOS build compile failure
  • PUR: flexible special features/purposes in Consent-or-Pay now show a toggle instead of being forced mandatory
  • Billing: fix session buffer overcounting that caused a spike in the Displays metric
  • TCF: remove hard AppsFlyer import and correct incorrect treatment of purpose-one
• No functional API surface changes or dependency updates in these diffs; no breaking changes apparent from the provided changeset.

Reviewed by Panto AI

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

[pantoaibot]

Reviewed up to commit:7cd559c0779ebdaf67ecd0220163134b287896ac

Reviewed by Panto AI