Release: 2.27.1 - #241
Conversation
🤖 CodeAnt AI — Review Status
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (3)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe release metadata and Android native SDK dependency are changed from version 2.30.0 to 2.27.1. The changelog records the 2.27.1 release. ChangesRelease version alignment
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This release updates the native SDK and package versions with matching lockfile and changelog changes; no actionable merge-blocking risk remains beyond normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (2 skipped: 2 unsupported.) ✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
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. Comment |
|
PR Summary: Release 2.27.1 — version/changelog updates and native SDK bump.
|
| "author": "Usercentrics <developer@usercentrics.com>", | ||
| "iosPackageName": "react-native-usercentrics", | ||
| "iosPackageVersion": "2.30.0", | ||
| "iosPackageVersion": "2.27.1", |
There was a problem hiding this comment.
[VALIDATION] You updated "iosPackageVersion" to "2.27.1". If this is meant to reflect the native iOS SDK version, confirm that the iOS Podspec (react-native-usercentrics.podspec), any CocoaPods/publish metadata, and native iOS binary used in the ios/ folder are updated to match. Run pod install / a sample iOS build to verify the specified version is resolvable and the API is compatible with the JS bridge.
{
"name": "@usercentrics/react-native-sdk",
"version": "2.27.1",
"description": "Usercentrics SDK",
"homepage": "https://usercentrics.com",
"main": "lib/index.js",
"types": "lib/index.d.ts",
"author": "Usercentrics <developer@usercentrics.com>",
"iosPackageName": "react-native-usercentrics",
"iosPackageVersion": "2.27.1",
"license": "SEE LICENSE IN LICENSE",
"files": [
"android",
"ios",
"lib",
"src",
"react-native-usercentrics.podspec",
"react-native.config.js",
"!.DS_Store",
"!.gradle",
"!.idea",
"!build",
"!gradle",
"!*.iml",
"!gradlew",
"!gradlew.bat",
"!local.properties",
"!project.xcworkspace",
"!xcshareddata",
"!xcuserdata"
]
}| @@ -1,4 +1,4 @@ | |||
| val usercentricsVersion = "2.30.0" | |||
| val usercentricsVersion = "2.27.1" | |||
There was a problem hiding this comment.
[CRITICAL_BUG] The usercentricsVersion was changed from "2.30.0" to "2.27.1" (a downgrade). Confirm this is intentional. If you intended to bump the native SDK, set the correct newer version; if you intended to pin to 2.27.1, ensure downstream Android build files and publication metadata (Maven coordinates, dependency availability) are consistent. Run a full Android build (assemblePublish / ./gradlew assemble) and integration tests to verify no missing artifacts or API incompatibilities. Also ensure this value stays in sync with any iOS/native version metadata.
// If the intent is to truly bump to 2.27.1 (rollback from 2.30.0),
// keep Android/iOS/native metadata consistent as already done in package.json
// and changelog. Consider adding a short comment to document why this
// version is lower than the previous tag to avoid future confusion.
val usercentricsVersion = "2.27.1"| ### 2.27.1 – Aug 25, 2026 | ||
| ## Chores | ||
| * **[Core]** Bumped native Usercentrics SDK to 2.27.1. |
There was a problem hiding this comment.
[NITPICK] The new 2.27.1 entry was inserted above the existing 2.30.0 entry, which is confusing because 2.30.0 is a later release. Keep changelog entries in descending chronological order. Also clarify in the entry that this change only updates the native Usercentrics SDK dependency (and whether this is a downgrade), so readers understand the scope (native-only vs. JS/API changes).
[Release Notes](https://docs.usercentrics.com/cmp_in_app_sdk/latest/about/history/)
### 2.30.0 – Aug 19, 2026
## Features
* **[Unity — Mediation]** Added support for Unity's End-User Consent Mode API (`EndUserConsent.SetConsentState`), mapping UC consent decisions to Unity Vector's `AnalyticsIntent`/`AdsIntent` signals — unblocks Unity Ads Vector adoption. Also fixed the dead Unity Ads link in the Consent Mediation docs
* **[Android]** Added APIs to capture and restore in-flight 2nd-layer consent state across Activity recreation (e.g. dark-mode toggles, single-activity navigation hosts), so unsaved user selections are no longer lost
* **[Flutter]** Added Swift Package Manager (SPM) support for the iOS plugin, recommended for Xcode 15+, alongside continued CocoaPods compatibility
## Fixes
* **[Android — Mediation]** Fixed `CrashlyticsMediationSDK` throwing `NoClassDefFoundError` on Firebase BOM 34+ by resolving `FirebaseCrashlytics` via reflection instead of the removed KTX API
* **[Unity/Android]** Fixed a crash during SDK initialization in Unity Development builds on Android (Production builds were unaffected)
### 2.29.1 – Aug 5, 2026
## Features
* **[Unity]** Added `isExempt` to the Unity `ServiceConsent` model, propagating the statistical exception flag to the Unity bridge
### 2.29.0 – Aug 5, 2026
## Features
* **[Mediation]** Added Amazon Consent Signal (ACS) mediation support for Android and iOS, including Adjust adapter integration
* **[PUR Compliance]** Added statistical exception disclosure and toggle UI to the first and second layer, and excluded statistical exception services from Reject All/Deny All, supporting the UK DUAA statistical-exception requirement
* **[Unity]** Automated the Unity-flavored SPM release pipeline, publishing `usercentrics-spm-ui`/`usercentrics-spm-sdk` package tags for Unity releases
## Fixes
* **[Android]** Fixed consent banner rendering behind system bars on edge-to-edge displays
* **[Android]** Fixed `ExternalLinkSpan.onClick` crash on invalid/empty link URLs
* **[iOS]** Fixed app hang caused by synchronous HTML parsing in first-layer banner/content text
* **[Android/iOS]** Removed residual `assert(false)` calls in Additional Consent Mode and CCPA save paths that could crash debug builds
* **[TV]** Fixed `DPAD_DOWN` navigation escaping the second-layer detail list boundary
## Chores
* **[Unity]** Stripped debug symbols from iOS core release binaries, reducing device binary size by ~31% with no functional change
### 2.27.1 – Aug 25, 2026
## Chores
* **[Core]** Downgraded bundled native Usercentrics SDK dependency from 2.30.0 to 2.27.1 (no changes to the React Native JS API surface).|
Reviewed up to commit:62266aba0e78d7cf208c3d5ce7aee6b4fdf11090 |
62266ab to
e56ab7a
Compare
User description
Automated bump of the native Usercentrics SDK dependency to 2.27.1.
CodeAnt-AI Description
Release the React Native SDK with native Usercentrics SDK 2.27.1
What Changed
Impact
✅ Consistent Android and iOS SDK versions✅ Clearer package release versioning✅ Documented native SDK update💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.
Summary by CodeRabbit